Database changes from 1.5.3 to 1.5.4

There seems to be a good bit of database structural changes from 1.5.3 to 1.5.4 which is causing a number of plugins (that involves sql modifications) that is listed as 1.5.x compatible to not work properly. It would really help a lot if the plugin compatibility information is a bit more accurate as compatible with 1.5.x is no longer true. Just an observation.

Not true. The only database change from ZC1.5.3 to 1.5.4 is the addition of a configuration switch.

michaelchu:

There seems to be a good bit of database structural changes from 1.5.3 to 1.5.4 which is causing a number of plugins (that involves sql modifications) that is listed as 1.5.x compatible to not work properly. It would really help a lot if the plugin compatibility information is a bit more accurate as compatible with 1.5.x is no longer true. Just an observation.
Perhaps it's worth you naming those problematic plugins here?

It's quite likely that you've installed some Numinix plugins that have changed the core structure of the "configuration" table, and thus has broken a zillion other otherwise-perfectly-compatible plugins in the process.

DrByte:

Perhaps it's worth you naming those problematic plugins here?

It's quite likely that you've installed some Numinix plugins that have changed the core structure of the "configuration" table, and thus has broken a zillion other otherwise-perfectly-compatible plugins in the process.
Our old plugins had some code that would delete a row that has a configuration_id of 0 or null. We didn't realize at the time there were actually configuration options that Zen Cart hides in the configuration table. Maybe those should actually just be defined in a file?

Anyways, that shouldn't be a problem if using any of our plugins that have been updated in the past 2-3 years.

numinix:

Our old plugins had some code that would delete a row that has a configuration_id of 0 or null. We didn't realize at the time there were actually configuration options that Zen Cart hides in the configuration table. Maybe those should actually just be defined in a file?

Anyways, that shouldn't be a problem if using any of our plugins that have been updated in the past 2-3 years.
Not completely correct. You also added additional columns, and therefore any code that didn't explicitly name the columns into which a value was being inserted, would break.

That's correct, some of our plugins have expanded the configuration table. It's a bad practice to blindly insert data into a table and those other plugins should be updated.