• Resolved neotrope

    (@neotrope)


    Hi, folks; weird confluence of events having to do with retiring all /AMP /?=amp and /?print=pdf trailing links, recent WordPress update, etc.

    We are getting a redirection loop on certain post slugs when the word ‘champion’ or today ‘campaigns’ as part of slug.

    A post slug like /wire/my-story-ends-in-campaigns

    would start a redirect loop unable to load page to

    /wire/my-story-ends-in-ca

    Slugs with ‘champions’ would die after ch

    like wire/my-story-with-champions-in-training

    would go to a loop of

    wire/my-story-with-ch/

    SO: I have tried disabling any existing regex or redirects, including security stuff to kill requests to WP admin stuff, turned off mod_pagespeed, restarted Apache, PHP, Nginx, cleared redirects in Redirection plugin, reinstalled Redirection and imported WP internal redirects and cleared them, and still getting this weirdo thing. I even cleaned out some leftover stuff from the PHP plugin in the database, removed all drafts in dbase (which I limit to 3).

    Absoultely no idea how to debug this? Is there anything in the Redirection plugin that can track “redirect errors” ? Totally stumped.

    I realize this is no fault of your plugin, but ironically trying to manage redirects and suddenly the past couple of weeks have this weird thing I can’t sort. Thanks for any feedback or suggestion.

    ((NOTE: not an issue with my browser cookies, as not browser related; not an issue with SSL as dedicated server, dedicated IP, and now using Let’s Encrypt certs which are generally bullet proof.))

    • This topic was modified 6 months ago by neotrope.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Godley

    (@johnny5)

    If Redirection is involved then it will show redirects in the log. Otherwise Redirection is not involved.

    It’s possible to configure Redirection to monitor other redirects within WordPress (see the options page), but not redirects outside of WordPress.

    Thread Starter neotrope

    (@neotrope)

    Ah! Of course; I’ll enable that option to see if I can ‘catch’ what the heck is going on with that. Thanks!

    Thread Starter neotrope

    (@neotrope)

    okayyyyy,,,,, well, human error (of course). Looks like we had an htaccess file inside the sub-folder for news platform, in addition to htaccess file outside the folder, and there was duplicate 301 redirect for /amp and /?amp=n stuff, with different format, and potentially WRONG filesmatch string vs better regex version. So, looks like posts with certain words were trying to redirect to an amp page then redirect from amp page to non amp page, or somesuch. Doh.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bizarro Redirect Issue’ is closed to new replies.