I’ve just released a new Umbraco package (v17):
Umbraco.Community.HeadsUp
We’ve had a number of clients report content issues arising when multiple editors work on the same node simultaneously, or when someone leaves a stale content tab open, doesn’t refresh to pull the latest version, and then saves the outdated data back to their website. We also had a client who reported that Umbraco was repeatedly losing their changes, when in fact they had multiple tabs open for the same content and were overwriting their own edits — which proved surprisingly tricky to explain!
Rather than looking at some of the various Lock based packages (eg the great Content Lock package), we wanted to have a lighter implementation and have a package run in a way that editors don’t need to remember to lock / unlock nodes, and so, leaning on the SignalR setup, we instead show a modal notifying users of a change to a node from elsewhere and give them different options and guidance on how to proceed.
It’s available in the marketplace here:
And on Nuget here: