Bakery is not working in STRICT-mode

[Gast]

thanks for the hint 
problem was a "wrong" page-name in combination with short-url. on my server, i can use every folder also as a subdomain. my short-url produce a like with the same name like the pontiac-folder and there is a intern project for registered users only with protected documents like repair instructions, software for the engine etc . But this project was a SP6 and doenst run under PHP 7.1.x

[freeSbee]

Cool car, and it's great that you carry it out as a family project!
I just liked to have a look at it on your website. Unfortunately there are a lot of php warnings at the pontiac page which you might want to rectify ...

[Gast]

also off topic

a 25y old Pontiac, not sooooo old 
engine, gearbox etc works fine, but the chassis needs a complete restauration to be fit for the next 25 years. i start with this job after my last holidaytrip to the northcap (norway) in 2008/2009, but then i get problems with my own body/shoulders, a lot of OP's in the last years and the rust "eating" the half body frame 
now, my son is 12 and old enough to help and my wife has experients, to dismount engine and axle etc and my job is cleaning and welding

[freeSbee]

Thanks so much for reporting, Uwe!

PS off topic:
What about your oldtimer?
Is it running yet?

[Gast]

sorry, i'm too late, but i need all my time to rebuild my oldtimer 

-not possible, to save additional image informations like html-title, alt etc, if you dont have defined any article options
Incorrect integer value: '' for column 'item_attribute_id' at row 1

to see the error message, add the db-error-check after the db-update in save_item.php // Ln 205
possible solutions: option with value = 0 in the image - option-select field or definition of a default value in save_item.php ~ Ln 204

[freeSbee]

Thanks for testing, gemnb!

[gemnb]

Thanks for the update freeSbee. 
I tested a new installation and an update with your criteria on my MySQL STRICT-mode configuration(s) and everything seems to work well.
I think that it would be better if more users test this update (also the NON-STRICT-mode users).

[freeSbee]

Please test Bakery version 1.80 which is adapted to mysql save mode (thanks to jacobi22).
Use for your tests a new install as well as an upgraded version.

Please test and give feedback on:

- Edit all backend settings
- Edit payment methods
- Add and edit items
- Add new item images
- Add new item attributes

- Put items into the cart
- Enter address data and proceed to checkout
- Choose different payment methods to pay
- Check order status

Download link: Bakery v1.80.

[gemnb]

As I wrote before, some providers (and there will be much more) have set their systems (MySQL) standard to STRICT-mode (mine too), so I can't change the setting.
It would benefit all none-STRICT-mode and STRICT-mode users if you could make an update for that. 

I read that STRICT-mode makes mySQL more secure. The fact that providers change their setting makes it almost necessary to change the code, I think.

[freeSbee]

I assume you are talking about the SQL mode STRICT_TRANS_TABLES, don't you?
What are the benefits of strict mode for Bakery?

BTW:
To determine the current session sql_mode value, use the following statement:

Code Select Expand

SELECT @@SESSION.sql_mode;

You can change the SQL mode at runtime. Set the session sql_mode system variable using a SET statement. To clear the SQL mode explicitly, set it to an empty string:

Code Select Expand

SET SESSION sql_mode = '';

[gemnb]

At the moment Bakery doesn't work in STRICT-mode. You have to alter the code to get it work. If that was a one-time job, no problem. But every release you have to fix the code (that takes a lot of time and I still can't get it to work properly ...).
Since more providers decide to put their systems in STRICT-mode, it may become a problem.

So a request to the the developer(s). Can you please fix the code in the Bakery module so everyone can use it (again)?