I had two posts scheduled on one of my blogs (see image). “Workism, AI and Vocation” was originally scheduled for 8/12, but I changed it to 8/13 (as in the image) when I decided to schedule “Tech Sucks! Victim in Denial!” for 8/12.
This morning, both posts were published. Seems that changing the scheduled date for “Workism, AI and Vocations” was ignored.
@manton Well this issue just got more interesting. The system double-published one of the posts on my site. This is the post I had originally re-scheduled for today:
IOW — it appears when I changed the scheduled date the system created a second copy of the post. Of course the URLs are different because the date is different.
Unfortunately, I didn’t take a screenshot of the posts page yesterday, but it had the 12th for the post. And today it has today’s date - not showing the duplicate:
I just realized… This explains another glitch. When the post was published yesterday it didn’t have a comment box on it. Today’s post does have a comment box.
Here’s a bigger problem: even if I want to, I can’t remove yesterday’s post, since it is no longer showing up in the posts lists.
But, to make things more complicated: there are comments and upvotes associated with yesterday’s post via Bubbles.town which would lose their links if I remove it. And, today’s post also already has upvotes on it.
This is now a proper mess.
This won’t solve your problem without tweaking my code for your site, but I built my own way of dealing with exactly this problem for my micro.blog site, and not just in this case, but also my migrated posts. It’s all using some special Hugo helpers and JavaScript.
My theme is open-source, I hadn’t shared it out yet because it’s still under a lot of dev. Someday I’ll make this a separate plugin, but in order to do that I have to unwind how it works for me specially first.
For now, I have a custom comment.js that might help. It renders a custom web component when your post includes a special replies tag:
{{< replies threads="https://…" mastodon="https://…" bluesky="https://…" >}}
And if you have multiple posts, you can just separate their links with commas.
{{< replies mastodon="https://fedisite.example/@poster/link/1,https://fedisite.example/@poster/link/2" >}}
The threads functionality uses a custom server function, so if you did want to reuse some code you’d have to strip that out, and the way likes work also depends on my hosted server, but at its core it can work without them.
You can see the multi-link function in action here for a threads post: the yak is back - birdwatching
The core problem here, I think, is in the micro.blog editor. When I changed the scheduled time for a post it created a new copy of the post on the path for the new date, however the original post wasn’t removed from the old path.
Why this broke the conversation.js script I don’t have the foggiest clue, as it’s just being called with the permalink for the post, which I think was still valid.
I don’t really want to stray away from using micro.blog’s standard converstion.js script. It’s more than adequate for my needs. If @manton decides to add threading into it at some point, that would be nice. But it’s not something I need.
I suspect this might not have happened if I had done a full site rebuild after I changed the schedule date. But, I didn’t know that at the time.
@manton So, as I mentioned in my comment to @codybrom above, a full-site rebuild removed the original copy of the post. So, in essence, it looks like it was orphaned when I changed the scheduled date.
I’m guessing I am the first person to report this issue… But it doesn’t sound like an edge case to me. It seems it’s something that could happen if more people were scheduling multiple posts at a time and wanted to move them around.