content creation via webdav on windows 8
Hi, I've been evaluating Nuxeo for the past days, and I was surprised to learn about the explorer integration via webdav/windows sharepoint services. However when editing a pre-existing document the associated meta-data and versioning information is destroyed. In my particular use-case I was editing the document with Microsoft Office 2013, I was wondering if this is a common issue and if there are some configuration steps that could be taken to retain the information. Ideally, the document should be incremented with a minor version on every change, as opposed to being treated it's a new document all together.
Edited to provide detailed reproduction steps:
- Upload document to Nuxeo, be it via webdav, be it via the webinterface.
- Adjust associated meta data, I use version major and minor which is very opaque to see, mine was set to 2.1
- Mount the nuxeo to a drive letter via webdav (webfolders in windows terms) i.e. computer add network drive enter http:// as described by nuxeo documentation.
- Navigate to the file in question and edit the document using Microsoft Office Word 2013 (and presumably 2010, 2007)
- Overwrite the file by saving it.
- Back in the webinterface the associated version data is being reset to 0.0, even more so,when you refresh the page it says the document no longer exist.
Video:
Software versions:
- Nuxeo 6.0 (latest installer from the website)
- see
- Microsoft Office 2013 Professional Plus, Microsft Word, 15.0.4420.1017
- Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) (9600.winblue_gdr.131030-1505)
Thanks for the video.
As you can see in the Nuxeo URL, when Microsoft Word saves the file, it saves it under the name 996D933E.tmp instead of saving it with the original name. Nuxeo has no way of knowing that this is a new version of the old file and just update it as a new version with an incremented number.
To fix this we would need to understand how Microsoft Word does its saves through WebDAV and try to work around the fact that it loses some context and see if we have a way of reacquiring the correct info.
I opened NXP-16335 but this is not scheduled at the moment.
If you have a WireShark trace of the whole exchange it could help debugging.
|
Florent Guillaume
Member (36K) 6 8 8 |
01/12/2015 ( History) |