Needs work
Project:
Multistep (D7)
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Oct 2011 at 00:27 UTC
Updated:
21 Jun 2012 at 02:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
chrislabeard commentedAnybody have any idea why this is happening?
Comment #2
WoozyDuck commentedSame issue here
Comment #3
fnikola commentedi'm experiencing the same issue with multistep 6.x-1.5 and select (or other) 6.x-2.11. I am allowed to submit the page with the select or other value entered (in the other textbox) on that page, but then all other pages/steps fail with the illegal value error.
Comment #4
nathanhilbert commentedThis is hitting the form validation of CCK text field module on line 156.
if (count($allowed_values) && !array_key_exists($item['value'], $allowed_values)) {
$item['value'] is passing here with a value of "off" which is outside my allowed values of 0 and 1. I can only guess that core provides the default "off" if the access is denied as happens in the multistep module on line 548 :
$form[$field_name]['#access'] = FALSE;
I have a provided a patch that changes the field type to "value" essentially making it a hidden field, but allowing the values to be passed, which is able to pass the text.module validation in cck. I'm not sure of the implications of this beyond my specific use case, but it works. I'm open to safer ways of allowing values to be passed without the user seeing them in the multistep form.
I have not tested this with select (or other) module.
Comment #5
nathanhilbert commentedDisregard the patch. It doesn't fix anything. A simple change that doesn't help with the select (or other) module: change your allowed values for select field as "off" and "on". I think the fix is beyond my knowledge.
Comment #6
marleo commentedSame problem here. Replaced select_or_other with cck_select_other and it worked. Would've preferred to keep the former, though, because of UI differences.