Created attachment 81740 [details]
DOCX containing 2 restricted paragraphs and 1 editable paragraph
When LO loads a DOCX file that has 'Restrict Editing' protection - it does not do anything about it.
'Restrict Editing' can be used in several ways to protect a document (allow only specific styles to be used, allow only specific sections to be edited by specific people \ users).
Steps to reproduce:
1. Load the attached DOCX
2. Edit any line of the document
LO allows you to edit any line of the document.
LO should only allow you to edit the 2nd paragraph.
Operating System: All
Version: 184.108.40.206.alpha0+ Master
Password to disable restrictions is '12345'.
The nodes that are not exported back to DOCX are:
- <w:permStart> in the 'document.xml' file.
- <w:permEnd> in the 'document.xml' file.
- <w:documentProtection> in the 'settings.xml' file.
> The nodes that are not exported back to DOCX are:
Of course, I meant 'the nodes that are not imported from'.
Thanks for the reports. I can confrim what you notice about the behaviour.
But may I ask: where in Writer can I set restrictions to the editing of a paragraph, different then putting it in a section?
I've not started Word to look at it, but then shouldn't his be an enhancement request for new functionality in the first place?
And a - maybe related - note: there is some protection in Wordt documents for forms (form protection). If anyone works on document protection: pls keep that in mind too, so that there are no accidential changes (not that currently it's perfect or not, but just to take that into account ;) )
> I've not started Word to look at it, but then shouldn't his be an
> enhancement request for new functionality in the first place?
You may look at it as an 'Enhancement Request', as this indeed should be an enhancement of LO.
However, in addition to that - this is a serious case of an interoperability bug, that changes a document's core property once it goes through LO.
A user might 'use' LO to get rid of protection of a document (maybe without even knowing).
Thanks to Cor who confirmed this 'bug' and asked a good question :-), and the nice reply of Adam, which I agree to -> NEW.
** 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 (4.4.1 or later)
*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 your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Win 7 Pro 64-bit Version: 220.127.116.11.alpha1+ (x64)
Build ID: f3375fa07f27bd2ade519af3c07d69040d10eaa9
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-22_23:38:50
*** This bug has been marked as a duplicate of bug 101244 ***
I don't think this is a duplicate of bug 101244, rather that it was resolved with bug 66398's fixes by Serge Krot:
tdf#66398 Parse and output permissions for DOCX using bookmarks
tdf#66398 Enhance unit test: check permissions at content level
tdf#66398 Fix copy-paste: call start() bookmark instead of end()