Showing posts with label
Post Editor Strange Behaviour.
Show all posts
Showing posts with label
Post Editor Strange Behaviour.
Show all posts
Some blog owners report a problem with editing posts, in post editor.
With any changes made to a published post, an attempt to update shows another monolithic error.An error occurred while trying to save or publish your post. Please try again.
But the mystery does not end there. Even seeing the error, a curious blog owner, refreshing the post as displayed, may find a surprise.
Even with the mysterious error displayed, repeatedly, the changes just made may be visible in the post.
In some cases, a new post editor session - or the post display refreshed - will even show the changes made.
Even with the post editor showingAn error occurred while trying to save or publish your post. Please try again.
you may see your changes displayed, when you refresh the displayed post.
I just updated my earlier post, Country Code Aliasing Is A Solution - Not A Problem.
My personal and recent experience.
The post, before being updated.
I added the observation to the postBlogger has described the problem, as a solution to free expression and controversial content.
to the post.
I just updated my post.
Post Editor, showing the added observation.
Then, I clicked "Update" - and waited for an eternity. No matter how many times I hit "Update", I see the same error.
It's enough to make one pull hair, in anguish (as if, Chuck!).
Post Editor, showing the added observation, after clicking "Update".
But, the story does not end here.
The post, after being updated - even with the bogus error message displayed.
Surprise! See the added observation?
Don't believe me? Examine my post, Country Code Aliasing Is A Solution - Not A Problem.
If you see the error, don't give up!
So, if you edit your post, and having made the necessary changes, you see the bad newsAn error occurred while trying to save or publish your post. Please try again.
don't pull your hair in anguish, immediately.
Refresh the post - then examine the updated display, and the change just made (in a separate tab / window). You may find your changes saved, as if nothing is wrong.
And, it's the EverReady Bunny problem of the week.
I was once again, updating my previous post, and idly wondering if this problem had been fixed - and hello!
Post Editor, showing this error, after clicking "Update" - just as I updated my previous post.
My previous post - updated, even with Post Editor displaying the error!
This, too, may involve the Blogger / Google CDN - and delay in updating the Blogger database, between the nodes in the CDN.
Just be careful when closing the post editor tab or window, with the warning about unsaved changes displayed.
So, what to do, now? I couldn't even leave that window, to update this post - I had to Stay!
And having updated this post, in this window, I have to close that window, with the changes maybe unsaved. But I'll re read the post as displayed, first.
If you see a mysterious #Blogger Post Editor error "An error occurred while trying to save or publish your post. Please try again.", when trying to update a previously published post, repeatedly, take a moment and verify that the changes being made were NOT saved. You may be surprised!
This, too, may involve the Blogger / Google CDN - and delay in updating the #Blogger database, between the nodes in the CDN.
Recently, we have some blog owners observing that use of Post Editor leads to generation of an extra draft post.
If I edit this post, then save my changes, I may see an empty post when I hit "Close".
So, we will see. I will next Save this post, as is.
Here's this post, initially created.
And this post, being Edited.
Having added the above screen prints, I'll Save again.
And if I Save, then Close, I see an empty post.
The "empty" post, shown above, is normal for this blog - which uses dashboard "post template" content in new posts.
If I were to Save this new post, I would end up with an extra draft post. Since I don't care to Save, I will simply hit Close.
And when I Edit, then Save, there's the bogey, again.
This time, I Save - or wait until AutoSave kicks in.
And look at my Posts display.
And hitting Publish, I get another.
Here we see possibility for real confusion.
Be careful, and think - if this happens to you!
If you Save instinctively - or if you hesitate, and AutoSave activates, you end up with an extra draft post.
Be really careful, now!
The bogey is an "empty" post (with "post template" content).
Even with the bogey being "empty", look at the Posts list! If you Edit your post later, always make sure that you Edit the right post - with your updated content!!
If you end up with an extra draft post, be very careful to Delete or Edit the right post. Think carefully, before you continue!
Anyway, this problem is in the hands of Blogger Engineering.
Just don't Save - hit Close, immediately - and you'll see no long term weirdness. Until you Edit, again, of course.
This weekend, we see #Blogger Post Editor adding an extra post, when we Edit then Save a draft post. If you Close the unwanted post immediately, you'll see no lasting effects, however.
I recently updated an old post, to add a link to a newly published post - and experienced panic.
Adding a link to an old post, Deleted / Locked Blogs Have Several Causes, I discovered an oddity which caused extreme heartburn for several hours. Maybe you have experienced this, also.
Editing my post, and adding a simple single sentence, with embedded link, at the end of the post, I refreshed the display (always test your changes - no matter how minor!), and watched as the paragraphing scrambled itself.
I added a single sentence to the end of an old post - and watched as paragraphs in the post became hopelessly scrambled.
See the missing "</li>" at the end of the first list element?
Look at how the list line spacing is screwy now.
<li><a href="#DMCA">DMCA Violation</a> looks for copyright and similar violations.
Just one missing tag. Long ago, I learned to always close every list element properly.
<li><a href="#DMCA">DMCA Violation</a> looks for copyright and similar violations.</li>
But my proper list syntax policy had apparently started after the post, in question, was published.
I spent the next 1/2 hour re paragraphing the post content, following the broken list - and re spacing the list itself.
And having saved my work, the list - and the paragraphs following the list - remained scrambled.
This is no good!
How can I hope to help people, using this post?
Observing that paragraphing above the broken list was fine, I looked at the list code, line by line.
Paragraphing above the list is OK!
Much to my relief, I found a missing "</li>" tag. Adding the missing tag, I re paragraphed the post content - and this time, my changes remained.
This is what I would want to see.
Even the list remains properly spaced, in post editor.
Be very careful, when editing lists, in post editor "HTML" mode. Lack of care can lead to unpleasant consequence.
When editing a #Blogger blog post, in HTML mode, be very careful to avoid dropping closing list element tags. One dropped tag affects formatting of list content after the missing tag - and paragraphing following the broken list, even with the list properly closed.
target="_blank"
Recently, we've been seeing a few reports, in Blogger Help Forum: Get Help with an Issue, suggesting more problems with Post Editor, in Draft mode.I keep getting an error, when editing my posts.An error occurred while trying to save or publish your post. Please try again.
I am editing Draft posts, some of which are fairly large.
This blog owner is discussing yet another facet of the Post Editor feature, AutoSave.
Early AutoSave Experience
Long ago, people would report a different problem, when composing posts.When I compose my post, my typing is way ahead of what is displayed.
Blog owners, long ago, discovered that AutoSave, which applied to posts being composed before publishing, made their computers slow down. This made their on screen post content show noticeable delay, from their typing.
With newer and more powerful computers, and people who still type at the same speed, Post Editor slow down has become a thing of the past - but at a price.
With highway traffic engineering, a well known problem involves the regional effects of upgrading a local arterial street, to handle more traffic. This might improve traffic in your neighbourhood, but at the expense of another highway in the next city.
Similarly, upgrading the speed of your computer improves your Post Editor typing problem, but puts more load on the networks and Blogger servers. Thus we see the symptom, reported above.An error occurred while trying to save or publish your post. Please try again.
Pre AutoSave Experience
As you compose a post, what you type is saved on your computer - and displayed in Post Editor. This lets you see what you are typing, in a "what you see is what you get" display. If you hit "Save", periodically, what you have typed gets saved to the Blogger servers.
Originally, many blog authors did not think to Save, when composing a post. Some would just type - then eventually Publish, when convenient. This technique created two problems.- The longer an author waited before Publishing, or Saving, the greater the chance that something would happen with the computer being used, causing loss of what was being typed. And the greater the catatrophe from the loss.
- The longer the author waited before Publishing or Saving, the more work would be done by the Blogger servers, when the author finally did Save, then Publish.
Blogger added AutoSave to Post Editor, so the effects of Publishing massive amounts of unsaved post content would not affect Blogger resources so abruptly - and so less people would see their hard effort go down the drain.
Current AutoSave Experience
One known problem with AutoSave is that it generates load on the local computer, on the networks connecting to Blogger, and on the Blogger networks and servers - thus the slow typing problem, long ago.
Another problem is that it saves automatically (hence the name) - and for some people, who may have just cleared the contents of a post, AutoSave saving an empty post tends to cause a problem. The longer people work on pages or posts, without publishing, the greater the chance that this disaster may happen.
Unfortunately, having a more stable publishing process, thanks to the reverse effect of AutoSave, will just encourage people to take longer before Publishing or Saving. Thus the complaint.I was working on my new post for weeks. Right in the middle of highlighting a section for deletion, AutoSave kicked in, highlighted the whole post, deleted the highlighted section, and saved an empty post. How do I get my post back?
And for this unhappy author, there can be no helpful answer.
Future AutoSave Prognoses
For a while, I've been suggesting that when possible, you should publish a post immediately, then continue editing your post after publishing - since AutoSave only affects post editing, before the initial Publish. Recently, I discovered that it may be possible to use Google Docs as a Content Management System, for long term post development.
A third possibility is that you compose your unpublished posts in HTML mode, instead of Compose mode. The effects of AutoSave, in HTML mode, are not as objectionable. Some of my posts, I might develop for a week or two before Publishing, using HTML mode. If you use this technique, and you include anchor links in your posts, beware of switching back and forth between Compose and HTML.
A fourth alternative, use of Microsoft Word instead of Google Docs, is known to cause problems with auto pagination and with various posts newsfeed accessories. We do not recommend use of Microsoft Word.
However you develop a post, the longer you wait before Publishing, the greater the chance that AutoSave will make you unhappy - either by sudden destruction of your post - or by contributing to the latest symptom.An error occurred while trying to save or publish your post. Please try again.
Publish sooner, develop offline, or become a victim.
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
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.- 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
