Error: "... modified by another user, changes cannot be saved"

By schildi on 14 Jan 2008 at 14:32 UTC

Since months I get errors for some nodes:

"This content has been modified by another user, changes cannot be saved."

I tried to edit the node using different users, but did not succeed. I also cleaned the cache, tried to revert to a previous version.
How can I get rid of these errors. And how to check for nodes having this problem?

regards
Schildi

Comments

That is a repeatable problem

themphill commented 14 January 2008 at 20:00

That is a repeatable problem for me if I create content using the "Create Content" tool, it displays a preview of my post, then I use my browser's "back" button to try and edit further. For me the solution is to make any subsequent edits using the Administer > Content Management > Content tool. I hope your problem is a simple as mine.

No, the node is completely

schildi commented 15 January 2008 at 01:51

No, the node is completely blocked. NO ONE, including admin can update the node.
I tried to find out if it is possible to manipulate the database fields (node, node_revisions) but had no luck.

Same thing

zemogle commented 6 February 2008 at 18:18

I'm getting exactly the same problem. My client is not happy with the work around solution. If anyone knows why this is happening, I would be really pleased to hear about it, especially if you have found a solution :-)

Thanks!

No solution found. My

schildi commented 7 February 2008 at 14:44

No solution found.
My "work around" was to copy the content to a new node and delete the old one.

Wonderful, one year later,

ChristineBaker commented 2 January 2009 at 07:42

One year later, still the same bugs.

I don't know how people with "clients" deal with this. I can't use Drupal for business.

I didn't have this effect

schildi commented 2 January 2009 at 13:56

I didn't have this effect since about one year. As far as I remember it has to do with the way I worked on articles that time. I used to open an article (node) from more than one window (tab) and may be closing the initial one. Since I strictly use one single window to act on an open article the described error did not raise any more.

Please tell the way your user worked on the node.