When opening a document in CMIS, LO does not lock the file on the CMIS server or open the file in read-only mode.
This is very dangerous because another user can open simultaneously the same file and overwrite the ongoing changes.
Therefore 2 options to resolve this when a document is opened in CMIS:
- the file is in read-only mode unless the user 'Extract' the document (BTW 'Extracts' should be replaced by a more user friendly term, ie 'Lock for Editing')
- set a CMIS lock on the server
Not a critical bug - critical bugs are saved for bugs that create data loss, crashes, etc . . . while there is a potential for multiple users to be working on same file which could result in bad things it's not a critical bug in of itself.
Also is this a new problem or was it in older versions of LibreOffice as well?
Nb: This bug could lead to data loss because a user can overwrite another user work
This bug was present in previous versions
I chose openKm for document management and I am using libreoffice 188.8.131.52 to access openKM server using CMIS. Files can correctly be opened and saved, but no lock is done on server side so that users can modify simultaneously files...
I agree with Christopher Potter, this is quite an important bug of CMIS feature.
Is this a regression? Can someone test older versions and narrow down if it ever worked? That will at least help us narrow it down.
If a version worked - please set the version field to the oldest version that it's confirmed as broken, add "regression" to keywords, and leave a comment letting us know the latest working version and latest broken version. Thanks
I cannot tell you if this is a regression since I only used it recently. I had the problem on version 4.3.6. I updated with latest version 4.4.0 (windows), but this did not solve the problem.
My collegue has libreoffice version 184.108.40.206 for ubuntu Linux and he has also the same issue.
Hope it will help
Although I am not a developper, is there maybe something that I can do to help?
You can check to see if it's a regression (and figure out what exact release caused it). Will be time consuming but greatly appreciated.
So my suggestion is test the very oldest release first (3.3) and see if you can reproduce. If you can't, then that means it's a regression. Then I'd take the middle point (let's say 4.0) and test that....keep narrowing it down until you figure out what exact point release caused the issue.
I downloaded version 3.3 but CMIS was not available.
I checked release notes and CMIS was introdcued in 4.0 release.
I downloaded it (220.127.116.11.beta2 from http://downloadarchive.documentfoundation.org/libreoffice/old/18.104.22.168.beta2/win/) and CMIS is available.
Still, lock is not put on CMIS server file when opened with libreoffice 22.214.171.124 beta2.
So this is not a regression but an important feature missing since the beginning.
Any update from your side on this defect?
Thanks a lot.
No and to be honest it could be awhile before it's fixed. It's 100% dependent on a volunteer choosing to fix it (no one in the project can dictate that the bug be fixed). So - really the options from your side are:
1) Fix it yourself;
2) Find someone to fix it;
3) Pay for a fix (likely quite expensive);
4) Wait - and like I said, it could be awhile
Just a couple of remarks:
1) for CMIS now there is a 'Checkout' command to lock file to edit
2) for WebDAV file lock should be working from LO 5.1.
So if someone can try this bug, probably it can be closed.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice
(5.4.1 or 5.3.6 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Still occurs in 126.96.36.199
Another option to put a lock while editing without a checkout would be to open in read-only mode