Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I have created a flexified in my cck. suppose i have submited the cck form containing flexifield and it contains a validation error also. Then one 'Array' text appears before flexifield. It is not coming form my custom module. I have tested in various drupal installations same issue is coming. Apart from that flexifield working fine.
Please help. Thanks in advance.
Comment | File | Size | Author |
---|---|---|---|
flexifield.JPG | 33.22 KB | nirmal_george |
Comments
Comment #1
dddave CreditAttribution: dddave commentedThis doesn't seem to be a Drupal core issue, therefore moving to flexifield issue queue.
In addition you should use the current Drupal release (or at least 6.15 because of a bug in 6.16). There were multiple changes between 6.9 and 6.16.
Comment #2
artur.martirosyan CreditAttribution: artur.martirosyan commentedGot same problem with 6.15
Aside from displaying 'Array' it also makes fields draggable, even though normally dragging is disabled.
Comment #3
feedbackloop CreditAttribution: feedbackloop commentedHas anyone been able to track this down?
Comment #4
lupas CreditAttribution: lupas commentedI get the same problem and wasn't able to trace the error.
Also, the table ID for the CCK group containing the flexifield changes from:
group_formacion_field_flexiformacion_values
to
field_flexiformacion_values
Comment #5
lupas CreditAttribution: lupas commentedMore information:
I've got several flexifields defined in my content type. This issue only happens to the first one appearing on the node form.
Comment #6
yogeshchaugule8 CreditAttribution: yogeshchaugule8 commentedhello All,
Same problem here.
I am using 6.x-1.0-alpha5 version of Flexifield and 6.16 of Drupal.
While debugging this issue, I came across "_flexifield_alter_multiple_values_form" function in "flexifield-widget.inc" file and found that commenting line "$aElement['#input'] = TRUE;" removes the Array text from the form.
There is also a note of author, which says
"For the #process function to work, we need to set #input,
but doing so affects #value, and we want to be able to
clean that up"
I haven't look at how this module saves the data into DB or do other processing, so can not say whether this will affect functionality/flow of this module and also don't know whether this is the right way to do this.
Comment #7
yogeshchaugule8 CreditAttribution: yogeshchaugule8 commentedCommenting $aElement['#input'] = TRUE; causes another issue to arise.
Did anyone found solution for this.
Comment #8
vivek.saurabh CreditAttribution: vivek.saurabh commentedIs there a way to hide the text "Array" via css or javascript .