This is the tag I want to link to: https://pirateswithben.com/tag/command-the-oceans/
However, it redirects to a specific post that starts with the last part of the above URL. Ex: https://pirateswithben.com/command-the-oceans-10-13-2017/
I want the first link to work so all the posts with the “Command the Oceans” tag are displayed, not a specific post redirect.
This has not always been an issue, but has been reoccurring this year.
How can I fix it?
Thanks!
Hi, thanks for getting in touch.
Does the issue resolve if you temporarily change the published status of the command-the-oceans-10-13-2017 post to Draft?
Before doing that, I just checked the tag page again and it works fine: https://pirateswithben.com/tags/command-the-oceans/
Changing that post to a draft status keeps it working fine. I just don’t know why the tag oscillates between working and redirecting, seemingly at random. Sometimes I have to refresh my permalink settings to avoid page not found errors on other pages, but this seems unrelated to the occasions when I do that.
You can perhaps chat with your hosts about needing to save permalinks often. Perhaps they can check the appropriate error log file to see if anything related is coming up. I’m, unfortunately, not sure why the issue is intermittent. If the issue doesn’t persist with the 10-13-2017 post in draft status, then I might have suggested removing “command-the-oceans” from the slug entirely and then publishing to see if that helped.
Following up on this:
I think it’s related to whether or not there is an “s” after “tag”. When the URL has tags in it, it works fine. When it’s just tag, it does the redirect. I think perhaps there was a plugin update somewhere along the line that changed the URL structure of default tags, where some links got updated but old ones didn’t have the s and therefore redirected to a specific post.
I have a plugin “Post Tags and Categories for Pages” that hasn’t been updated in a year, so perhaps that was part of the issue.
Thanks for the help!
Hi, thanks for the update. Have you checked to see if the issue occurs with only SiteOrigin plugins activated?
No, but I don’t have any SiteOrigin plugins for the website. (assuming it’s the same four on the SiteOrigin homepage)
Thanks for the plugin information. Does the issue persist if you temporarily switch to a default theme like Twenty Nineteen?