I am working on an issue reported by users who moved from 5.4 to 6.0.
In their use case, they have Calc files on a shared folder. Each user
has write access to his files, but the folder itself is read-only (to
prevent users from deleting each-other's files).
With 5.4, this use case works - each user can edit his files.
With 6.0, users can't open their files - they get an error about not
being able to create the lock file.
I could easily reproduce this behavior using a local read-only folder.
From a user's standpoint, this looks like a regression.
But from my standpoint, it seems logical, and I'm actually wondering why
5.4 was not failing too...
Is this change of behavior expected ? Does it result from a fix
somewhere between 5.4 and 6.0 ?
What recommendation do you have about this use case : being able to
share files with write access without letting users delete them ?
I have verified that I could open the file when I modify the flag
"org.openoffice.Office.common/Misc/UseLocking" in advanced settings, but
this would leave them open to concurrent access, and corrupted files. Is
there anything better suited?
Any suggestion is welcome,
Message envoyé grâce à OBM, la Communication Libre par Linagora
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
- [libreoffice-users] LibreOffice 6.0.6 - Calc - Open file in read-only folder · Julien Ropé
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy