I'm getting an issue where I hhave content items that are very often changed from multiple sources simultaneously. There's 14,000 occurences of this in the last 24h.
I understand the problem. User 1 and user 2 cause an update to an item at the same time. user 1 goes through fine but user 2 gets a 500 because their data is now outdated.
Due to the nature of the content, it is a necessity that many can update a content item like this simultaneously.
What would be a good way to go about fixing this? Is it possible to check whether the data is now outdated before calling .SaveAndPublish, and if it is outdated to then retry somehow.
I had ready about using Guid rather than id to access content item caused the issue pre 8.3, but im in 8.7, so no longer an issue?
I do think its down to multiple people causing a change, rather than a bug in umbraco.
Not sure whether there is a package for this, but an awesome solution would be “locking” the content, if someone is currently editing it. So:
User 1 accesses the content, user 2 now access the content, but cannot edit it, before user 1 leaves the content. This would be possible with SignalR. Now the good question is, should it be possible to “request” editing access from the current user and how should it be.
But I guess the simple solution could work for you for now. It does however require some coding and some knowledge about how SignalR works and how it communicate with clients. But should be possible.
Cannot save a non-current version
Hi!
I'm getting an issue where I hhave content items that are very often changed from multiple sources simultaneously. There's 14,000 occurences of this in the last 24h.
I understand the problem. User 1 and user 2 cause an update to an item at the same time. user 1 goes through fine but user 2 gets a 500 because their data is now outdated.
Due to the nature of the content, it is a necessity that many can update a content item like this simultaneously.
What would be a good way to go about fixing this? Is it possible to check whether the data is now outdated before calling .SaveAndPublish, and if it is outdated to then retry somehow.
I had ready about using Guid rather than id to access content item caused the issue pre 8.3, but im in 8.7, so no longer an issue? I do think its down to multiple people causing a change, rather than a bug in umbraco.
Hey Dave.
Not sure whether there is a package for this, but an awesome solution would be “locking” the content, if someone is currently editing it. So:
User 1 accesses the content, user 2 now access the content, but cannot edit it, before user 1 leaves the content. This would be possible with SignalR. Now the good question is, should it be possible to “request” editing access from the current user and how should it be.
But I guess the simple solution could work for you for now. It does however require some coding and some knowledge about how SignalR works and how it communicate with clients. But should be possible.
Let me know what your solution is. :-)
I should have noted that this isn't within the backoffice. It's programmatic, through the API.
is working on a reply...