Description: Hi, I recently started using the "Form" option to input data to Libre Calc. I noticed I can overwrite data in protected and locked cells this way. Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.8 Steps to Reproduce: 1.create protected and locked columns and unprotected columns 2.select all 3.use form to input and write over protected and locked cells Actual Results: overwrite protected and locked cells Expected Results: not being able to overwrite protected and locked cells Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
First, your version it's a bit old. Have you protected the sheet: Menu/Tools/Protect sheet. https://help.libreoffice.org/latest/en-US/text/scalc/01/06060100.html?DbPAR=CALC#bm_id141619439455954 No clear for me your steps, what is the meaning the use a form to input after select all. And what form do you use?
Hi, "form" is a way of entering data in cells. You can find it under Data - Form. I've noticed I worked on an old version indeed, so I installed both Flatpack and Appimage versions and tried again. But another worse bug appears now. If I select protected cells (in a protected sheet) and use the "form" function the whole program freezes.
Hi, "form" is a way of entering data in cells. You can find it under Data - Form. I've noticed I worked on an old version indeed, so I installed both Flatpack and Appimage versions and tried again. But another worse bug appears now. If I select protected cells by ctrl-a in a protected sheet and use the "form" function the whole program freezes.
Please attach a sample file.
No need for that. Just protect a cell, lock the sheet, select all and go to data - form and the bug is there.
[Automated Action] NeedInfo-To-Unconfirmed
Since 7.4, Calc supports 16384 columns, so that is causing the performance problem when selecting all and opening the Form dialog. *** This bug has been marked as a duplicate of bug 131560 ***