rest_no_route error

  • Resolved mhartste

    (@mhartste)


    5 months, 1 week ago

    Hi Guys –

    Thanks for your plugin! It’s been working great for me for a long time, until I upgraded from v1.7.3 to v2.0.6.

    Now, when I click on the Rollback link, for any plugin, I get an error:

    rest_no_route
    No route was found matching the URL and request method.

    I’m on WordPress 6.4.3, PHP 7.4.33.4, on GoDaddy.

    Thanks!

    Mike H.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 22 total)
1 2
  • jbartel

    (@jbartel)

    5 months, 1 week ago

    Same error with v2.06 in WordPress v6.4.3 – previous WP ROLLBACK version worked perfectly. ERROR accures with every PLUGIN I’ve tried to roll back …

    rest_no_route

    Es wurde keine Route gefunden, die mit der URL und der Request-Methode identisch ist.

    • This reply was modified 5 months, 1 week ago by jbartel.
    • This reply was modified 5 months, 1 week ago by jbartel.
    iThemes

    (@ithemes)

    5 months ago

    I’ve seen a few reports, but I can’t reproduce it still without more information.

    It has to be either a plugin conflict (maybe a Security plugin blocking REST routes), a hosting issue, or a combination of the two.

    So, I’m not going to keep taking shots in the dark to fix it without access to an environment where it’s happening, and I can modify the code to debug it.

    Plugin Author Devin Walker

    (@dlocc)

    5 months ago

    Sorry, I was logged into the wrong account. This is my reply above. 👆

    Plugin Author Devin Walker

    (@dlocc)

    5 months ago

    I’m on WordPress 6.4.3, PHP 7.4.33.4, on GoDaddy.

    I actually have a Managed WordPress account on GoDaddy and just tested and did not receive any error.

    Thread Starter mhartste

    (@mhartste)

    5 months ago

    Thanks, Devin, for getting back to me.

    I created a test site. I deactivated absolutely every plugin on my test site except for WP Rollback v1.7.3. I upgraded WP Rollback to v2.0.6. Then I tried to roll back one of my (deactivated) plugins. I still get this error.

    I restored my test site with the older WP Rollback. I am using the Ocean WP Theme. I changed to use the Storefront Theme and upgraded WP Rollback. Again, WP Rollback fails with this error.

    How else can I narrow it down?

    Thanks for your help.

    Mike

    deeveearr

    (@deeveearr)

    5 months ago

    I’ve given up on waiting for a fix – WP Rollback has not worked on my website since the upgrade to version 2

    All of these ‘fixes’ though will eventually push the last working version out of the bed, so I’ve saved version 1.7.3 to my pc now.

    Plugin Contributor Matt Cromwell

    (@webdevmattcrom)

    5 months ago

    Hey folks, I did a little bit of digging on this error myself. It pops up a lot with any plugin that has custom REST API endpoints. The root cause seems to always be related to those endpoints not being created correctly or successfully. So something in your environment is preventing WP Rollback from creating those endpoints. Here’s what I’d do to troubleshoot this a little further:

    0. Ensure WP Rollback is on the latest version

    I know you’ve updated several times, and rolled it back as well, but in order for these next steps to work, start by having Rollback on the latest version.

    1. Install the “Disable REST API” plugin

    Install this plugin: Disable REST API

    It doesn’t just disable the REST API endpoints, it allows you to control all the REST API endpoints on your site per user role.

    2. Go to the Disable REST API settings page

    There you’ll see a dropdown to choose different user roles. It defaults to “Unauthenticated users”, which is fine for now. On this screen, just verify that you see a section for WP Rollback, it should say /wp-rollback/v1 like this:

    3A. If you DO see that section

    If you do see that section, ensure that when you toggle to the Administrator at the top of that screen, that all the WP Rollback endpoints are enabled.

    Then go to Settings > Permalinks and just resave permalinks again.

    Hopefully now you’re all set.

    3B. If you do NOT see that section

    If you don’t see that section, then we’ve verified that something in your environment is preventing WP Rollback from registering those endpoints correctly. I would reach out to GoDaddy about that, it’s most likely a security setting in your server settings.

    4. Further Reading

    Here’s several sources I found that pointed me at some of this info. I believe between the troubleshooting above, help from your web host, and these resources that you should be able to find and resolve the issue.

    Try that out, and let us know what you discover. I’m certain we can get to the bottom of this together. Thanks!

    deeveearr

    (@deeveearr)

    5 months ago

    Hey @webdevmattcrom

    I just tried your solution and it didn’t work, I’m afraid.

    Plugin Contributor Matt Cromwell

    (@webdevmattcrom)

    5 months ago

    @deeveearr – give me some details, what DID happen? Did you see the wp-rollback endpoint? Was everything enabled for Administrators?

    Then, as I said above, if it did NOT work then you need to contact your host. Did you do that? What did they say?

    Always looking for the next step and we can only get there with more information. Help me help you.

    deeveearr

    (@deeveearr)

    5 months ago

    hI, @webdevmattcrom

    Yes, I’d gotten the endpoints, but only a couple of them, nowhere near as many that are showing in your diagram.

    And yes, everything stayed enabled for administrators.

    Thread Starter mhartste

    (@mhartste)

    5 months ago

    Thanks, Matt, for your detailed response. Are you the Matt of Give?

    I contacted GoDaddy and I was told by Joe in Web Development of GoDaddy that the security server for WordPress.com in the USA has been down and has had intermittent problems sine 4-Feb-2024. Upgrades of WP Rollback since then have not been installed properly. The solution is just to wait for this security server issue to be resolved, which should happen on 7-Mar (tomorrow), then upgrade the WP Rollback plugin again.

    I will test it again tomorrow and update the ticket.

    Thanks,

    Mike

    Aleš Fizešan

    (@afizesan)

    3 months, 1 week ago

    Hi.

    Solution to the problem is simple:

    Navigate to Settings > Permalinks

    Under “Permalink structure” select “Post name”

    Save the page and navigate back to “Plugins” page

    Continue to successfully use the “Rollback” function.

    Cheers.

    Thread Starter mhartste

    (@mhartste)

    3 months, 1 week ago

    Thanks, @afizesan, for your brilliant suggestion.

    It works, but it causes another problem. But can you explain why this change allows the WP Rollback plugin to work?

    The problem this change introduces, however, is that it changes my URL structure. Instead of my pages being style /mysite/?page_id=nn, they are now style /mysite/page-title. I have a lot of external pointers to various pages in my site which will no longer work. And there is a security exposure with this style — for blog posts, the poster’s username is embedded in the URL name, exposing the usernames. This is why I originally switched to the page_id style.

    Is there some way for the WP Rollback plugin to continue to work with my page_id URL style, like it used to in v1 of WP Rollback?

    Thanks!

    Mike

    Plugin Author Devin Walker

    (@dlocc)

    3 months, 1 week ago

    Hey @afizesan – thanks! Now, I can reproduce the issue. I’ll have a fix out for this soon.

    I wasn’t sure what the issue was… but now that you mentioned the plain permalink structure, it all makes sense. I can’t believe I didn’t figure that out before… thanks again!

    Plugin Author Devin Walker

    (@dlocc)

    3 months, 1 week ago

    Hey All,

    Version 2.0.7 is live and should resolve the issue. Please let me know if you have any more concerns or issues!

Viewing 15 replies - 1 through 15 (of 22 total)
1 2
  • You must be logged in to reply to this topic.