It's tough to diagnose something wrong with the server, especially when they'll rarely investigate "3rd party software".
So, to figure out why there aren't error logs, we can try to force a known error, and fiddle with the logging mechanism a bit.
Let's try commenting-out line 76 of /includes/extra_configures/enable_error_logging.php by adding // to the front of the line, like this:
Code:
// set_error_handler('zen_debug_error_handler', $errors_to_log);
That'll rule out whether some of the extra decoration of error message data may be something the server is denying use of.
Then go rename the /includes/init_includes folder to init_includes_TMP and try to visit the site. This should give a blank page, and fatal errors in the logs. Then rename it back so your visitors aren't impacted. Then go look at what's in the logs directory.
Next option might be to write a single-file php script that enables error reporting perhaps at its maximum level (which we don't usually do on a "production" site, for both performance and unsafe disclosure reasons), specifies a log directory, and then triggers an error that should be written. Then see what happens. Isolate the issue completely away from Zen Cart so the hosting company can see how a basic function isn't working, and then they can own the issue until it's fixed.
Or it may point to something that's been altered inside Zen Cart with plugins or broken php files etc.
Bookmarks