Bug 132636 - FILESAVE: ODT->DOC: Protect changes are lost on export
Summary: FILESAVE: ODT->DOC: Protect changes are lost on export
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on:
Blocks: 132637
  Show dependency treegraph
 
Reported: 2020-05-03 12:37 UTC by Timur
Modified: 2024-07-26 03:16 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
LockF.doc: locked for forms protection - a poor example since there are no form fields, but it highlights only the difference between the different types of protection. (19.50 KB, application/msword)
2020-05-07 04:39 UTC, Justin L
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2020-05-03 12:37:05 UTC
Steps:
1. create simple Writer .ODT
2. set Edit - Track Changes - Protect.. password
3. save as .DOC
4. reopen saved in LO and MSO

Actual: can turn off Track Changes
Expected: need password to turn off Track Changes

In MSO that would be Review-Track Changes-Lock Tracking, it's not checked.

DOCX was handled in Bug 106843 and bug 128744.
Comment 1 Justin L 2020-05-07 04:39:07 UTC
Created attachment 160475 [details]
LockF.doc: locked for forms protection - a poor example since there are no form fields, but it highlights only the difference between the different types of protection.

There are 4 types of document protection: read-only (attachment 160424 [details]), comments-only(attachment 160423 [details]), fill-in-forms-only, and enforce track-changes. Import is only fully implemented for read-only I believe.

This bug report is focused on the export side. Probably all four export cases should be fixed together.
Comment 2 QA Administrators 2022-07-26 03:29:00 UTC Comment hidden (obsolete, spam)
Comment 3 QA Administrators 2024-07-26 03:16:23 UTC
Dear Timur,

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

MassPing-UntouchedBug