---- Reported by nengard@gmail.com 2008-10-13 04:58:56 ---- See attached. And read this report from a customer: "I was experimenting with the dictionary and got both radio buttons in an OR statement stuck on- I couldn't get either of them to turn off. I just didn't save the definition but when you click one radio button to create an OR statement the other button should toggle to off" ---- Additional Comments From nengard@gmail.com 2008-10-13 04:59:20 ---- Created an attachment radio buttons ---- Additional Comments From nengard@gmail.com 2009-05-18 20:38:00 ---- After looking at the templates I think that this: <td><input type="radio" name="<!-- TMPL_VAR NAME="name" -->_all" value="all" />All dates</td> <td>OR</td> <td><input type="radio" name="dates" value="range" />Date range<br /> has to be changed to this: <td><input type="radio" name="<!-- TMPL_VAR NAME="name" -->" value="" />All dates</td> <td>OR</td> <td><input type="radio" name="<!-- TMPL_VAR NAME="name" -->" value="range" />Date range<br /> But after talking with Chris he seems to think that this will only solve the toggling of the radio buttons and that the code behind it doesn't really work ... so I'm not going to make the change and I'm going to leave it to a more experienced expert :) --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:54 UTC --- This bug was previously known as _bug_ 2669 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2669 Imported an attachment (id=782) Actual time not defined. Setting to 0.0 CC member bchurch@ptfs.com does not have an account here The original submitter of attachment 782 [details] is unknown. Reassigning to the person who moved it here: chris@bigballofwax.co.nz.
Created attachment 8794 [details] screenshot I tried retesting this on current master, what I did: 1) New definition 2) Module: patrons 3) Registration date 4) Nothing shows up for the 4th step For other dates like 'Expiry date' the 4th step shows up correctly and shows the wrong behaviour Nicole described.
(In reply to Katrin Fischer from comment #1) > Created attachment 8794 [details] > screenshot > > I tried retesting this on current master, what I did: > > 1) New definition > 2) Module: patrons > 3) Registration date > 4) Nothing shows up for the 4th step > > For other dates like 'Expiry date' the 4th step shows up correctly and shows > the wrong behaviour Nicole described. With current master 'Expiry date' displays on current master, but the bug as such is still valid.
Created attachment 46482 [details] [review] Bug 2669: Change checkboxes to radio buttons on dictionary On creating new dictionary for report, the choice between "All dates" and "Date range" should be a real radio button, not 2 radio buttons with different names (which means they could be selected altogether...) Note that I don't understand what means 'All dates', there is no condition generated for the dictionary. We should not have to select a field if we don't want to add a condition on it :) Test plan: Create a new dictionary for the Patron module, then a date field (dateenrolled or birthdate, etc.) Confirm that the radio buttons now behave as radio buttons...
(In reply to Jonathan Druart from comment #3) (...) > Note that I don't understand what means 'All dates', there is no > condition generated for the dictionary. We should not have to select a > field if we don't want to add a condition on it :) Same findings with my tests: If "All dates" is set, the definition saves with an empty condition. (With and without patch, see dictionary.pl line 152.) To have a condition saved, "Date range" and at least one of the dates "Start of date range" and/or "End of date range" has to be set. Conclusion: The checkboxes rsp. radio buttons and the condition for their value in dictionary.pl line 152 could be removed.
Created attachment 46505 [details] [review] Bug 2669: Change checkboxes to radio buttons on dictionary On creating new dictionary for report, the choice between "All dates" and "Date range" should be a real radio button, not 2 radio buttons with different names (which means they could be selected altogether...) Note that I don't understand what means 'All dates', there is no condition generated for the dictionary. We should not have to select a field if we don't want to add a condition on it :) Test plan: Create a new dictionary for the Patron module, then a date field (dateenrolled or birthdate, etc.) Confirm that the radio buttons now behave as radio buttons... Signed-off-by: Aleisha <aleishaamohia@hotmail.com> Looks so much nicer too!
Jonathan and Aleisha, Since the radio buttons do not make much sense, couldn't we simply remove them? (See test and conclusion on comment #4)
(In reply to Marc Véron from comment #6) > Jonathan and Aleisha, > > Since the radio buttons do not make much sense, couldn't we simply remove > them? (See test and conclusion on comment #4) I would prefer another bug report, it won't be as easy as this patch.
Created attachment 46515 [details] [review] Bug 2669: Change checkboxes to radio buttons on dictionary On creating new dictionary for report, the choice between "All dates" and "Date range" should be a real radio button, not 2 radio buttons with different names (which means they could be selected altogether...) Note that I don't understand what means 'All dates', there is no condition generated for the dictionary. We should not have to select a field if we don't want to add a condition on it :) Test plan: Create a new dictionary for the Patron module, then a date field (dateenrolled or birthdate, etc.) Confirm that the radio buttons now behave as radio buttons... Signed-off-by: Aleisha <aleishaamohia@hotmail.com> Looks so much nicer too! Radio buttons display as expected. Signed-off-by: Marc Véron <veron@veron.ch>
Created attachment 46716 [details] [review] Bug 2669: Change checkboxes to radio buttons on dictionary On creating new dictionary for report, the choice between "All dates" and "Date range" should be a real radio button, not 2 radio buttons with different names (which means they could be selected altogether...) Note that I don't understand what means 'All dates', there is no condition generated for the dictionary. We should not have to select a field if we don't want to add a condition on it :) Test plan: Create a new dictionary for the Patron module, then a date field (dateenrolled or birthdate, etc.) Confirm that the radio buttons now behave as radio buttons... Signed-off-by: Aleisha <aleishaamohia@hotmail.com> Looks so much nicer too! Radio buttons display as expected. Signed-off-by: Marc Véron <veron@veron.ch> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Another wishlist item: it would be nice of the date range fields only displayed when the date range option is selected, or the date range option is selected automatically if the date range gets filled in my the librarian.
Pushed to Master - Should be in the May 2016 Release. (Also would be cool to notes Kyle's wish list at the end of this.)
Patch pushed to 3.22.x, will be in 3.22.3
This patch has been pushed to 3.20.x, will be in 3.20.9.