All matched targets lost

  • Resolved kay3647684

    (@kay3647684)


    1 month, 3 weeks ago

    After updating the plugin to either version 5.7.1 or 5.7.2 (not sure when the problem started occuring), all redirects added through the plugin have lost their matched target and are now sending those URLs to a 404. Trying to add and save the matched target doesn’t take effect – after saving the matched target field remains empty.

    Current plugin version: 5.7.2
    WP version: 6.9.1
    Match type: URL and server

    The website has hundreds of redirects. There has to be a way to restore them without doing it manually.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author John Godley

    (@johnny5)

    1 month, 3 weeks ago

    The redirects still have their matched targets and will continue to operate, it’s just the form that doesn’t show it (unless you save over it). I will release a fix for that.

    Thread Starter kay3647684

    (@kay3647684)

    1 month, 3 weeks ago

    Thanks for the reply.

    Unfortunately, the URLs do not work. All of the URLs that were supposed to be redirected now return a 404.
    Reverting back to a 5.6 version helped, in that you can now add a matched target and it will save and work, however, all the target redirect remain purged, so they needed to be re-added manually. That means hundreds, maybe thousands of URLs for us.

    Plugin Author John Godley

    (@johnny5)

    1 month, 3 weeks ago

    That doesn’t make a lot of sense as the problem isn’t one that could go and update the underlying data. If you can send me the wp_redirection_items table I will take a look and see (export from your database, contact details in the plugin).

    Thread Starter kay3647684

    (@kay3647684)

    1 month, 3 weeks ago

    UPD 2.

    With some further testing, the rollback seems to have restored the redirects.

    Following up on your response. I am now having second thoughts that there was some inside tampering, and I was just unlucky choosing the URLs whose redirects were removed manually, but if you could check that for further updates, we would be very grateful.

    Plugin Author John Godley

    (@johnny5)

    1 month, 3 weeks ago

    The underlying problem should be fixed in 5.7.3

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.