Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.If I create a new select component, use "Load a pre-built option list", and use a pre-built option list that contains a group, Options Element does not display properly because it is configured to not allow groups. The problem is that #optgroups is set based on the value of aslist, but this doesn't get updated when one chooses the pre-built option list.
The attached patch fixes it by always setting #optgroups to TRUE. This is fine because the user is always allowed to use groups. Current behavior already is that if the user uses groups, then aslist is set TRUE when the component is saved.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | webform_optgroups_true.patch | 532 bytes | Liam Morland |
| webform_optgroups_true.patch | 532 bytes | Liam Morland | |
Comments
Comment #1
quicksketchThanks for the report and patch!
I don't think this is always the case. Groups are not allowed if assembling radio buttons or checkboxes (in other words if "aslist" is FALSE). Perhaps adding validation to the form would be the right thing to prevent the conflict in settings.
Comment #2
Liam MorlandWhat I mean is that a select component can always handle groups, it just has to use a select element if they exist. Webform already sets aslist automatically in some situations. As it is now, if a person wants to create a select component with groups, they need to make the component, set aslist, and save, then re-edit the component to add the options with group. With my patch, they could just create and set the options with groups. When they save, they'll be told that aslist has been set.
Comment #3
Liam MorlandIf Options Element is not installed and one tries to use groups with radio buttons or checkboxes, Webform sets aslist = TRUE automatically. It should do the same when Options Element is installed instead of going to a broken state.
Comment #4
Liam MorlandDo you have another suggestion about how this patch could be done?
Comment #5
Liam MorlandWhat sort of validation do you suggest adding? If the user enters an option which starts with "<", they get an error? (Only, of course, if Options Element is being used; otherwise aslist is already set automatically.)
Comment #6
Liam MorlandThis problem still exists. Reroll.
Comment #7
quicksketchHi Liam, sorry I wasn't avoiding this patch in particular, I just haven't been in the Webform queue for a long time. The validation I was suggesting was that if you attempt to use an option group in your list of options, but the checkbox for "Listbox" is not checked, then a validation error is thrown.
Ah, I hadn't remembered that we were doing this already. In that case, it seems like it would make the most sense if we made Options Element lists work the same way, and if a group is created, we automatically enable "aslist", just like we do for the non-Options Element version.
Comment #8
Liam MorlandThanks, Nathan. That is what this patch does.
Comment #9
quicksketchExcellent, I'm doing an on-site this week and I'll be taking another run through the issue queue on the weekend. Thanks Liam for all your continued work on Webform.
Comment #10
quicksketchThanks, works as advertised (of course)! Committed to 7.x-4.x.
Comment #11
Liam MorlandThank you!