Well I see your use-case a little more clearly now, but unfortunately still don’t have many suggestions. I can easily throw a filter into the launch()
method:
/**
* Create a class property for each taxonomy that we are converting to radio buttons, ex: $this->categories
* @access public
* @return object
* @since 1.0
*/
public function launch(){
$options = apply_filters( 'radio_buttons_for_taxonomies_taxonomies', get_option( 'radio_button_for_taxonomies_options', true ) );
if( isset( $options['taxonomies'] ) ) {
foreach( $options['taxonomies'] as $taxonomy ) {
if ( taxonomy_exists( $taxonomy ) ) {
$this->{$taxonomy} = new WordPress_Radio_Taxonomy( $taxonomy );
}
}
}
}
Which should let you turn the WordPress_Radio_Taxonomy
class off for admins, but you’ve still got to do something about the save routine. If you start saving more than 1 term, when the author views the radio buttons, how will the input know which term is selected? If you save with the radio buttons, you risk losing the extra terms.
You might be better off writing your own custom plugin… feel free to hack out as much of RB4T as you find helpful.