BugWP logo BugWP
Back to Community
Home / Community / Plugin → Redirection

Resolving Redirection Plugin Issues: Redirects Persisting After Deactivation

39 threads Sep 16, 2025 Plugin → Redirection

Content

One of the most perplexing issues users encounter with the Redirection plugin is when a redirect continues to work even after the plugin has been deactivated or a specific rule has been deleted. This guide will explain why this happens and provide the most effective solutions to resolve it.

Why Do Redirects Persist After Deactivation?

It's a common misconception that a deactivated plugin can still function. The Redirection plugin, once deactivated, ceases all operations and cannot perform any redirects. If a redirect is still occurring, the cause is almost always caching. Caching mechanisms store responses to make your site faster, but they can also store old redirect instructions long after the original source has been removed.

How to Identify and Fix the Problem

1. Clear All Caches

The first and most crucial step is to clear every cache that could be involved:

  • Browser Cache: Clear your browsing history and cached data, or test the URL in a browser's "incognito" or "private" window.
  • WordPress Cache: If you use a caching plugin (e.g., W3 Total Cache, WP Super Cache, WP Rocket), clear its cache from the plugin's settings.
  • Server-Level Cache: Contact your hosting provider to clear any server-side caching (like Varnish or Nginx fastcgi cache).
  • CDN Cache: If you use a Content Delivery Network (e.g., Cloudflare), purge its cache through its control panel.

2. Check for Other Redirect Sources

If clearing the cache doesn't work, the redirect may be coming from another source. The Redirection plugin's log can be a valuable tool here. Check the "Redirects" > "Log" section. If the "redirect_by" column says "WordPress," it indicates that WordPress's own internal functions are causing the redirect, not the plugin. Other common sources include:

  • Your site's .htaccess file (for Apache servers).
  • Other active plugins that handle SEO or security.
  • Your theme's functions.php file.
  • WordPress settings like a Site Address change or a page's permalink history.

3. A Specific Fix for Permalink Conflicts

As seen in one user's solution, a conflict with a page's permalink can sometimes cause a persistent redirect. If the problematic URL is redirecting to a specific page, try this:

  1. Move the target page to the Trash.
  2. Empty the trash to permanently delete it.
  3. Create a new page with the desired slug.
  4. This process often clears any lingering redirects stored by WordPress's rewrite rules.

4. For Extreme Cases: Manual Plugin Disable

If you are completely locked out of your WordPress admin area due to a redirect, you can manually disable the Redirection plugin via FTP or your hosting file manager. To do this, navigate to the /wp-content/plugins/ directory and rename the folder redirection to something like redirection_disabled. This will deactivate the plugin and allow you to log in again. The official Redirection support site provides detailed instructions for this process.

Conclusion

A redirect that continues after deactivating the Redirection plugin is not a bug in the plugin itself but a caching issue or a conflict with another system. By methodically clearing all caches and investigating other potential sources, you can identify and eliminate the persistent redirect. Always remember to test changes in a private browser window to get accurate, uncached results.

Related Support Threads Support