If you've only a few content editors then you can just temporarily disable their accounts via the Users section. This would prevent anyone logging in and thus changing content.
If you wanted to disable all accounts you could do it via the database and run the following SQL:
UPDATE umbracoUser SET userDisabled = 1 WHERE id > 0
That should disable all accounts (apart from main Admin account).
Disclaimer: I've not tried this :)
If SQL works you could write a dashboard to enable / disable all more quickly.
Set Umbraco as readonly for deployment
Is it possible to set Umbraco as readonly to ensure that no content editor is able to push changes in the database.
My idea is to lock Umbraco while doing update using deployment slot on azure.
If you've only a few content editors then you can just temporarily disable their accounts via the Users section. This would prevent anyone logging in and thus changing content.
If you wanted to disable all accounts you could do it via the database and run the following SQL:
That should disable all accounts (apart from main Admin account).
Disclaimer: I've not tried this :)
If SQL works you could write a dashboard to enable / disable all more quickly.
Alternatively there is this script you can create that doesn't write to the database but disabled backoffice access
https://shazwazza.com/post/easily-lock-out-umbraco-back-office-users/
I've not tested it, but it might be easier than needing DB access.
Nik
That's good ideas. I'll try them, thanks.
is working on a reply...