[23-Mar-2024 11:34:42 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Uri.php on line 24 [23-Mar-2024 17:22:13 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Toolbar.php on line 22 [26-Mar-2024 13:29:00 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Shortcode.php on line 19 [07-Apr-2024 20:50:03 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Compatibility.php on line 21 [22-Apr-2024 01:11:01 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/LoginRedirect.php on line 23 [27-Apr-2024 12:01:47 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Core.php on line 29 [29-Apr-2024 08:46:14 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [20-May-2024 23:30:31 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [14-Jun-2024 03:19:07 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [15-Jun-2024 11:51:01 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Uri.php on line 24 [21-Jun-2024 22:54:39 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Compatibility.php on line 21 [25-Jul-2024 17:18:44 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [25-Jul-2024 17:18:44 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Toolbar.php on line 22 [15-Aug-2024 09:41:56 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [15-Aug-2024 09:41:56 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [15-Aug-2024 09:41:56 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [26-Aug-2024 09:54:58 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [26-Aug-2024 09:54:58 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [26-Aug-2024 09:54:58 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Capability.php on line 16 [28-Aug-2024 00:16:58 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [28-Aug-2024 00:16:58 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [28-Aug-2024 00:16:58 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Shortcode.php on line 19 [06-Sep-2024 22:28:06 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [06-Sep-2024 22:28:06 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [06-Sep-2024 22:28:06 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_SingletonTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Core.php on line 29 [11-Sep-2024 15:48:15 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [11-Sep-2024 15:48:15 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [11-Sep-2024 15:48:15 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/SecureLogin.php on line 32 [13-Sep-2024 13:54:30 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [13-Sep-2024 13:54:30 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [13-Sep-2024 13:54:30 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/DeniedRedirect.php on line 21 [24-Sep-2024 18:09:42 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [24-Sep-2024 18:09:42 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [24-Sep-2024 18:09:42 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_RequestTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/Toolbar.php on line 22 [24-Oct-2024 10:28:10 UTC] PHP Warning: Module 'sodium' already loaded in Unknown on line 0 [24-Oct-2024 10:28:10 UTC] PHP Warning: Version warning: Imagick was compiled against ImageMagick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 [24-Oct-2024 10:28:10 UTC] PHP Fatal error: Trait 'AAM_Core_Contract_ServiceTrait' not found in /home/xhtmljunkies/public_html/wp-content/plugins/advanced-access-manager/application/Service/DeniedRedirect.php on line 21 How to Organize a Magento Error Page? | Xhtmljunkies
Check out our newest developed Magento 2 Customer Discount More Info

How to Organize a Magento Error Page?

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:

#Mage::setIsDeveloperMode(true);

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

          /report/config.xml

Modify this line

      <action>print</action>

To

      <action>email</action>

And insert your email address in this line

      <email_address></email_address>

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.

Author: Harshal Shah

Harshal Shah is CEO & Founder of Xhtmljunkies, Located in Gujarat, India, XHTML Junkies is one of the best companies that offer unique eCommerce solutions by the virtue of its dedicated professionals. Our professionals are extremely proficient in offering development services pertaining to eCommerce. You can find Harshal on and Twitter.

The following two tabs change content below.

Harshal Shah

Harshal Shah is CEO & Founder of Xhtmljunkies, Located in Gujarat, India, XHTML Junkies is one of the best companies that offer unique eCommerce solutions by the virtue of its dedicated professionals. Our professionals are extremely proficient in offering development services pertaining to eCommerce. You can find Harshal on and Twitter.