Unprotected cell remains locked even after Cell Protection is unchecked in Cell Format and Sheet Protected. 1. I formatted a cell and unchecked protection. 2. Then I protected the Sheet with and without a password. 3. The unprotected cell remains protected and is uneditable. LibreOffice 4.0 installed and then OpenOffice 3.4 uninstalled. The same scenario emulated in MSOffice 2003 and it works fine.
I have the same problem with LO 4.0.2.2 on Windows NT. It used to work on LO 3.x. Stephan
Could you attach sample file & how to see that problem so others can easily check it?
I can't reproduce that problem using LO 4.0.3.3 (Win7 32bit). Please we need more detailed info.
Created attachment 81398 [details] sample document document is locked completely in 4.x although there is one unprotected cell and the user is allowed to select unprotected cells
Created attachment 81399 [details] cell format protection is off for A1
Created attachment 81400 [details] protect sheet user should be able to select unprotected cells only
Same here. Sample document attached in comment #4. Password is empty. I also attached two screenshots (comment #5 and 6) to illustrate the way to reproduce. It worked for us up to 3.6.5 (did not check later 3.6.x versions) and was broken in 4.x (checked with 4.0.3, 4.0.4 an 4.1.0 beta 2). This behavior can be reproduced in Mac OS X 10.8, Windows 7 and Server 2008 R2.
> Created attachment 81398 [details] > sample document > > document is locked completely in 4.x although there is one unprotected cell > and the user is allowed to select unprotected cells I can select & modify cell A1 on that file (using LO 4.0.4.2 & Win7 32bit). Did I misunderstand? If yes, please provide step by step procedure to demonstrate that problem. Have you tried resetting user profile?
Sorry, my sample document was too simple. You are right, it works as expected. I will upload a new example that will demonstrate a locked (not selectable) but unprotected cell in a protected sheet. In fact there are more parameters active - e. g. the cells have conditional formatting: 1) marking the status protected/unprotected (for usability reasons: only the cells with no background fill are selectable). 2) in cells with content "0" the zero will be colored white (making it invisible, further enhancing readability). Remove conditional formatting #2 and everything is fine. You can select the cells with content "0" and enter other values. This example is an excerpt from a real life file. We have dozen other files of that kind need every day that prevent us rolling out LibO 4.x. This kind of formatting originates from MS Excel files (no problem there), but were saved in OpenDocument format long ago (sometime during the OOo 2.x days). You can select the zeroed cells in LibO 3.6.x and before but not in 4.x
Created attachment 81416 [details] sample file #2 More complex example. C13 an C17 are unprotected cells in a protected sheet. They are not selectable. Empty password.
Hi Rolf, After some testing & searching, I found the fact: 1. Check style "weiße schrift" (applied on conditional format #2) by hitting F11, right-click, then Modify. 2. Select tab 'Cell Protection', see that 'Protected' checked. So the behavior you've been explained is work as expected. Style used on Conditional Formatting will override existing format of cell(s) where that Conditional Formatting applied. (see Bug 51636) Tested on LO 4.0.4.2 (Win7 32bit) Set status UNCONFIRMED -> maybe I'm wrong, let ask the experts
You are right. Sorry that I hijacked this thread. Obviously LibO 4.x takes conditional formatting more thorough than earlier versions - which is not a bug :-) Thanks for "debugging" this. I corrected the formatting in our files and this will help rolling out 50+ installations of LibO 4 in our company. Maybe the initial reporter has a different setting causing his problem?
> Thanks for "debugging" this. I corrected the formatting in our files and > this will help rolling out 50+ installations of LibO 4 in our company. So we wish you success :) > Maybe the initial reporter has a different setting causing his problem? @Batayub/Stephan, perhaps you had different issue? If not I would suggest to mark this RESOLVED NOTABUG.
I just checked with LO 4.0.4.2 and it seems to work as expected. So from my point of view there is no reason not to close this bug. Thanks for looking into it! Stephan
I think 3 resolved confirmations is enough :) WORKSFORME seems more appropriate
This is working fine since release 4.0.3.3 Thanks!