Conversation
supportWe occasionally edit an existing post and then schedule that update to be published at a future time. This is typically creating 404 errors upon publishing. It doesn’t happen with content that has never been previously published – only updates of existing content. Interestingly, the post is live on our blog loop but the link results in the 404. The titles of the posts are being changed (e.g. 10 ways to 9 ways or something like that). Not sure if that’s causing an issue.
I’ve been able to dig into this a bit more and it seems like a BIG ISSUE. What I’ve determined is that if a custom permalink has been set for a blog post (we have the Custom Permalinks plugin installed), then when the post is scheduled for an update the original URL results in a 404 until the update is published or deleted. I went back to old posts with the default URL, and things went as expected. I then went back to those same old posts, updated the permalink to something new, scheduled an update and the 404 happened until the update was published. This makes the plugin unusable for us, possibly for others using that plugin as well (I’m thinking it’s an issue with that specific plugin although perhaps it’s a broader issue that would impact *any* custom permalink).
I’m not familiar with the Custom Permalinks plugin, but as far is I can see from quickly skimming through the code it uses the wp_postmeta table to save the custom permalinks. tao-schedule-update simply copies all postmeta for each post in order to create a 1:1 copy of the original. You need to contact the developers of the Custom Permalinks plugin to have them ignore any post that is set to a non-builtin status.
I’ve been able to dig into this a bit more and it seems like a BIG ISSUE. What I’ve determined is that if a custom permalink has been set for a blog post (we have the Custom Permalinks plugin installed), then when the post is scheduled for an update the original URL results in a 404 until the update is published or deleted. I went back to old posts with the default URL, and things went as expected. I then went back to those same old posts, updated the permalink to something new, scheduled an update and the 404 happened until the update was published. This makes the plugin unusable for us, possibly for others using that plugin as well (I’m thinking it’s an issue with that specific plugin although perhaps it’s a broader issue that would impact *any* custom permalink).
I’m not familiar with the Custom Permalinks plugin, but as far is I can see from quickly skimming through the code it uses the wp_postmeta table to save the custom permalinks. tao-schedule-update simply copies all postmeta for each post in order to create a 1:1 copy of the original. You need to contact the developers of the Custom Permalinks plugin to have them ignore any post that is set to a non-builtin status.