I've got a whole fieldset that I'm cloning and it has a few conditionals set on some components in the fieldset.

The cloned fieldset conditional rules seem to get neglected.

Perhaps a simple solution would be to create different keys for said fields and edit the conditionals?

Comments

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
CreditAttribution: tedbow commented

@thadbloom, can you check to see if this same problem happens when you use conditionals that are for multipage forms?

densolis’s picture

densolis CreditAttribution: densolis commented
Issue tags: +waiting-for-user

Status update 8-29-12. We are waiting on user response to our question of 6-20-12.

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
CreditAttribution: tedbow commented
Priority: Normal » Minor
Status: Active » Postponed (maintainer needs more info)

postponing until answer from #1

grahamC’s picture

grahamC
Location Oxford, UK
CreditAttribution: grahamC commented

From my reading of the report (@thadbloom, correct me if I'm wrong!) the situation is like:

* Fieldset
1. Component A
2. Component B (shown if 1. is true)

Where cloning should(?) result in:

* Clone of Fieldset
3. Component A
4. Component B (shown if 3. is true)

But actually, 4. is still dependent on 1.

I think this situation would be impossible to create with multi-page conditionals, as this is specific to having both conditional component and dependent within the same fieldset.

densolis’s picture

densolis CreditAttribution: densolis commented

grahamC,

Now that I have some specifics, I will play with it. I should be able to check this out in the next day or two and get back to you. But I understand the issue now.

densolis’s picture

densolis CreditAttribution: densolis commented

Webform clones and controls all the components. Webform conditional just control the conditionality.

The dependencies are controlled by the fields keys. To change to the described behavior, Webform conditional would have to change the keys for the components and Tedbow does not believe that Webform conditionals should be changing the keys (as this is controlled by Webform itself).

However, I believe that you can manually change the dependency (and keys if necessary). The only time that would be a problem is if you have a very complex dependency chain or a lot of dependencies in a cloned field set. I will test it and verify if this works,

Per Tedbow (Webform conditional maintainer), cloning same page conditional fields would require changing the keys and he feel that should be task for Webform or at least we should think about what the consequences would be. I feel like there will more consequences for changing the keys than for not(and having the user update dependencies manually.

Since Webform wants to clone everything, I think you should put this in the Webform issue queue with a link to this issue. If quicksketch (Webform maintainer) wants us to do something, we will be happy to work with him. We just don't want to step on Webform's toes.

I will test the above "work around" in the next few days and let you know if it works. I'm have system problems right now, so I have to get my development system backup and running.