Dammit gocomics and Google.
Concerning gocomics:
It seems that a number of strips, including the ones I was just coming up on, currently display graphics stating "This comic is currently unavailable check back soon." At this time this includes comics for Fabruary 9-12, 1954, as well as the 14th, the 18th, the 20th and the 22nd. There may be others too.
In fact, the paragraph I just gave you us slightly out of date. That was yesterday, which I couldn't post because Blogger was down. Now the strips in question don't even show the error image. Just navigation elements. See for yourself.
I think I know why. When I was looking through these strips before, I noticed that a few of them had been poorly cropped. Specifically, there were three or four strips in the same image, I seem to remember noticing they were like that back at comics.com.
I was all set to remark upon the problem when I got up to it, but what do you know, they seem to have found it just about the moment I got up to them. I wonder if anyone at Universal reads this blog? A pleasing, and yet unsettling, thought.
I'm going to hold off on discussing those strips to see how quickly gocomics fixes the problem. (I could get them from Other Sources, but let's give them a week to fix it themselves, it's not like it should be a particularly hard thing to correct.) There are some interesting strips affected so I'm loathe to skip them for long.
Concerning Blogger:
You'd think that Google themselves would know something about site reliability, but geez. Blogger was down all of yesterday, and there was a worry that some posts would be lost. That doesn't seem to have happened, at least in my case, but the outtage is the reason there was no post yesterday.
Showing posts with label blogger. Show all posts
Showing posts with label blogger. Show all posts
Friday, May 13, 2011
Wednesday, November 11, 2009
META: More on the Image Break
I have figured out a way to fix all the links in one fell swoop. However, it is fairly drastic mojo. It will likely remove any flags (funny, cool, interesting, etc) that have been set on posts. Trial runs have indicated that it probably will not erase comments, but it might result in some strange feed behavior. I am not doing it immediately, but will probably do it in the next few days.
For those of you interested in what this entails....
A quick Google search didn't turn up many promising avenues. An Ask Metafilter thread from 2005 said it might require hacking the Blogger API to implement changes of this magnitude.
It turns out that it doesn't require going quite that far. It is possible to export all of the posts of a Blogger blog into an XML file, and then import it later either to the same blog or a different one. While it is on the local machine passing it through a quickie Python script easily fixes the links, once I get the old URL format solidly recognized (for the record, Comics.com's new URL system is rather simpler than the old one). It turns out that even comments get exported to the archive file.
The problems arise from the fact that, while I can restore the blog posts to a new blog then change its address to match the old one, not all of the old blog's settings get restored. The kinds of issues this produces ranges from minor (having to reupload the banner) to somewhat harsh (anyone following the blog will have to refollow).
The alternative is to delete all of the posts on the current blog and reimport them from the hacked backup. This should be safe since I have the blog backed up. It will keep all of the settings and followers, but I don't know if it will do something nutty like resend all of the pages as new RSS entries.
Will probably take action on this in a day or two.
For those of you interested in what this entails....
A quick Google search didn't turn up many promising avenues. An Ask Metafilter thread from 2005 said it might require hacking the Blogger API to implement changes of this magnitude.
It turns out that it doesn't require going quite that far. It is possible to export all of the posts of a Blogger blog into an XML file, and then import it later either to the same blog or a different one. While it is on the local machine passing it through a quickie Python script easily fixes the links, once I get the old URL format solidly recognized (for the record, Comics.com's new URL system is rather simpler than the old one). It turns out that even comments get exported to the archive file.
The problems arise from the fact that, while I can restore the blog posts to a new blog then change its address to match the old one, not all of the old blog's settings get restored. The kinds of issues this produces ranges from minor (having to reupload the banner) to somewhat harsh (anyone following the blog will have to refollow).
The alternative is to delete all of the posts on the current blog and reimport them from the hacked backup. This should be safe since I have the blog backed up. It will keep all of the settings and followers, but I don't know if it will do something nutty like resend all of the pages as new RSS entries.
Will probably take action on this in a day or two.
Subscribe to:
Posts (Atom)