A few bloggers in the MidWest USA region - apparently AT&T DSL customers - are reporting inability to access Blogger, Blog*Spot, and in some cases, various Google services.
We have a Problem Rollup question in Blogger Help Forum, where the epidemiology of the problem is being explored.
For right now, if you are affected by this outage, please use a proxy server to access all Blog*Spot blogs. And read BHG Resources: My Blog Is Gone, or [FAQ] I Can't See My Blog. What Should I Do? for insight into diagnosing this problem.
(Update 10:00 3/28): This problem has been resolved.
>> Top
Showing posts with label Problem Resolved. Show all posts
Showing posts with label Problem Resolved. Show all posts
Friday, March 26, 2010
Thursday, September 18, 2008
Strange Behaviour By Post Editor #2
Mindful of the volume of complaints seen in the forums today, I'll see if this post can be published.
Having tested in my previous post, it appears that posts can be updated. Now, we'll verify that new posts can be created. (1) Looking good, so far. (2) Test 1 was successful. (3) Test 2 was successful, and the updates show in the published post. And this post is visible in Edit Posts. (4) And test 3 was successful. (5) And so on. Back to work, now.
>> Forum thread links: bX-*00083
>> Copy this tag: bX-*00083
>> Top
Having tested in my previous post, it appears that posts can be updated. Now, we'll verify that new posts can be created. (1) Looking good, so far. (2) Test 1 was successful. (3) Test 2 was successful, and the updates show in the published post. And this post is visible in Edit Posts. (4) And test 3 was successful. (5) And so on. Back to work, now.
>> Forum thread links: bX-*00083
>> Copy this tag: bX-*00083
>> Top
Wednesday, September 17, 2008
Strange Behaviour By Post Editor
Normally, when I publish a post, I'll re publish repeatedly, to get the right content. For this post, I won't be doing that.
I just spent 1/2 hour updating another post, Another blog is already hosted at this address. I had to copy and paste some changes, from the published copy to Post Editor, when revising other changes. Here's what I did, initially.
Other bloggers claim that AutoSave doesn't work either.
And some claim problems with the posting date / time.
>> (Update 9/20 8:00): Last night, Prashant declared this episode to be over.
>> (Update 9/19 12:00): A Blogger Employee has (finally) posted a pinned thread, with a possible workaround.
>> If you're still experiencing this problem, try clearing both cache and cookies, and restarting the browser. Or, try using a different browser for your editing.
>> (Update 9/18 13:00): A Blogger Employee is now asking for diagnostic details.
>> (Update 9/18 8:00): The problem is not 100%, and it's not consistent. I'm able to post here, now. (1) And, having posted and verified the post, I can edit and see my immediately previous change. (2) And I can correct and annotate the previous change, too. (3) And so on. (4) And now we see 4 posts in a 10 minute span of time, and no loss of updates. (5) Looks like I, at least, am back in business. (6) And see my subsequent tests, too.
>> Forum thread links: bX-*00083
>> Copy this tag: bX-*00083
>> Top
I just spent 1/2 hour updating another post, Another blog is already hosted at this address. I had to copy and paste some changes, from the published copy to Post Editor, when revising other changes. Here's what I did, initially.
- Start Post Editor.
- Make changes to an existing post.
- Publish the changes.
- Verify the changes in the updated post.
- Go back to Post Editor to revise the changes.
- The changes just made are gone.
Other bloggers claim that AutoSave doesn't work either.
Your request could not be processed. Please try again.
Auto Save failed.
And some claim problems with the posting date / time.
when i post the time it is wrong and doesn't change. keeps showing 12.08.
>> (Update 9/20 8:00): Last night, Prashant declared this episode to be over.
Recently, some of our users reported problems with editing, publishing and auto saving posts. We have released a fix which should prevent this from happening.
>> (Update 9/19 12:00): A Blogger Employee has (finally) posted a pinned thread, with a possible workaround.
Clear your browser's cache but do -not- clear your cookies.In the process of adding this update, I note that my Post Editor shows very old contents for this post. Moving to another computer, I am able to update the current copy of my post. (1) But, to annotate the update, I have to move to yet a third computer. And I must note that the second computer is NOT typically used for composing or editing posts, so having a Post Editor article in cache there is not a possibility. And now, I am out of computers. I suspect that I will have to cease updating this post.
>> If you're still experiencing this problem, try clearing both cache and cookies, and restarting the browser. Or, try using a different browser for your editing.
>> (Update 9/18 13:00): A Blogger Employee is now asking for diagnostic details.
could you tell me the URL of the blogs you're experiencing this problem with, what Operating System (e.g. Windows XP) you're using, what Web browser you're using (e.g. Firefox, Safari, Internet Explorer), and what country you're in.
>> (Update 9/18 8:00): The problem is not 100%, and it's not consistent. I'm able to post here, now. (1) And, having posted and verified the post, I can edit and see my immediately previous change. (2) And I can correct and annotate the previous change, too. (3) And so on. (4) And now we see 4 posts in a 10 minute span of time, and no loss of updates. (5) Looks like I, at least, am back in business. (6) And see my subsequent tests, too.
>> Forum thread links: bX-*00083
>> Copy this tag: bX-*00083
>> Top
Saturday, June 28, 2008
Line Spacing And Pre-Formatted Blocks
I use "<pre> ... </pre>" blocks in my posts a lot, as a way to highlight code examples and log outputs. Unlike blockquotes, preformatted blocks preserve indentation in the material highlighted, and with both code and log listings, indentation (horizontal spacing) is as an important part of the display as is line spacing (vertical spacing).
Earlier this month, I showed how the corrected (finally!) vertical line spacing issue had been corrected, and how easily you can tweak the line spacing for elements like pre-formatted blocks. At that time, vertical line spacing for pre-formatted blocks was predictable, and could be tweaked. Since that time and just before the (mostly Draft) New Blogger June 2008 release, vertical line spacing changed.
You can see the problem, in Blogger Spacing Issue Fixed - June 2008. When I wrote that post, the code displayed, as I describe farther down in the post as
Now, it's not tighter.
Coming just before the release of New Blogger June 2008, we have to wonder.
>> (Update 6/28 21:00): This issue appears to be fixed.
>> Top
Earlier this month, I showed how the corrected (finally!) vertical line spacing issue had been corrected, and how easily you can tweak the line spacing for elements like pre-formatted blocks. At that time, vertical line spacing for pre-formatted blocks was predictable, and could be tweaked. Since that time and just before the (mostly Draft) New Blogger June 2008 release, vertical line spacing changed.
You can see the problem, in Blogger Spacing Issue Fixed - June 2008. When I wrote that post, the code displayed, as I describe farther down in the post as
tighter vertical spacing (1.2em)
Now, it's not tighter.
Coming just before the release of New Blogger June 2008, we have to wonder.
>> (Update 6/28 21:00): This issue appears to be fixed.
>> Top
Subscribe to:
Posts (Atom)