This problem is not going away, and it doesn't appear to be server specific either.
I can reproduce it at will too. I can post to this blog. On another blog, where I have administrative access, and COULD post, I get a 450 when posting.
When I try to mirror my "test" blog (it's not really a test blog, and my friend doesn't think so either), using HTTrack, I end up with the same problem that's being seen online.
I can go into the Dashboard for my friend's blog, and I can see all of the posts there. Including the ones omitted in #2 above.
I just created a new post, and when I tried to publish it, it came back with the dreaded
BUT - I can publish THIS at will.
Here's an interesting question, that came up during the writing of this article. Why am I involved here? My blog is fine.
I see Blogger really is working on the problem. Finally.
But it would be good if they had posted that yesterday, before this got started. I can't stop now, and I won't.
>> Top
I can reproduce it at will too. I can post to this blog. On another blog, where I have administrative access, and COULD post, I get a 450 when posting.
When I try to mirror my "test" blog (it's not really a test blog, and my friend doesn't think so either), using HTTrack, I end up with the same problem that's being seen online.
- The sidebar is truncated halfway thru its content.
- Posts are missing from the display.
- Looking at the download log, I see numerous entries
Warning: file not stored in cache due to bogus state (incomplete type)
which I'm pretty sure correspond to the missing posts (#2).
I can go into the Dashboard for my friend's blog, and I can see all of the posts there. Including the ones omitted in #2 above.
I just created a new post, and when I tried to publish it, it came back with the dreaded
450 Write error: No space left on device
001 java.net.SocketException: Connection
resetblog/20/43/11/troublealwayshasadoor/archives
/2006_03_01_troublealwayshasadoor_archive.html
BUT - I can publish THIS at will.
Here's an interesting question, that came up during the writing of this article. Why am I involved here? My blog is fine.
I see Blogger really is working on the problem. Finally.
But it would be good if they had posted that yesterday, before this got started. I can't stop now, and I won't.
>> Top
Comments