This is the second time this happened to us. We saved a node a couple times and then when we try to save it displays the error: The content has either been modified by another user, or you have already submitted modifications. As a result, your changes cannot be saved.
This is the error: The content has either been modified by another user, or you have already submitted modifications. As a result, your changes cannot be saved.
We don't know the steps that we took to get it to this state but we are using Panels and we save a lot. The way I was able to fix this was to update the node_field_data table and update the "changed" timestamp to a lower number.
One thing that I found weird is that the node_field_data vid was set to 2116 but in the node_field_data table there were vids: 2117, 2118, and 2119 for my node. Perhaps that has something to do with it.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 2020-10-28_15-14-23.png | 58.98 KB | dpagini |
Comments
Comment #2
albertski commentedComment #3
amateescu commentedThe revision IDs getting out of sync could be related to #2640496: Revision ID in {node} and {node_revision} can get out of sync.
Comment #10
dpagini commentedStumbled across this issue. Just want to share 1 thing that I think is significant to this problem...
My node revision history is non-linear. Somehow, my history went 8/18, 8/19, 8/18, 8/25 and I can't figure out how that's possible. I believe THAT is contributing to why/how my node is getting the EntityChangedConstraint.
I should also mention that I'm using layout_builder and block_content and getting this issue. The issue is trying to save one of the blocks on the layout_builder field.
Comment #13
larowlanWe need steps to reproduce here before we can take action
Moving to a support request in the meantime
Comment #15
cilefen commented