We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When a file is locked, users are still able to edit it using the desktop client
Scenario: Two users have access to the same file
When a user locks a file to edit it, the file should be set as "read-only" for other users.
As far as I remember this was the behaviour some versions ago. I am not sure why this behaviour changed.
any file
Windows
Windows 10
Appimage
25.0.5
3.8.0
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Encryption is Disabled
No response
The text was updated successfully, but these errors were encountered:
See also #4060
Sorry, something went wrong.
@mgallien @allexzander Do you believe you can bring back the feature which sets the file as read-only when it is locked?
Thank you!
@vagner-dias this would be #5841
No branches or pull requests
Bug description
When a file is locked, users are still able to edit it using the desktop client
Steps to reproduce
Scenario:
Two users have access to the same file
Expected behavior
When a user locks a file to edit it, the file should be set as "read-only" for other users.
As far as I remember this was the behaviour some versions ago. I am not sure why this behaviour changed.
Which files are affected by this bug
any file
Operating system
Windows
Which version of the operating system you are running.
Windows 10
Package
Appimage
Nextcloud Server version
25.0.5
Nextcloud Desktop Client version
3.8.0
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: