Haven't seen anyone post about trying to use this with ZC 1.5.6 or issues directly related to using this with ZC 1.5.6 (where more likely to have stricter controls over operations); however, did want to provide some information if a problem occurs that identifies this plugin by reference to the table orders field order_delivery_date.
Operation on my test site shows history that at some point in use/development a date of 0000-00-00 was stored in the field; however, in operation of the current version it appears to properly store a value of null. That said, I wanted to address the problem before it was identified as an issue if it is/has been.
My suggestion first would be that while the database modifications of this plugin are present, that the following SQL be executed prior to attempting to upgrade to ZC 1.5.6 or if you ever encounter a problem modifying the orders table and the order_delivery_date field is identified as a problem.
The problem statement that may be expected to be seen in the zcInstall related logs would be something like:
Code:
[DATE_AND_TIME_OF_ISSUE SERVER_TIMEZONE] MySQL error 1292 encountered during zc_install:
Incorrect date value: '0000-00-00 00:00:00' for column 'order_delivery_date' at row XXX
ALTER TABLE orders ADD order_weight FLOAT default NULL;
The following SQL could be executed to eliminate any such issue with the order_delivery_date field.
Code:
UPDATE orders SET order_delivery_date = NULL WHERE order_delivery_date < '0001-01-01' and order_delivery_date is not null;
If operating with ZC 1.5.1 and above, the sql statement could be applied as is in the admin->Tools->Install SQL Patches. If, however, it is executed in phpMyAdmin, a similar database access utility or from within an older version of Zen Cart, then care must be taken to prepend the DB_PREFIX (defined in includes/configure.php and matching in admin/includes/configure.php) to orders. If the prefix were 'bright_', then the above would start with UPDATE bright_orders SET ...