The defined_paths.php files (either) contain a comment that, “It should NOT be necessary to edit anything here. Anything requiring overrides can be done in override files.” (in the /includes/...) or “It should NOT be necessary to edit anything here. Anything requiring overrides can be done in override files or in configure.php directly.” (in the /admin/includes/...).

I have never found any documentation whatsoever that indicates the override system applies to administration (to the contrary, that it doesn’t). I haven't found documentation that indicates how to override anything other than theme and a few other odds and ends.

I recently upgraded a heavily customized Zen Cart 1.3.9h site to 1.5.4. While that was being tested and taken live, 1.5.5 and 1.5.5a were released. That broke the defines that been put in configure.php, though, strangely, it didn't appear to break anything in the front-end.

By the way, the Upgrade Instructions indicated that it was only necessary to customize any files changed in 1.5.5 and upload those; however, when logging into admin, there is a warning that a database upgrade has not been done — when that is done, the configure.php files are updated).

To continue testing the 1.5.5a conversion (on a test site), I have modified the /admin/includes/defined_paths.php file. However, I would expect the override system that works on so much of the front-end to be able to handle this for /includes/defined_paths.php. Can someone explain please?

By the way, the way the defines are done in defined_paths.php could be simplified. Either all the defines will exist, or none of them will (because the only place they should be defined is in one of the defined_paths.php files). So it is only necessary for a single “if ()” statement to enclose all the defines. I suppose the saving is marginal, but it’s cleaner :)

Regards,
John