Return to Answer

Debugging is a bit of an art, but something that can easily be mastered by following a simple regiment.

Debugging is a bit of an art, but something that can easily be mastered by following a simple regimen.

Content willingly sourced from www.sonassi.com/knowledge-base/magento-debug-process and www.sonassi.com/knowledge-base/stop-magento-permissions-errors-permanently

^{Content willingly sourced from www.sonassi.com/knowledge-base/magento-debug-process and www.sonassi.com/knowledge-base/stop-magento-permissions-errors-permanently}

You can enable errors with a more permanent solution, or something merely more temporary.

In your document root .htaccess file - just drop this at the top.

For Nginx/fastcgi users

Incorrect permissions will cause a wealth of problems, a lot of which are not transparent.

And in your BASH environment for SSH, set this in either you .bashrc or .bash_profile

For your FTP server, you’ll need to read the documentation for it, but the principal is the same.

*This comes with the caveat that some modules may be dependant on certain theme features

Rather than change anything via the admin, it is much simpler to merely rename the offending directories.

Again, rather than disable modules via the Magento admin. It is more practical to do this at a file-level.

Some models are actually still stored in the database (Eg. order increment) - so at this point, it becomes a case of manually making those edits. So far, all the steps above have been reversible with no lasting damage. But if we were in import a clean Magento database too - it could prove reversible (short of restoring a backup).

You can enable errors with a more permanent solution, or merely something more temporary.

In your document root's .htaccess file - just drop this at the top.

For Nginx/FastCGI users

Incorrect permissions will cause a wealth of problems, a lot of which are not that easy to find at first glance.

And in your BASH environment for SSH, set this in either your .bashrc or .bash_profile

For your FTP server, you’ll need to read the documentation for it, but the principle is the same.

*This comes with the caveat that some modules may be dependent on certain theme features

Rather than change anything via the admin panel, it is much simpler to merely rename the offending directories.

Again, rather than disable modules via the Magento admin panel, it is more practical to do this at a file level.

Some models are actually still stored in the database (Eg. order increment) - so at this point, it becomes a case of manually making those edits. So far, all the steps above have been reversible with no lasting damage. But if we were in import a clean Magento database too - it could prove irreversible (short of restoring a backup).