Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
A client of mine has imported some redirects into SEO Checker. One has sneaked through which is incorrect, but doesn't appear in the list of redirects so it's not possible to edit it. Re-adding the redirect doesn't work as it's recognising it as a duplicate: "The old url already exists in the database, you can only specify the old url once". So basically, there's a rogue redirect rule in there which is not accessible to be edited/deleted nor added again.
Time is against me on this in terms of tracking down how this happened, but I wanted to patch up the reference manually so I'm trying to find out where these items are saved. It doesn't seem as if there's a database table for this.
Thanks for any pointers.
Actually, the redirects do seem to be stored in the db, in the 'SEOChecker_PageNotFound' table.
I've also found the bug I think. It seems that the node selected to redirect to was deleted as the node id in the table was '-1', which seems to render that redirect rule inaccessible. It seems there should be some way to cater for this in the interface to let the user know they've deleted the redirect destination node and to allow the user to edit this.
The deletion of the node may actually not be what's causing the -1 node id. I tried editing the redirect through the SEO Checker admin interface as even though the rule seems correct in the database now it is 404'ing rather than redirecting, so I changed it from using the content picker as the redirect to using a URL, and that caused the node id to change back to -1 and the item again disappeared from the list of redirects in the CMS. Setting the node Id back to a sensible number brought it back, but the redirect on this rule still doesn't do anything other than 404.
Sorry to hear you are having issues. I can reproduce the error with changing from picker to normal url. I assume you are using 1.5.2 on V7? I will fix this and post a link here.
Still curious why the normal picked item wouldn't redirect properly. Could it be that there is an entry in the database with column Ignore set to true?
Fixed the issue redirect disappearing when you deselect the node and add a hard coded url. If you can run the installer then that should be fixed. Still curious about the duplicate redirect.
Thanks Richard - so I need to install this package over the top of the current one?
I'll try to get to the bottom of why this one rogue node still isn't working and will report back if I establish a cause.
Yes just install over the current one. Installer takes care of the update. Looking forward to hear what happened.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted