Bug 81833

Summary: EDITING: ProtectForm attribute in settings.xml cannot be changed in Writer.
Product: LibreOffice Reporter: Nikolay Amiantov <nikoamia>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: medium CC: todventtu
Version: 4.2.5.2 release   
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
i915 platform: i915 features:

Description Nikolay Amiantov 2014-07-28 09:45:31 UTC 
Problem description: 
In some documents (I'm working with [1]) there is a ProtectForm attribute set, which persists after saving .doc to .odt, which disables editing of any content outside of some kind of form "fields". "Design mode" doesn't work, and "Format > Sections" menu item is greyed out. Nothing else worked, and I've found a mention of this ([2],[3]) and a fix in [3] which works. This implies that there is no method (or no easily visible one) to change that flag inside of Writer.

Steps to reproduce:
1. Open a document
2. Try to edit something outside of fields
3. Try to disable this protection

Current behavior:
Editing is prohibited, and there is no visible way to disable protection without manual editing of .odt.

Expected behavior:
There is a way to do this.

[1]: http://www.brave.ru/upload/brave/anketa_visa.doc
[2]: http://nabble.documentfoundation.org/How-to-unprotect-readonly-parts-of-a-document-td4056306.html
[3]: http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.user/21694
Operating System: Linux (Other)
Version: 4.2.5.2 release
Comment 1 Nikolay Amiantov 2014-07-28 09:58:01 UTC 
Even if I manage to change this flag with editing of settings.xml, there is an invisible symbols at start and end of these "fields" which cannot be removed.
Comment 2 Beluga 2014-11-05 12:08:34 UTC 
Confirmed as an enhancement.

Win 7 64-bit Version: 4.4.0.0.alpha1+
Build ID: b7d8a58ff2698ffc6e22943f64aa97c5ea253bd9
TinderBox: Win-x86@42, Branch:master, Time: 2014-11-05_00:40:38

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.