There is currently no support for the
<a>tag in the
Select-Advancedfield types. Before I start creating a custom field type that supports optgroup, I thought it best to get some thoughts on this.
Logically, the field options could be defined like so:
'options' => array( 'Monkeys' => array( 'king_kong' => 'King Kong', 'curious_george' => 'Curious George' ), 'Donkeys' => array( 'eeyore' => 'Eeyore', 'gus' => 'Gus' ) ),
From a quick investigation the following elements would need to be overwritten
- RWMB_Choice_Field > get_options
- RWMB_Select_Field > walk
- RWMB_Walker_Select > start_el
Does it make more sense to change the core to support this standard HTML element, or build a custom field type? Am I the only one that missed the optgroup tag? Thoughts?
You must be logged in to reply to this topic.