Behavior of $force_selection on Radios

[mrwweb]

I just tried to use $custom_tax_mb->set( 'force_selection', true ); with radios and was surprised by the behavior to the point that I'm not sure it's right.

When $force_selection is set to false for radios, a hidden "None" option is added. When true, that option is gone but there is still no default selection of the first taxonomy term. I expected that the behavior would be more like the select implementation where the first option is defaulted to when $force_selection is true instead of a "none" option.

As it stands, I don't think $force_selection actually results in any difference in the post's term assignment when using radios.

[mrwweb]

Just realized that I would also expect the "Clear" button to be removed when $force_selection is true.

[studionenontwerp]

Hi mrwweb,

I experienced the same isues. Hook into the 'admin_init' action hook: add_action( 'admin_init', ... ). Then the default is set the right way.
Also: add if statement ' ! $this->force_selection ' at line 275 and ' endif ' at line 279 within the class ( function radio_close ). Then the clear button is left out.