The Selectplus solves my needs fantastically, the ability to easily select and add options when theyâre not there, however, it is polluting (for lack of a better word) the UX of the admin panel.
In the screenshot, you can see âlocationâ and âseriesâ, is it possible to hide these pages so theyâre not seen here?
Another option is to maybe group the both âLocationsâ and âSeriesâ under the a page called âOptionsâ which would look a little cleaner. Is this possible? Any help would be greatly appreciated.
However, hiding those pages only makes sense if you donât want the client to edit them. I developed the plugin for a project where the user should be able to quickly add an option and still later have the possibility to edit the page and add more information to the location.
Thanks for the swift reply. The client will not have to edit them, only to add options and select, so hiding seems ideal at the moment. Iâm essentially using it as a tagging system.
I have run into a little problem. If I have two selectplus on the page when I click on âAdd Pageâ both inputs open up. Is this feasible or am I doing something wrong here?
locations:
label: Locations
type: selectplus
formfields:
title:
label: Name of Event Location
placeholder: Location Name
required: true
template: location
width: 1/2
options: query
query:
page: locations
fetch: children
value: '{{uid}}'
text: '{{title}}'
series:
label: Series
type: selectplus
formfields:
title:
label: Name of Series
placeholder: Series Name
required: true
template: series
width: 1/2
options: query
query:
page: series
fetch: children
value: '{{uid}}'
text: '{{title}}'
Oh, yes, that is because the click event is called on the wrapper, not on a particular id. I didnât have any intentions to have more than one of these fields. Shouldnât be too difficult to adapt it, though. For a simple tagging systems, I wouldnât create new pages for all these categories, anyway, but store them in a field somewhere.