Closed (cannot reproduce)
Project:
Select (or other)
Version:
6.x-2.8
Component:
CCK / Field API widget
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Oct 2011 at 10:17 UTC
Updated:
17 Oct 2011 at 18:50 UTC
If there is no allowed values set for the field, when user choose to enter a custom other value,
form validation failed with a "illegal value" error displayed.
The issue is tracked down to be in the function "select_or_other_content_allowed_values_alter".
In which even there is no allowed values set on the field,
it adds all available options to allowed values list, which causes the custom value to fail validation.
When no allowed value is set, the default action should be to allow any value.
So a simple solution would be to check the number of values on the allowed values list first.
If no value exists, then simple do not add available options to the list.
Comments
Comment #1
danielb commentedMmm, OK that seems like a really unlikely bug, because this version was released almost 3 months ago and no one has said anything, and the CCK support has been there for two years. I use it all the time too.
What version of CCK?
Comment #2
danielb commentedWorks fine. CCK 2 and 3.
10 minutes of my life right there.
Comment #3
landing commentedI am getting this error when I try to use an embedded node form (it works fine on standard node forms).