At midnight tomorrow (that would be midnight following 29 October 2024, Central Daylight Time), we’ll be cutting over to the new shiny Ghost-based site instead of this old, busted WordPress one.
Not everything is finished, because some things are very hard and/or impossible to set up without it running on the proper domain name. (Which includes, sad to say, the Discourse comments, which while they will be the first thing that gets set back up post-cutover, won’t be there immediately.) There’s a featured post on the new site that tells you what’s on the list and what hasn’t been put there yet. Feel free to make comments on this post (and its parallel on the community site) if you think I’ve missed anything.
Rather than import the mess of the old tagging system and images, I’m going back through all the imported posts and adding nice clean tags and images to them. There’ll be another featured post telling you how far I’ve got.
Fortunately, links to posts should not be affected by this migration, as I’ve tweaked the routes configuration to make them all match up.
Okay. For those of you still awake, basic switchover is now done, and things seem to be working except for the things which I have not done yet, which obviously are not.
I’m going to get more up tomorrow, starting with the full Discourse comments integration, but that’s all for tonight as our guest corgi will be waking me at 5 am one way or another, so might as well get a quick nap in first.
Hello corgi! And good luck with the transition. Let us know when the switch is complete and we’ll unleash our walking unit test (ie the user aptly named “Buggy”).
(I was starting to think that having them unlisted was actually good, since having them embedded using Discourse native support generates a new topic for every single post, even the backlist, as those posts get visited.)
Okay, let’s do some science. I’ve changed that setting now - let me know if you still get more notifications without visible topics attached going forward.
I do! They’re pretty obviously transient though, they just look worrisome when they show up.
EDIT: possibly important clarification - they’re not notifications as in pings, they’re just messages at the top about how there’s like 18 updated topics.
Right. Well, bleh. Apparently that’s just how it works, although I’ll put it on the list to see if it can be avoided.
If not… well, it’s a sort-of self-limiting problem. These are all showing up today as people are browsing their way through the new site and hitting posts that don’t have a matching Discourse topic, so once someone’s looked at all 2,000-plus posts that don’t have those yet, this should stop happening!
(So, y’know, no problem in the long-term. Right? Right? )
So what we have here, gentles all, is that WordPress is too special to use the normal Discourse embedding support and instead the WP plugin for Discourse talks directly to the API and does its own damn thing.
Which manages not only to be incompatible with the normal embedding support but actually break it into the bargain.
I have not enough yay to fully express my feelings about this, but I’m sure new stocks will be arriving soon.
On the other hand, at least we now have e-mail blog subscriptions working.
)