Troubleshooting eZ 101
Table of contents
Real trouble happens so seldom with eZ you will forget how to do even the most basic procedures.
Do Not Panic!
The Possible Edit Conflict warning that scares new users is actually no big deal. Hopefully eZ will in the future use these kinds of warnings for something much less likely to happen and much more critical.
Regular checkups can prevent problems.
Regular maintenance item, but included here as first step, make a habit of regularly checking last output in var/log/error.log. To be clear, that is the var folder within the eZ Publish file structure, not the var for the operating system.
ssh# tail -n50 var/log/error.log from the eZ Publish doc root is informative.
When all else has failed..
First stop is change /settings/override/site.ini.append.php
[DebugSettings]
DebugOutput=disabled
[DebugSettings]
DebugOutput=enabled
Edit the file, and if the text is not there, add it.
Debug settings can be changed in the admin interface, but if the admin interface is not displaying, this little bit of knowledge will be handy.
