While working with Magento for a long time, a server side error like “error processing your request” page may take place, which is sometimes become very irritating. This error page should never appear to online customers on a live site for the reason that, this may alert the website attackers to attack your website, also there are chances for the users of your website to get confused seeing such a page and may not found your website user-friendly.
The responsible person of the website may not be aware of this error, except a customer contacts him and inform him regarding Magento error page. Now, you can make up the behavior of Magento in case of errors, as there are two major changes that have been introduced between Magento version 1.3 and 1.4, one is, these errors are no longer put on view by default and other is, the error managing has been moved from the report folders to a dedicated error folder in a standard install.
During development, be sure to facilitate the developer mode so that you’ll be able to see the errors directly on the page where they crop up. To perform this action in version 1.3, you just have to open the index.php in the root of your Magento setting up and take out the comment from the line:
In version 1.4 and newer, as environment variable has been established that allow you to set developer mode on your test server, thus you need not to have different copies of index.php for different servers.
If an error develops the Magento can email this error to an important person and also exhibit a feedback form for the visitors requesting for details.
In the Version 1.3, to do the set up, follow these steps:
Go to the file
Modify this line
And insert your email address in this line
That’s it and you are done.
In Version 1.4, as report/config.xml has been substituted by errors/local.xml, what you have to do is, throughout a fresh installation there will be an error folder having a local.xml sample file, copy that file and rename this as local.xml and adjust this in the same manner as you have done earlier in version 1.3 followed by the steps as described above.