options_options() and theme_options_none() have test cases for $instance['widget']['type'] == 'node_reference_select', 'node_reference_buttons', 'user_reference_select', etc

Problematic if noderef / userref stay out of core - but even if they end up in core, this hardcodes the list of field types that are able to use option widgets.

We'd need to move away from testing the actual widget name, and instead find a way to determine that the actual FAPI element used has #type 'options_[select|buttons|onoff]'

Comments

puradata’s picture

puradata commented
Assigned: Unassigned » puradata

I am not sure what to do here, but it's listed as a 4 and has the word test in the description, so I'll give it a try.

puradata’s picture

puradata commented
Assigned: puradata » Unassigned

I don't know what to do here, so I'll take my name off the assigned so nobody thinks I am working on this.

Anonymous’s picture

Anonymous (not verified) commented

I'm bumping into this now with taxonomy term autocomplete widgets... I don't know if it affects my work, but I'm see what's going on.

mr.baileys’s picture

mr.baileys
Primary language Dutch
Location 🇧🇪 (Ghent)
commented
Status: Active » Closed (duplicate)

It looks like this was fixed as part of #635202: Remove #process pattern from option widgets.