- 🇬🇷Greece dimitriskr
I'm reopening this issue as it's a feature that would improve the user experience, when using the field plugin.
I'm also attaching a patch for 2.x codebase - 🇮🇳India patelh84
I have added a new patch for version 2.0.7 where the all the extra default fields have been enabled.
- 🇬🇷Greece dimitriskr
@patelh84 can you upload an interdiff from #12? Thank you
#13 lacks the core of the functionality, so I expanded on #12 and did the following
- Renamed fields_default_state to preselected_fields (Thought it would be more descriptive/clear)
- Added the selection to the form field as a property (Like we do with the default_enabled property) so that we don't have to fetch the setting from the display handler when preprocessing
- Fixed a warning that was caused by a wrong index for the 'checkboxes' option
- Added a state to hide the preselected_fields property when the default_enabled is checked, since it would override any selection anyway.
Future Improvement Suggestion: We could rename the default_enabled to exclude_for_selected (or smth like that). This would not change the way this option works, but would need extension for the preselected fields (Kinda like conditions work for displaying blocks etc)
- 🇬🇧United Kingdom scott_euser
I have tried to elaborate on this a bit more to make it more clear the use case and intent. Not sure the patch is right, as you can already set default selections in the default InOperator from core (which this extends). Really the only thing you cannot do is prevent control of particular fields (ie, where you want them required).
- 🇬🇧United Kingdom scott_euser
Actually this is already doable with InOperator too, reverting description, sorry for the noise!
- 🇬🇧United Kingdom scott_euser
scott_euser → changed the visibility of the branch 3032517-views-uncontrolled-fields to hidden.