• Resolved markmacallister

    (@markmacallister)


    I am running 11.4.2 of this plug-in and have done so for a long time. However, when I updated to WordPress 6.1 today, it appears to have broken my site. I was getting a “page not found” error on every single page of the site. When I de-activted this plugin, the error went away and I was able to access pages without any problems. Is there a compatability issue with the plugin?

    Thanks!

Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    Hi Mark (I guess),

    that’s weird, sorry for that. I’ve tested the plugin with the release candidate of WP 6.1 about one week ago without any problems. Besides, it also works well on all my sites with WP 6.1. There seems to be a conflict with the theme or another plugin. Please follow this checklist https://petersplugins.com/please-follow-these-simple-steps-if-you-have-any-problems-with-one-of-my-plugins/ and keep me informed about the results. I’ll do my best to fix that.

    Regards,
    Peter

    Same thing on my site. Nothing shows up on the homepage with an error message (below) that the page is missing (that’s how I narrowed it down to your plugin). Also, when I preview articles, I get this error message generated by the custom 404 error message:

    “Sorry, we can’t find what you’re looking for!
    You’ve landed on a URL that doesn’t exist and it’s probably our fault.”

    Once I disabled it, the issue went away. Hate to not have this working! Keep us updated on a fix or maybe suggest an alternative.

    • This reply was modified 2 years ago by Boston Tom.
    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    Same problem – same answer. Please try to figure out what causes the problem by following the checklist. If you can tell me what is causing the problem, I’ll try to fix it as soon as possible.

    Sorry for the inconvenience, but as said before it worked in my tests and it works fine on all my sites.

    Regards,
    Peter

    quirecleveland

    (@quirecleveland)

    I experienced the exact same problem (and resolution) as @markmacallister. Changing to a WordPress default theme did not have an effect (the problem still existed). No other plugins caused a problem (they were all deactivated and reactivated to isolate the source of the problem). I could not find any discussion in the WordPress forums of this problem occurring globally with the update to WordPress 6.1.

    It’s a handy plugin, so it would be great if you’re able to fix it.

    Thanks!

    Kees Lamper

    (@keeslamper)

    I’ve the same problem on 2 client websites where the plugin is used.

    I tried your checklist on both the sites, and your plugin seems to be the one causing the 404.

    Hi Peter,
    I also have the plugin installed on a different site I manage that uses a different theme and have no issues. On the site where the plugin doesn’t work, I can’t turn off and on plugins as you suggest as it’s a heavily trafficked site and some of the plugins will lose their default settings upon deactivation.
    I’ll look into plugins that also modify URLs, as the only difference between the two sites is the problematic site uses Cloudflare with WP Rocket and the non-problematic site uses WP Rocket (no cloudflare). The problematic site also uses AISEO while the non-problematic site uses Yoast.
    Turning either of these plugins off is hugely disruptive as the site would literally go offline, the cloudflare cache would have to be deactivated (I emptied it but it didn’t fix the issue), and so on.
    Cheers.

    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    Many thanks to everyone who helps to find the cause of the problem.

    Unfortunately, I haven’t been able to reproduce the problem yet. That’s really frustrating. I just installed a fresh copy of WordPress 6.1 on a test system and tested it with the themes Twenty Nineteen, Twenty Twenty, Twenty Twenty-One, Twenty Twenty-Two and Twenty Twenty-Three. No problems.

    Which PHP version are you using?

    Regards,
    Peter

    Kees Lamper

    (@keeslamper)

    Both 7.4 and 8 / 8.1.

    Thread Starter markmacallister

    (@markmacallister)

    Greetings Peter:

    Thanks for your hard work. For what it’s worth, my site runs PHP 7.4.33 and uses Kadence Virtue theme. The Virtue theme includes an extension that allows me to specify a custom 404 page. I disabled that extension while I was using your plugin, but perhaps there’s a conflict there?

    Best,

    Mark

    Hi Peter,
    I’m running PHP 7.4.32 (which I got from under Tools > Site Health > Info) on both sites. One is having no issues, but the other is. The one having issues is using a different theme but by the same company. Cheers, Tom

    quirecleveland

    (@quirecleveland)

    Hi Peter,

    I’m running 7.4.32.

    Happy to help with whatever information I can provide. Thanks for working to get this working for us!

    Beth

    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    I’m one step further. Seems that it is not caused by a certain PHP version.

    Thankfully, a user of the plugin gave me access to a website where the problem exists. I cloned the site and can reproduce the problem with the clone.

    Now I can start research… I do my best.

    Thank you all for your patience.

    Regerad

    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    Is Compatibility Mode activated?

    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    I still don’t really understand exactly what has changed in WordPress, but I think I’ve found the reason for the problem.

    To speed things up, I packed and released a new version 11.4.3 right away. I hope this solves the problem.

    Please test.

    Regards,
    Peter

    quirecleveland

    (@quirecleveland)

    It works for me! Thank you for your work to resolve this!

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Plug-in appears to site after WordPress 6.1 update’ is closed to new replies.