[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
The Magento Database Repair Tool evaluates two databases i.e. reference and target. After comparing these two databases, this tool updates the target database so as to keep its structure same as the structure of reference database. This is done by performing the following methods:
The Database Repair Tool is applied to fix the database of an existing Magento installation that contains any of the errors which are stated above. You just have to install the same version of Magento that you are using into a clean database. Use the new database as “reference” and existing database as “corrupted”.
The most important thing which you should always keep in your mind, make sure that you have tested the database repair tool on development environment before actually running it on production environment. Also, don’t forget to keep a backup of your original database prior to running database repair tool.
While the repairing process is going on, it is highly advisable to restrict the access to your website. By restricting your Magento instance to your IP address, the visitors including search spiders, will get the HTTP503 Service Unavailable error.
You have to generate a 503.php file in your Magento installation root as:
After doing this, you have to add the rewrite rule in .htaccess or in Apache server configuration as follows:
RewriteEngine On
RewriteCond %{REMOTE_ADDR} !^127.0.0.1$
RewriteRule ! 503.PHP$ /503.PHP [L]
Where, 127.0.0.1 (backslashes ahead of dots) should be reinstated with your IP-address. As you save this .htaccess file or restore the Apache configuration, your site will be down until you bring back to original status.
Here are the Steps:
Currently, You have the duplicate copy of your original database in “database2” and empty Magento installed in”database3”
Now,
Run http://url-of-your-server/path-to-folder/magento-db-repair-tool-1.0.php
Don’t forget to remove the magento-db-repair-tool-1.0.php. Now, you can Access your website on browser and you are done.
]]>