In a form you could chose for every field the property "Input required". This property doesn't do anything if there isn't set "Input required" also in the table, which should be filled by the form. Expected behavior: You could chose "Input required" in a field of a form and the dialog of an error occurs, if there is missing input. This error should appear, if there is "Input required" set in the form or set in the table (through SQL) or in both ways - but it isn't shown only, when it is set in both ways. See https://bugs.freedesktop.org/attachment.cgi?id=94532 for an example. Open the form "Table_Input_requred_GUI". You could save data without any content except the primarykey "ID". But all fields were set to "Input required" in the GUI of the form.
Reproduced. All the columns have Input required: Yes, but it still allows to save without content. Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: c989f5e0e11e295b11ffc921b0d105869e037e47 TinderBox: Win-x86@42, Branch:master, Time: 2014-11-07_22:50:48
Adding self to CC if not already on
** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Bug still exists with LO 5.4.0.0.beta1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
** 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
Bug still exists with LO 6.0.4.2, OpenSUSE 42.3 Leap, 64bit rpm Linux.
I think it could be interesting to test this again following tdf#91837 fix. I'll give it a try.
(In reply to Julien Nabet from comment #7) > I think it could be interesting to test this again following tdf#91837 fix. > I'll give it a try. I could still reproduce this
I gave a try with https://gerrit.libreoffice.org/#/c/60109/
Julien Nabet committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=dbb444e4ed7c19a11733ce8438bbb6546d42f852 tdf#75341: fix condition to approve row (form) It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Backports in gerrit waiting for review 6.1: https://gerrit.libreoffice.org/#/c/60125/ 6.0: https://gerrit.libreoffice.org/#/c/60126/
Just for information, since analyzing consequences of the patch on 6.0 may take some time and 6.0 branch will be soon EOL , the fix won't be backport on it.
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-6-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=3448ca93eb46365d05387f7f3512c706bdb987c4&h=libreoffice-6-1 tdf#75341: fix condition to approve row (form) It will be available in 6.1.2. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
This is all very well, but you don't seem to have thought of the number of people who have forms with the default setting of "Input required" - which appears to be "Yes". Now we have to go through all of our databases, through all of the forms, and for all of the fields set it to "no" where appropriate. A mega-PITA IMHO.
(In reply to Peter Toye from comment #14) > This is all very well, but you don't seem to have thought of the number of > people who have forms with the default setting of "Input required" - which > appears to be "Yes". Now we have to go through all of our databases, through > all of the forms, and for all of the fields set it to "no" where > appropriate. A mega-PITA IMHO. Have a look here: https://bugs.documentfoundation.org/show_bug.cgi?id=120353#c27 As I understand: Input Required will be set to "No" automatically when opening an older form by LO 6.1.4 Dosen't this work for you?
Doesn't seem to have worked. Just opened a base document dated March 2018. It's insisting on my putting data in a field that I don't want filled. I'm trying to write a macro to go through all forms in a document and convert all the fields to "not required". It'll take some time, given the arcane API.
(In reply to Peter Toye from comment #16) > Doesn't seem to have worked. Just opened a base document dated March 2018. With what version of LibreOffice?
6.1.3.2 64-bit running on Windows 7.
(In reply to Peter Toye from comment #18) > 6.1.3.2 64-bit running on Windows 7. Please give a try to brand new 6.1.4 version. Indeed, it should be fixed.
"Check for updates" says my LO is up to date. I'm downloading 6.1.4 manually. I just spent a frustrating hour changing all the "input required" controls to "no" :(
All fields (including those I'd originally marked as "Yes" are now "No". At least there are fewer of them!
Have tested this again and again. Bug isn't fixed. If I set a field in LO 7.4.0.3 as "Input Required" in a form, not in the table, nothing will happen in the form. I will reopen the bug. The patch only sets fields in older forms to "Input Required" → 'No'. But it doesn't change the behavior to give a warning, if no content is in a field I have set "Input Required" → 'Yes' and I save the row.
Let's put this one to NEW and since I can't help here, unassign and uncc myself.
Undoing all the damage done here by reopening, that led to clearing all *important* metadata like assignee, target, etc. Please do not reopen bugs that had "fixed" status for more than a year (this had it for almost four years). Comment 14 (and later discussion with Peter, and bug 120353) clearly indicate that the fix was effective. So anything that happened later, including something having exactly the same symptoms, must be filed separately, with this bug put in See Also. Thanks for understanding.
LibreOffice 5.4 will be made available as 64bit version in addition to the 32bit version. Installing the 64bit version requires Windows Vista or newer, the 32bit Version runs on Windows XP or newer. ( https://geometrydashscratch.io)