After checking in document in CMIS an unexpected copy of document can be created in repository causing problems on next checkout. Steps to reproduce and more explanations: 1. Open file from CMIS. As a example I was using file "/Yyy.txt" from Alfresco CMIS (http://cmis.alfresco.com/cmisatom user:admin, password: admin). 2. Checkout file by clicking a button in notification in top of screen. If used CMIS is Alfresco, personal working working copy of file is opened instead of original file. In my example it is called "/Yyy (Working Copy).txt" 3. Do some modifications to file 4. Check it in back to CMIS (File->Check in). After checking in LO still have opened personal working copy opened, it does not reopen document original. In my case I have still opened "/Yyy (Working Copy).txt" and not "/Yyy.txt". This behavior seems wrong and it is an starting point for problems. 5. Do some more modifications to file and save it. As a result in repository new document is created "/Yyy (Working Copy).txt". This is not a personal working copy like before, but just an independent copy of document. 6. In case of Alfresco CMIS this leads for even more problems. Original file "/Yyy.txt" can not be checked out anymore: filename for working copy is already used. But this is a problem in Alfresco, not in LibreOffice. System: Windows 7 LO Version: 5.1.0.0.alpha1+ Build ID: a6fed7a19befa5673403ec5fe3ab69a91475da3a Locale: ru-RU (ru_RU)
Vasily Melenchuk committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=c8cd629132f5b4d879edc53911a4e4abeb8d90aa tdf#92758: no more duplication of document in CMIS after checkin It will be available in 5.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
It was already implemented reload of document after commit. But due to conditions it was not happen in described above case. This was fixed.