Opened 8 years ago
Last modified 7 years ago
#39908 new enhancement
Make the page and category widget exclusions use a drop down not ID
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | Widgets | Keywords: | needs-patch |
Focuses: | rest-api | Cc: |
Attachments (1)
Change History (8)
#2
@
8 years ago
This could be made more user friendly by using a drop down.
...especially since IDs aren't usually exposed anywhere.
#3
@
8 years ago
- Focuses rest-api added
- Keywords needs-patch added
- Milestone changed from Awaiting Review to 4.8
While the exclusion could be implemented via a multi-select field (select[multiple]
) if there are hundreds or thousands of pages then this doesn't scale. Nevertheless, the same problem exists for the dropdown-pages
control in core currently. So it would be better than nothing! (And it could surely be implemented before we can get an accessible equivalent to Select2 into core.)
The list of pages populating the select should be sourced from the REST API once the widget control is expanded as opposed to being exported with the control up front when the customizer is loaded. The same should be done for the dropdown-pages
widget. See #30738.
@karmatosed coincidentally a prototype for this was implemented in JS Widgets when Customize Object Selector is also active. See pages-widget-in-js-widgets-and-customize-object-selector.mov