When I save a document with a table that contains some protected cells in MS Word 2003 (DOC) or MS Word 2007/2010 (DOCX) format, the protected cells are not protected when the document is loaded in MS Word. Expected result: Cells protected in Writer should remain protected when the document is saved in MS Word 2003 (DOC) and MS Word 2007/2010 (DOCX) formats. Actual result: Cells protected in Writer lose the protected "state" when the document is saved in MS Word 2003 (DOC) or MS Word 2007/2010 (DOCX) formats. I created a table with some empty/blank columns to be used as "spacers". To make sure the "spacer" columns contain no data, I mark them as being protected. This is being lost when I save the document in MS Word 2003 (DOC) or MS Word 2007/2010 (DOCX) formats. I'll attach sample documents for troubleshooting purposes. Both LibreOffice Writer and MS Word 2007 are running on the same Windows XP SP3 system. Thanks!
Created attachment 124615 [details] The original ODT document with the protected table cells.
Created attachment 124616 [details] The original ODT document saved in MS Word 2003 (DOC) format
Created attachment 124617 [details] The original ODT document saved in MS Word 2007/2010 (DOCX) format
I have reproduced the unprotected cells in but daily Linux bibisect repository version 2016-04-25 and 43max bibisect repository version oldest. So, I am setting but status 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 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro 6.2+.
Dear Tom Williams, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This issue still occurs in LibreOffice Writer 6.2.7.1 on Ubuntu Linux. I'll see if I can try a newer version of LibreOffice, when I get a chance. This is what I did: 1) Open the test ODT file in Writer 2) Save it as a DOCX file 3) Open the DOCX file in Writer 4) Try to enter values in a protected cell Actual results: The value I attempted to enter into a protected cell was successfully entered. Expected results: The value I attempted to enter into a protected call should NOT have been successfully entered. When I perform these same steps with the original ODT file, I get an error popup indicating I can't enter data in a protected cell.
I don't see any option to protect cells in MICROSOFT WORD 2003 or 2016. I think for this report to be valid, you would have to produce a document in Word, and then have LO not be able to import or export it properly. My guess (and my conclusion from a google search) is that LO has functionality that MSO doesn't have, so you loose that when saving in a proprietary format.
(In reply to Justin L from comment #9) > I don't see any option to protect cells in MICROSOFT WORD 2003 or 2016. I > think for this report to be valid, you would have to produce a document in > Word, and then have LO not be able to import or export it properly. > > My guess (and my conclusion from a google search) is that LO has > functionality that MSO doesn't have, so you loose that when saving in a > proprietary format. Makes sense to me. Thanks for the update!