If all goes well, very shortly you won’t see this post at all, and then you will, on a different blog in the same location.
It helps to stay awake! Really, here goes…
I just hate to see any links broken. Certainly not for long, even if it’s for the same of Google.
I also have a small client site update to do with static pages, which I am about to start so I can have it done and billed by Monday. That ought to get me a check by the end of the week, even if it’s small.
I’m going to regret being awake now, but apparently it was a bad idea to drink seven mugs of coffee during the course of Saturday. I was able to do very little on this with the kids, so hey, I can be a zombie for them and muddle through.
You may see less of a blip than I thought, if the migration works as I expect. Stay tuned…
The objective, which is supposed to be possible if moderately confusing, will be for any link to a post as it existed before to redirect automatically to the archived content.
I plan to attempt this tonight.
The goal is to work out the details on ours, so even if it’s undercooked tomorrow I know the technical hurdles, and then apply the knowledge to one I expect to do for another blogger tomorrow night.
During the surgery, you may find us down entirely for a while, or you may get an unexpected and incomplete site if you visit during the process. I’ll post in both places indicating it’s done and how it went, once it is done. Worst case, before I sleep tonight I will try to leave something in place that says what’s going on, even if the archive isn’t working yet and I have to continue with help from the kids during the day tomorrow.
Note to self… Good luck with that! It’s 9 PM. You just finished in the kitchen, have dishes soaking, have 3 kids to put to bed, and are going to start this from scratch when that’s all done? On about 5 hours of sleep and after more than 13 hours awake? Yeah, right…
There is a Kool-Aid flavor, which happens to be an especially good one, that has no color at all. They use that as a marketing coolness factor. Maybe there are other clear flavors, but the one we’ve had is kiwi watermelon, and we had another packet. I decided to make that the next one I made and to give the baby some, after reading the ingredients.
No. Reaction. Period.
If anything, he’s having an unusually calm day, except the runny nose in the morning from the diesel trains and/or honeysuckle or other growing things and/or wood smoke last night and/or dust. He barely even got itchy as he tends to when he was ready to sleep again. The itch sensation can cross and be confused with pain or unhappiness/discomfort, so he’ll itch, for instance, in response to tooth pain, gas pain, or emotional distress.
All he has had today has been a couple Club crackers, a piece of toast, and the clear Kool-Aid. He’s napping at the time I’d have offered him more to eat.
He drank a large quantity, too. When he steals Kool-Aid from the sisters, it can be little more than a sip to set him off, usually pretty quickly. It’s gotten to where we infer he’s gotten it by his reaction. I managed to keep theirs completely away from him, as they had the tail end of berry flavored blue Kool-Aid.
In a way, it’s onerous knowing that he reacts to at least two or three colors, but it’s also a relief to know and to be able to screen accordingly.
It doesn’t port unpublished posts, like some redacted ones from earlier this year. That’s fine.
The default is only 10 in the RSS. We have, after this post, 2251. Instead of 2249, Control Panel said we had 2030, so I used that number. If you removed the limit from the RSS template, you get 100. If you specify 2030, you get that, and actually the wait wasn’t that long.
A set that large hung at 349 when importing. That means either finding a way to specify a range in an RSS template, or systematically grabbing a smaller number and then deleting posts and then grabbing the next so many, and so forth.
No pictures came through. That may be a setting on the RSS template, allowing pictures to show in the feed. Never had reason to look at that.
We do full feeds, but presumably partial feeds wouldn’t work for this.
Multiple categories per post aren’t handled gracefully, turning into one long string and creating a new category like “kids pictures tv” in WordPress. Not sure there’s a way around it, but I think it might be wise to create matching categories in WP ahead of time either way. Might be possible to do a series of queries or replaces or something. Or just change every imported post to one category.
Apart from whatever URL customization is needed to make them match the old format, if desired, it appears to be a good idea to do the URL format setting to make them “pretty” before the import.
A small number of posts during the import, say one of every 30, claimed to have been imported previously. I thought it was a URL building problem with duplication, but I had it at the default where they end in numbers, so it may have been the way it identified each post during import.
I’m still intrigued and would like to know just what it takes, but it may be that the better part of valor is to archive the old blog, even if it means hacking .htaccess to redirect permalinks, and starting with a fresh one. We’d also considered that option.