There was more than one attempt to edit this resource at the same time. This may have been because you double clicked on a link or a button or because someone else is also editing this blog or post.
Please hit the back button on your browser and try again. If the problem persists, please contact the Blogger Help Group. We apologize for the inconvenience.
Literally, a Conflicting Edit occurs when the blog (or blog component, such as the blog URL, a single gadget, specific post, template, ...) in question is being "edited" (modified / updated) by more than one person, simultaneously. Resource allocation / maintenance, when more than one person is involved, is an infinitely complex concern in IT. The IT concept of "Time Sharing", and its inherent challenges, have been significant for a very long time.
Taken literally, I'd typically suggest two possible diagnoses.
- One person, with two or more browsers open, updating the same blog.
- Two or more persons, updating the same team blog.
- Clear cache, cookies, and sessions, restart your primary browser, and try again.
- Work with your teammates, and try to coordinate your activities better.
Recently, we've been seeing increased reporting of the "Conflicting Edits" symptom. In some cases, owners of "single owner" Blogger blogs, who use single browsers, have been reporting this message. In these cases, it's not likely to have the same resource (blog component) open at the same time, without the blog owner suspecting that to contribute to the problem.
In the latter cases, I'm suspecting that some setting conflict, on the local computer, is involved.
- The most likely culprit is going to be a cache / cookie / session conflict.
- Also consider that inconsistent Blogger access, caused by use of bookmarks on the local computer, causes use of conflicting Blogger aliases.
- Sequential (not necessarily concurrent) use of Draft and Production Blogger - or possibly Classic and New GUI Blogger - could cause artifacts in the Blogger database, for a given blog.
- Recovery from the May 2011 maintenance release rollback has caused many odd details, such as this one.