Multistep module breaks multi-valued fields

I'm encountering the same thing. The first item in the multigroup appears, then when "Add More Values" is clicked, a new row in the multigroup is created, but it is empty. Works as expected with multistep disabled for this content type (multistep module still enabled).

Eventually one of these will have to be marked as a duplicate, but for the moment I'd like to call attention to the test setup I made and reported at #579136-13: Multigroup module breaks with Multistep that clearly shows the behavior.

http://devel.splicer.com/ is a clean install with minimal modules. It demonstrates the incompatibility between multistep and cck-multigroup. It also shows that the problem is not limited to multigroups but to all cck fields that accept more than one value.

Hello guys! Took me a while to get down to this, sorry for the delay.

I realized that when the AHAH call is made, its internal URL arguments are different from those in the node edit form. The multistep module calculates the step based on the URL arguments, which meant that when you clicked on "Add another item", it was defaulting the $step of that field to 1, which in turn meant that it wasn't being shown on any step other than 1.

Anyway, I added a new condition to calculate the step for the js_add_more call and added a new function that calculates what the step should be for that specific field in the current content type.

Some things I still need to test/take into consideration:

• If the field is not within a group (see #585610: Make fields (instead of groups) available on different steps).
• Different types of multi-value fields from 3rd party modules (e.g. Date).
• Multigroup module (see #579136: Multigroup module breaks with Multistep).

Please test this patch and let me know your thoughts. I'll keep working on the above issues, and eventually we can decide whether this will take care of #579136: Multigroup module breaks with Multistep.

edit: I forgot to mention that I'm using CCK-6.x-2.5.

New patch. Made it work with with Multigroups in CCK-6.x-3.x-dev (2009-Oct-05) by ignoring the first argument of the "Add another item" URL call, which dictates whether it's content or content_multigroup, and focused only on the js_add_more clause.

Also tested it with different field/widget types inside both multigroups and regular groups. It appears that as long as the widget module allows CCK to handle the multi-value, it should work (which is the same condition that allows content_multigroup to work).

I committed the patch into the new development snapshot. Please update and use that one from now on.

Development snapshots are updated nightly. Re-download it today, or do a checkout directly from CVS (which is updated real-time).

Look for line 576 on multistep.module:

function _multistep_get_field_step($field, $type) {
  $step = 1;
  $group = _fieldgroup_field_get_group($type, $field);
  $groups = fieldgroup_groups($type);
  $step = $groups[$group]['settings']['multistep']['step'];
  return $step;
}

re opening this bug report.

Reading #12

variable $step is being set to 1 but being overridden in the line just above the return in which if the $groups[$group]['settings']['multistep']['step']; returned a null or false the multigroup or multivalues will not display. Attaching a simple patch to check whether the groups are returning either than false

subscribing

Thanks for the patch, garrizaldy!

Based on that, I changed the code to verify whether the group is a multi-valued field or a multigroup, and only override $step if there is a value to override.

The change is now in the latest development snapshot.

Have the latest dev. version and still having the same problem. When "Add Another" buttons are clicked, the entire field is disappearing - both in "View Entire Form" and during the multistep process.

I'm also having the same problem..

amaisano's issue seems to be #680746: Add an item will only work on step 1 of any multistep form. Reverting.

I still have this issue. I noticed that it doesn't matter if the field is on step 1, it still doesn't work.
But, if I'm logged in as admin, it works on any step.
Could this be related to permissions?