Making sure additional logging (other than the built in Zen Cart logging system) is where I would start... Enabling PHP logging will catch errors occuring before Zen Cart's logging code is started. I typically just edit php.ini directly (hosting provider permitting):
Code:
error_reporting = E_ALL | E_STRICT
display_errors = On
display_startup_errors = On
log_errors = On
error_log = /home/account/php_errors.log
Visual Output File Output
Setting error_log will cause PHP to not attempt to send the errors to the SAPI or SYSTEM error logger and instead log directly to a file. This makes it far easier to find PHP related errors without having to ask the host for access to their webserver / system error logs.
If no errors are found / logged by the above, then move on to checking where in the execution flow (using something like the TRACE_NOTIFIER plugin) the script is "dying" or failing to output the expected data.
If switching the template makes the site show back up, I would probably double check any "override" folders... Especially those specific to the problematic template.
NOTE: Do not leave visual display of errors enabled on a production server, it should only be enabled while actively debugging.
Bookmarks