https://bugs.documentfoundation.org/show_bug.cgi?id=150436
--- Comment #9 from Winfried Donkers <[email protected]> --- (I was too late to join the ESC.) The behaviour with AllowOverrideLocking seems 'unfair'. User A opens a document for editing that is not locked and assumes (s)he has locked the document for others. Next user B opens the same document, gets a message that the document is locked and chooses to open it (either deliberately or unknowing what the consequences may be), makes changes and saves these. No messages this time, as the lock has been transferred from user A to user B by choosing to open the document. Now user A wants to save her/his changes and finds the document locked by someone else! User A has no other options than disregarding her/his changes and doing them again after closing and reopening the document (in which case the situation between user A and B may reverse when user B still has the document open). The unfairness IMHO is that user A worked prudently but is the victim of inprudent actions of user B and user A has no possibility at all to prevent this. AllowEditReadOnlyDocuments is an analogue case. Someone decides a document should be readonly and (other) users can simply overrule this. I don't question the presence of these settings, just the default value and the fact that 'no one knows about these default values' until an incident occurs. The release notes for version 7.0 (https://wiki.documentfoundation.org/ReleaseNotes/7.0#Config_options) didn't alert me and suggest that new options were added where the default behaviour was changed. -- You are receiving this mail because: You are the assignee for the bug.
