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

Why Your Redirection Plugin Isn't Working: Common Issues and Solutions

44 threads Sep 7, 2025 Plugin → Redirection

Content

Understanding and Fixing Common Redirection Plugin Problems

The 'Redirection' plugin for WordPress is a powerful tool, but like any complex software, it can sometimes behave in unexpected ways. Based on community reports and troubleshooting discussions, here are the most common issues users face and how to resolve them.

1. The Dreaded Redirect Loop

Problem: You set up a redirect, but it creates an infinite loop, resulting in an "ERR_TOO_MANY_REDIRECTS" error.

Why it happens: This typically occurs when multiple redirects conflict with each other. WordPress's own redirect_canonical() function might be automatically redirecting a URL, and then the 'Redirection' plugin tries to redirect it again to a different destination. Other plugins or server configurations might also be creating conflicting redirects.

Solution:

  • Identify the loop: Use an online tool like Redirect Li to trace each hop of the redirect chain and see where the conflict originates.
  • Check for conflicts: Temporarily disable other redirect-related plugins or review your server's .htaccess file for rules that might be interfering.
  • Adjust match type: In the 'Redirection' plugin settings, try changing the match type for your rule to "URL only" instead of the default "URL and server."

2. Cache Conflicts

Problem: You create a redirect, but it doesn't work until you clear your site's cache.

Why it happens: Caching plugins (e.g., WP Fastest Cache) or server-level caching serve old, stored versions of pages. If a page was cached before you created the redirect, the cached version will be served without triggering the new redirect rule.

Solution:

  • Clear all caches: After creating or modifying a redirect, clear your WordPress cache, browser cache, and any server-side cache.
  • Reconfigure caching: Some users have reported success by excluding certain file types or the 'Redirection' plugin's logic from their caching rules, particularly on Nginx setups.

3. The Mismatched URL (Trailing Slash and Case Sensitivity)

Problem: A redirect for /page doesn't work, but a redirect for /page/ does.

Why it happens: The plugin's matching is exact by default. A source URL of /add will not match a request for /add/ unless the "Ignore trailing slashes" setting is enabled.

Solution:

  • Be precise when entering your source URL. If your old page was /old-page/, include the trailing slash.
  • Enable the "Ignore trailing slashes" option in the plugin's settings under Settings > Redirection > Groups to make matching more flexible.
  • Pay attention to the "Ignore Case" option when creating your rule if capitalization might be an issue.

4. Import and API Issues

Problem: Redirects imported via CSV don't work, but manually creating the exact same rule does. Or, using the API creates a redirect without a target.

Why it happens: CSV formatting can be tricky. A hidden space, incorrect column order, or improper encoding can cause the import to fail silently. For the API, the issue is often an incorrectly formatted JSON payload.

Solution:

  • Check your CSV: Ensure your file has only two columns (source and target) with no headers. Avoid blank rows. Open the file in a plain text editor to check for hidden formatting characters.
  • Check the API payload: The most common API error is malformed JSON. Ensure your request correctly sends the action_data parameter with the target URL. The example payload in the threads shows a successful format.

5. The .htaccess File Isn't Updating

Problem: You've added redirects to an Apache group, but they are not written to the .htaccess file.

Why it happens: This is almost always a file permissions issue. The WordPress application does not have write access to the .htaccess file.

Solution:

  • Connect to your server via FTP/SFTP and check the permissions on the .htaccess file. It typically needs to be 644 or 664.
  • Confirm the file path the plugin is using is correct. The path is usually found in the plugin's Support tab.
  • If the file can't be written to, you may need to manually add the redirect rules to your .htaccess file or contact your hosting provider to adjust the permissions.

General Troubleshooting Steps

If you encounter an issue, always start with this checklist:

  1. Clear all cache: WordPress, browser, and server cache.
  2. Check for conflicts: Temporarily disable other plugins to see if the issue resolves.
  3. Review the redirect log: The 'Redirection' plugin has a logging feature. Enable it to see exactly what URL was requested and which redirect, if any, was matched.
  4. Double-check your settings: A small typo or a mismatch in trailing slashes is the most common cause of a failed redirect.

By methodically working through these common problems, you can usually identify and fix why your 'Redirection' plugin isn't working as expected.

Related Support Threads Support