Experiencing a 301 redirection loop after deactivating the Cache Enabler plugin can be a challenging situation, but we’ll guide you through the steps to resolve it and regain access to your WordPress admin dashboard.
Step 1: Identifying the Issue
When deactivating Cache Enabler, it seems that a static HTML file causing the 301 redirection loop was saved. To address this, we need to locate and remove this static content.
Step 2: File Locations
Cache Enabler typically stores its static files in the WordPress uploads directory. Navigate to your WordPress installation via FTP or file manager and look for a folder named “cache-enabler.” Inside this folder, you should find static HTML files generated by the plugin.
Step 3: Clear Cache Enabler Files
Delete the contents of the “cache-enabler” folder. This action will remove the static files created by Cache Enabler, resolving the 301 loop issue.
Step 4: Resetting .htaccess
To ensure a clean slate, reset your .htaccess file. Access your WordPress root directory and locate the .htaccess file. Rename it to something like “.htaccess_backup.” WordPress will generate a new .htaccess file with default settings.
Step 5: Verify Site URL
Access the WordPress database using phpMyAdmin or a similar tool. Locate the “wp_options” table and check the values for “siteurl” and “home.” Ensure that these URLs match your website’s domain. Update them if necessary.
Step 6: Browser Cache and Cookies
Clear your browser cache and cookies to eliminate any cached redirects. This step is crucial for testing whether the issue persists.
After completing these steps, try accessing your WordPress site and admin dashboard. The 301 redirection loop should be resolved, and you should regain control.
If the issue persists, it may be beneficial to consult with your hosting provider or seek assistance from the WordPress support community.
Remember, always back up your site before making significant changes to ensure you can restore it if needed. We hope this guide helps you successfully resolve the 301 loop after Cache Enabler deactivation.