Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
puradata CreditAttribution: puradata commentedI 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.
Comment #2
puradata CreditAttribution: puradata commentedI don't know what to do here, so I'll take my name off the assigned so nobody thinks I am working on this.
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedI'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.
Comment #4
mr.baileysIt looks like this was fixed as part of #635202: Remove #process pattern from option widgets.