Bug 112213 - Documents based on templates which have ODF property "Open file read-only" are not editable
Summary: Documents based on templates which have ODF property "Open file read-only" ar...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Templates
  Show dependency treegraph
Reported: 2017-09-04 14:33 UTC by Harald Koester
Modified: 2023-09-28 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2017-09-04 14:33:24 UTC
In order to reproduce: 

[1] Create new text document and insert some text.
[2] Mark document “Read-only”: File > Properties… > Security > Check “Open file read-only”, then “OK”.
[3] Save the document as template: File > Templates > Save as template… > Insert template name > Chose template category > Save.
[4] Close the document without saving.
[5] Create new document based on saved template: File > New > Templates > Double click new template. Document is opened in read-only mode.
[6] Try to reset Read-only Mode: File > Properties... > Security. Option “Open file read-only” is greyed and can't be changed. Expected: Reset of Read-only mode should be possible.

As a consequence it is not possible to protect a template against unwanted changes. Templates can't be saved read-only if you want to use them. 

To my opinion already at step 5 a document should not be opened as read-only. You usually want to modify a new document also if you use a template.
Comment 1 Xavier Van Wijmeersch 2017-09-05 13:36:14 UTC
when saving a document as templates, you cannot make any change in it. When someone made some changes it will ask to save it as a document for the person him self. So protection off the template as read only is not needed. The templates stays as intent. For me its not a bug. Other comments may be welcome.
Comment 2 Harald Koester 2017-09-06 15:03:21 UTC
According the Help the read-only function should protect a document against accidental changes. To my opinion this also makes sense for templates. But this does not make sense for documents based on templates, because it’s quite usual, that these documents are modified. Hence at least it is necessary that a user is able to enable the Edit Mode if she/he has created a document based on a template. To my opinion it would be even better when a document based on a template is always created in Edit Mode. 

Meanwhile I found a work-around to enable the Edit Mode: You have to save the newly created document first as a normal document. Then you can modify the document. But this is not obvious, in order to go on with my work I only saw the possibility to enable the Edit Mode of the template.

Bug exists already in version 3.3.0. Hence set version set to "Inherited from OOo".
Comment 3 V Stuart Foote 2017-09-06 17:34:51 UTC
Confirmed. On Windows 10 Ent 64-bit en-US with
Build ID: dccd1633a111ba124f9868a4a51579c95200d745
CPU threads: 8; OS: Windows 6.19; UI render: GL; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-09-06_06:44:26
Locale: en-US (en_US); Calc: CL

The File -> Properties -> Security tab setting "Open file read-only" set on a template renders the resulting template based document uneditable in the document shell.

QA note: careful not to confuse this ODF extended document property with the OS file system Read Only protection.

Comment 4 QA Administrators 2018-09-22 02:44:09 UTC Comment hidden (obsolete)
Comment 5 Harald Koester 2018-09-22 16:55:52 UTC
Bug still exist in version 6.1.1. (64 bit, Win 10)
Comment 6 QA Administrators 2019-09-23 02:54:35 UTC Comment hidden (obsolete)
Comment 7 Harald Koester 2019-09-27 20:31:10 UTC
Bug still exist in version 6.3.2. (64 bit, Win 10)
Comment 8 QA Administrators 2021-09-27 03:23:42 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2023-09-28 03:17:42 UTC
Dear Harald Koester,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://downloadarchive.documentfoundation.org/libreoffice/old/

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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team