Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Currently the code removes the required fields entirely, rather than making them not required. Patch is attached.
| Comment | File | Size | Author |
|---|---|---|---|
| sans_reqd.patch | 455 bytes | douggreen |
Comments
Comment #1
bdragon commentedYep, this was a bug.
Just fixed it.
http://drupal.org/cvs?commit=164552
http://drupal.org/cvs?commit=164554
http://drupal.org/cvs?commit=164556
Comment #2
xolotl commentedSeems partially fixed.
Required fields now appear on other location groups beyond the first, but they are only required in the first location group.
Comment #3
yesct commentedrelated to #334311: Required fields in multiple locations
Are there three situations to consider?:
1) allow for example 3 locations per node, but only the first location has data filled in, the other two locations are optional (can be blank, or empty, but not allowed to be partially filled in)
2) allow for example 3 locations per node, but only the first location has data filled in, the other two locations are completely optional (can be blank, or empty, and allowed to be partially filled in, dont even require the required fields that are required for the first location)
3) allow for example 3 locations per node, and each location needs to have all the required fields.
Which way does this fix make it work?
Which way are people expecting it to work?
Maybe there needs to be a settings check box that allows the admin to decide which criteria should be applied when nodes can have more than one location.
Comment #4
yesct commentedno feedback in more than a year on a need for it to work any way other than the current way. Closing. Please reply with a detailed summary of use cases and how they differ from the current newest official release. If replying, please set the status back to active.