Blogger.com is always painful

Blogger.com managed to get itself blocked by my ISP — again. The problem is that even though the authorization credentials are wrong, blogger.com keeps trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and trying and eventually gets itself blocked.

That's a pain. I have to open a ticket and, with cap in hand, ask my ISP to please unblock the marauding googler.

My blog is back up, and I have successfully (?) moved my web service to a new server. Mail is being done incrementally, but we expect no interruption in service. (Hear that Mr. Murphy?)

Labels: blogger

0 comments

Publishing your blog is taking longer than expected.

Blogger.com goes spastic now and again. For the last few days, I have been unable to (re-)publish this blog, due to a mysterious "Publishing your blog is taking longer than expected." After that, I get a twitchy "Your blog published with errors." page without mention of what the particular errors are.

Needless to say, this has all been working for years without change.

I fixed the ftp path – somewhere was a mention that it must not be absolute. It had to be changed in several places for the blog pages, the atom and rss files and the blog archives. I had to keep clicking that "To continue waiting for it to finish, click here" link, but it still didn't work.

Some sort of error message sure would be helpful.

Meanwhile, I am about to give up on this ftp stuff and have blogger host the blog itself. I'll have to do a little magic to make it integrate nicely with the site, but how hard could it be?

Labels: blogger

0 comments