Post Editor Displays A Bogus Mistake When Updating Posts
Sunday, February 17, 2013
Edit
Some weblog owners written report a work amongst editing posts, inwards postal service editor.
With whatever changes made to a published post, an endeavour to update shows around other monolithic error.
Even amongst the mysterious mistake displayed, repeatedly, the changes merely made may endure visible inwards the post.
In around cases, a novel postal service editor session - or the postal service display refreshed - volition fifty-fifty present the changes made.
Even amongst the postal service editor showing
I merely updated my before post, Country Code Aliasing Is Influenza A virus subtype H5N1 Solution - Not Influenza A virus subtype H5N1 Problem.
My personal too recent experience.
The post, before beingness updated.
I added the observation to the post
I merely updated my post.
Post Editor, showing the added observation.
Then, I clicked "Update" - too waited for an eternity. No thing how many times I hitting "Update", I come across the same error.
It's plenty to brand i clit hair, inwards anguish (as if, Chuck!).
Post Editor, showing the added observation, later clicking "Update".
But, the even out does non cease here.
The post, later beingness updated - fifty-fifty amongst the bogus mistake message displayed.
Surprise! See the added observation?
Don't believe me? Examine my post, Country Code Aliasing Is Influenza A virus subtype H5N1 Solution - Not Influenza A virus subtype H5N1 Problem.
If you lot come across the error, don't plough over up!
So, if you lot edit your post, too having made the necessary changes, you lot come across the bad news
Refresh the postal service - too thence examine the updated display, too the modify merely made (in a split tab / window). You may uncovering your changes saved, every bit if naught is wrong.
And, it's the EverReady Bunny work of the week.
I was in i lawsuit again, updating my previous post, too idly wondering if this work had been fixed - too hello!
Post Editor, showing this error, later clicking "Update" - merely every bit I updated my previous post.
My previous postal service - updated, fifty-fifty amongst Post Editor displaying the error!
This, too, may involve the Blogger / Google CDN - too delay inwards updating the Blogger database, betwixt the nodes inwards the CDN.
Just endure careful when closing the postal service editor tab or window, amongst the alarm near unsaved changes displayed.
So, what to do, now? I couldn't fifty-fifty piece of work out that window, to update this postal service - I had to Stay!
And having updated this post, inwards this window, I stimulate got to unopen that window, amongst the changes peradventure unsaved. But I'll re read the postal service every bit displayed, first.
If you lot come across a mysterious #Blogger Post Editor mistake "An mistake occurred spell trying to salve or disclose your post. Please bear witness again.", when trying to update a previously published post, repeatedly, stimulate got a 2d too verify that the changes beingness made were NOT saved. You may endure surprised!
This, too, may involve the Blogger / Google CDN - too delay inwards updating the #Blogger database, betwixt the nodes inwards the CDN.
With whatever changes made to a published post, an endeavour to update shows around other monolithic error.
An mistake occurred spell trying to salve or disclose your post. Please bear witness again.But the mystery does non cease there. Even seeing the error, a curious weblog owner, refreshing the postal service every bit displayed, may uncovering a surprise.
Even amongst the mysterious mistake displayed, repeatedly, the changes merely made may endure visible inwards the post.
Related
In around cases, a novel postal service editor session - or the postal service display refreshed - volition fifty-fifty present the changes made.
Even amongst the postal service editor showing
An mistake occurred spell trying to salve or disclose your post. Please bear witness again.you may come across your changes displayed, when you lot refresh the displayed post.
I merely updated my before post, Country Code Aliasing Is Influenza A virus subtype H5N1 Solution - Not Influenza A virus subtype H5N1 Problem.
My personal too recent experience.
I added the observation to the post
Blogger has described the problem, every bit a solution to free aspect too controversial content.to the post.
I merely updated my post.
Then, I clicked "Update" - too waited for an eternity. No thing how many times I hitting "Update", I come across the same error.
It's plenty to brand i clit hair, inwards anguish (as if, Chuck!).
But, the even out does non cease here.
Surprise! See the added observation?
Don't believe me? Examine my post, Country Code Aliasing Is Influenza A virus subtype H5N1 Solution - Not Influenza A virus subtype H5N1 Problem.
If you lot come across the error, don't plough over up!
So, if you lot edit your post, too having made the necessary changes, you lot come across the bad news
An mistake occurred spell trying to salve or disclose your post. Please bear witness again.don't clit your pilus inwards anguish, immediately.
Refresh the postal service - too thence examine the updated display, too the modify merely made (in a split tab / window). You may uncovering your changes saved, every bit if naught is wrong.
And, it's the EverReady Bunny work of the week.
I was in i lawsuit again, updating my previous post, too idly wondering if this work had been fixed - too hello!
This, too, may involve the Blogger / Google CDN - too delay inwards updating the Blogger database, betwixt the nodes inwards the CDN.
Just endure careful when closing the postal service editor tab or window, amongst the alarm near unsaved changes displayed.
And having updated this post, inwards this window, I stimulate got to unopen that window, amongst the changes peradventure unsaved. But I'll re read the postal service every bit displayed, first.
If you lot come across a mysterious #Blogger Post Editor mistake "An mistake occurred spell trying to salve or disclose your post. Please bear witness again.", when trying to update a previously published post, repeatedly, stimulate got a 2d too verify that the changes beingness made were NOT saved. You may endure surprised!
This, too, may involve the Blogger / Google CDN - too delay inwards updating the #Blogger database, betwixt the nodes inwards the CDN.
