upgrading to 1.9.3 causes /news/* to /news-stories/* redirect loop error

Hello! Thanks for creating this fab and highly useful plugin. We just ran into some trouble when upgrading to version 1.9.3. Downgrading to version 1.9.2 made the problem go away. Hopefully this report will give you some information to help you pin it down so we can upgrade again, or point to troubleshooting steps we are missing on our end to identify a problem specific to our site. Let me know if you have any questions or need any details.

I can replicate this on my site by upgrading to 1.9.3 and creating 301 redirect /news/* to /news-stories/*. We also have similar redirects e.g. /stories/* and /blog/* that redirect to /news-stories/* – the goal is to have the landing page, taxonomy pages and posts redirect to /news-stories/ path and display correctly.

In 1.9.3, the redirects work fine for /stories/* and /blog/* but not for /news/*. Unfortunately, when the /news/* redirect is created, the /news-stories/ landing page crashes with a “redirect loop” browser error. The URL changes to SITE/news-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/-stories/

Intriguingly, changing the redirect to /news/* to /* takes you to SITE/-stories.

I was able to replicate this bug on my staging site, with the default wordpress theme. So it is not related to my custom theme.

An issue with troubleshooting I was able to overcome is that chrome caches the new link for 301 redirects so even if it’s fixed in wordpress the problem is still exhibiting in the web browser. The fix for this is to open devtools and disable caching, and sometimes to resort to opening new browser windows.

Thanks for your attention! ??