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.Dammit, Core!
It looks like I will need to rewrite / duplicate Allowed Values settings code, which will be a HUGE UX fail as there will be TWO form elements describing the same thing (one on the field and one on the widget level). In core, it makes no sense to allow you to remove Allowed Values, but in a select other list it does since you may want to try it out, edit a node, and then get bitten in the butt when you want to take it out.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1074914-allowed-values.patch | 875 bytes | mradcliffe |
Comments
Comment #1
mradcliffeOr I can remove the validate for that for cck select other widgets?
Comment #2
mradcliffeNope, I am not going to be able to do this either. I think I am screwed either way here.
The only option is to code our own field at this point because core list field is fundamentally broken for contrib modules that want to do funky things like this.
Comment #3
mradcliffeI guess I can just disable the element_validate for list allowed values. This will allow that functionality, but allow users to remove allowed values from cck_select_other list fields.
It should re-enable the element_validate if the widget changes back.
Comment #4
mradcliffeFound some more time to run tests in the coder lounge.
Committed.