upgrading to 1.5.8 results in 500 error.

[delia]

the new files trigger the 500 error. Never get to start the upgrade process - even in a new folder with just the 1.5.8 files. The client was able to install it in another folder so the mystery continues. At least I can move forward now.

I'm sure he uploaded the files via ftp whereas I used a zip file as I normally do. Not the original zip but one without a few things and not in a folder. Been doing this way for nearly 20 years. Can servers make a hash out of a zip file when extracting? I used the same zip on my test server with no issues. k

[delia]

*reminder - now running php 8.1*
ran the database upgrade - this message appeared /zc_install/includes/nginx_conf/ folder is not writeable so changed it to 777 instead of 755 which made the message go away.

Then discovered 71 install logs labeled debug. This one was the last so it looks like it's correcting the database?

[11-Feb-2023 09:02:33 America/New_York] MySQL error 1292 encountered during zc_install:
Incorrect datetime value: '0000-00-00 00:00:00' for column 'gdpr_accept_date' at row 1
ALTER TABLE customers ADD registration_ip varchar(45) NOT NULL default '';
---------------


[11-Feb-2023 09:02:33 America/New_York] MySQL error 1292 encountered during zc_install:
Incorrect datetime value: '0000-00-00 00:00:00' for column 'gdpr_accept_date' at row 1
ALTER TABLE customers ADD last_login_ip varchar(45) NOT NULL default ''; 

Also getting tons of error/warning logs from admin.

At least I've gotten to the point where I can start correcting small errors in the template.

My point in continuing this is that I'm thinking the issues are related to the server and not to 1.5.8. Anybody agree with that assessment?

[swguy]

The GDPR date issue can be fixed using this technique:

https://docs.zen-cart.com/user/upgra...andardization/

500 errors please review this list:
https://docs.zen-cart.com/user/troub...ternal_server/

[delia]

Thanks for that 500 link, Scott!

I am seeing admin messages:

[11-Feb-2023 11:16:27 America/New_York] Request URI: /store/xxxxx/index.php?cmd=developers_tool_kit&action=locate_all_files, IP address: 76.179.90.49
#0 [internal function]: zen_debug_error_handler()
#1 /home/xxxxx/public_html/store/xxxxx/includes/init_includes/init_templates.php(49): define()
#2 /home/xxxxx/public_html/store/includes/autoload_func.php(40): require_once('/home/humbleabo...')
#3 /home/xxxxx/public_html/store/xxxxx/includes/application_top.php(42): require('/home/humbleabo...')
#4 /home/xxxxx/public_html/store/xxxxx/developers_tool_kit.php(8): require('/home/humbleabo...')
#5 /home/xxxx/public_html/store/xxxx/index.php(11): require('/home/humbleabo...')
--> PHP Warning: Constant TITLE already defined in /home/humbleabodes/public_html/store/humble/includes/init_includes/init_templates.php on line 49.

I don't see this as fixed in github. My github search abilities in issues is crappy. Do I need to open a new issue?

[swguy]

How do you repro this? Please give detailed instructions.

[delia]

any movement in admin shows this:

[11-Feb-2023 12:23:12 America/New_York] Request URI: /store/xxxxx/index.php?cmd=display_logs&fID=a5eeb71c2e42b7bd87fc00cca535c56d634880e7&, IP address: 76.179.90.49
#0 [internal function]: zen_debug_error_handler()
#1 /humble/includes/init_includes/init_templates.php(49): define()
#2 /includes/autoload_func.php(40): require_once('/home/xxxx...')
#3 /humble/includes/application_top.php(42): require('/home/xxxx...')
#4 /zc_plugins/DisplayLogs/v3.0.1/admin/display_logs.php(35): require('/home/xxx...')
#5 /humble/index.php(23): require('/home/xxx...')
--> PHP Warning: Constant TITLE already defined in /xxxx/includes/init_includes/init_templates.php on line 49.

[11-Feb-2023 12:23:12 America/New_York] Request URI: /store/xxxx/index.php?cmd=display_logs&fID=a5eeb71c2e42b7bd87fc00cca535c56d634880e7&, IP address: 76.179.90.49
#0 [internal function]: zen_debug_error_handler()
#1 /humble/includes/init_includes/init_category_path.php(12): define()
#2 /includes/autoload_func.php(40): require_once('/home/xxxxx...')
#3 /humble/includes/application_top.php(42): require('/home/xxxxx...')
#4 /zc_plugins/DisplayLogs/v3.0.1/admin/display_logs.php(35): require('/home/humbleabo...')
#5 /humble/index.php(23): require('/home/xxxx...')
--> PHP Warning: Constant TOPMOST_CATEGORY_PARENT_ID already defined in /xxxxx/includes/init_includes/init_category_path.php on line 12.

For example, if I delete those logs in display errors - it creates 3 more.

[lat9]

[QUOTE=delia;1393100]any movement in admin shows this:

[11-Feb-2023 12:23:12 America/New_York] Request URI: /store/xxxxx/index.php?cmd=display_logs&fID=a5eeb71c2e42b7bd87fc00cca535c56d634880e7&, IP address: 76.179.90.49
#0 [internal function]: zen_debug_error_handler()
#1 /humble/includes/init_includes/init_templates.php(49): define()
#2 /includes/autoload_func.php(40): require_once('/home/xxxx...')
#3 /humble/includes/application_top.php(42): require('/home/xxxx...')
#4 /zc_plugins/DisplayLogs/v3.0.1/admin/display_logs.php(35): require('/home/xxx...')
#5 /humble/index.php(23): require('/home/xxx...')
--> PHP Warning: Constant TITLE already defined in /xxxx/includes/init_includes/init_templates.php on line 49.

[11-Feb-2023 12:23:12 America/New_York] Request URI: /store/xxxx/index.php?cmd=display_logs&fID=a5eeb71c2e42b7bd87fc00cca535c56d634880e7&, IP address: 76.179.90.49
#0 [internal function]: zen_debug_error_handler()
#1 /humble/includes/init_includes/init_category_path.php(12): define()
#2 /includes/autoload_func.php(40): require_once('/home/xxxxx...')
#3 /humble/includes/application_top.php(42): require('/home/xxxxx...')
#4 /zc_plugins/DisplayLogs/v3.0.1/admin/display_logs.php(35): require('/home/humbleabo...')
#5 /humble/index.php(23): require('/home/xxxx...')
--> PHP Warning: Constant TOPMOST_CATEGORY_PARENT_ID already defined in /xxxxx/includes/init_includes/init_category_path.php on line 12.

@delia, see this Zen Cart issue for the correction: https://github.com/zencart/zencart/issues/4939

Noting that those changes will be present in zc158a.

[delia]

That was my purpose - I figured that had been tended to already but needed to make sure it was a known issue. Thanks!