Closed (outdated)
Project:
Webform Conditional (Same Page Conditionals)
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2012 at 13:32 UTC
Updated:
25 Sep 2020 at 16:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tedbowCan you check to make sure that all your websites are using the same version of Webform Conditional and Webform?
Comment #2
SophieG commentedOK
working on :
webform 6.x-3.15
webform conditional 6.x-1.0-rc2
not working on:
webform 6.x-3.14
webform conditional 6.x-1.0
Comment #3
tedbowThanks.
In both cases 1 of the modules is not the latest version. It would be very helpful if you could test with the latest version of both modules.
Please let us know if the above works.
Thanks
Comment #4
SophieG commentedok, the thing is that i have people using the webform module right now, so i did not want to update it yet... Anyway, i think i'll have to wait, but as both the module are not in dev or rc and that nothing seems to indicate that there is some conflict...
Thanks for your help
Comment #5
tedbowI understand. This would probably better to test if you could work on a local/development environment. Please don't forget to report back if this clears up your problem.
Comment #6
tedbowJust FYI, I tested
webform 6.x-3.15
webform conditional 6.x-1.0
and
webform 6.x-3.14
webform conditional 6.x-1.0
On my development site with some test forms.
Both are working for me but different forms may act differently. You might want to check if the pages are having an Javascript errors. Also the other main difference between your sites could be your themes(if the sites are using different themes) and conflicts they might have with "webform 6.x-3.14"
I probably can't help you with this until you are able to update Webform but these might be some things to look at.
Comment #7
tedbowMoving to minor b/c not using latest webform, changing title to reflect
Comment #8
Anonymous (not verified) commentedI got similar problem after upgrading webform conditional 6.x-1.0-rc2 to 6.x-1.0. The webform module is version 6.x-3.15.
Comment #9
tedbow@jennifer_1 could check to see if moving back to 6.x-1.0-rc2 fixes your issue?
Comment #10
Anonymous (not verified) commentedThank you tedbow. Webform conditional 6.x-1.0-rc2 and webform 6.x-3.15 work well. I only upgraded our staging server so it doesn't bother me so much.
Comment #11
tedbowIf anyone is still experiencing this problem please provide and Webform export.
Instructions here
I am postponing all issues that need a exported Webform example.
Comment #12
grguth commentedIt will take me a little time tomorrow to work up a small example, however, I was able to quickly generate a test environment with conditional rc2 and webform 3.15 and compare it to conditional 1.0 and webform 3.15. The most obvious issue is that there is no conditional link on a fieldset with 1.0. So when you develop a new form, its not possible to have a conditional fieldset. However, if there is an existing form that already had a conditional fieldset, it continues to work on either combination. Editing that existing form does not show a conditional link on the fieldset, even though its obviously there.
Comment #13
grguth commentedWell, that was interesting ...... testing with webform 3.15, conditional 1.0
webform 1:
added select field, two options (cash/check)
added fieldset, conditional link on, set for check
added field, moved into fieldset
result: fieldset did not appear until select for check done -> OK
webform 2:
added fieldset 1, no condition link on
added fieldset 2, no condition link on
added select field, moved into fieldset 1 (cash/check again)
added field, moved into fieldset 2
checked fieldset 2, still no condition link
result: both fieldsets always present, choice irrelevant
webform 3: in case order of creation was an issue
added fieldset 1, no condition link on
added select field, moved into fieldset 1 (cash/check again)
added fieldset 2, no condition link on
added field, moved into fieldset 2
result: both fieldsets always present, choice irrelevant
checked fieldset 2, still no condition link
If you really want the nodes exported I'll be glad to do it, but the error seems to be related to the select field being inside or ourside a fieldset.
I will repeat later on 3.15 / RC1 combo.
Comment #14
tedbowgrguth thanks for all this info. I will try to get to this in the next couple of days.
Comment #15
grguth commentedTesting with webform 3.15, conditional RC1
webform 1:
added select field, two options (cash/check)
added fieldset, conditional link on, set for check
added field, moved into fieldset
result: fieldset did not appear until select for check done -> OK
webform 2:
added fieldset 1, no condition link on
added fieldset 2, no condition link on
added select field, moved into fieldset 1 (cash/check again)
added field, moved into fieldset 2
checked fieldset 2, condition link on, set appropraitely
result: fieldset 2 did not appear until check selected -> OK
webform 3: in case order of creation was an issue
added fieldset 1, no condition link on
added select field, moved into fieldset 1 (cash/check again)
added fieldset 2, condition link on
added field, moved into fieldset 2
result: fieldset 2 did not appear until check selected -> OK
Again, I'll be glad to export nodes, but this doesn't appear to be an execution problem, but a setup problem.
Comment #16
SophieG commentedOk,
i have updates both webform and webform conditional. I have now the latest stable version (3.15 and 3.1), but it is not working more...
I still get these buggy lines :
<div class="webform-component webform-component-radios" id="webform-component-select1" style="">It seems not all the code is added to these components, but i really don't understant why... I have no js error in my firebug console.
Here is the node export code :
Anyone to help me please ?
Thanks
Comment #17
tedbow@SophieG, the form you export works for me with webform 3.15. Can you try this form out on a new install of drupal with just webform, webform condtional and node export enabled? It maybe related to another module?
Comment #18
tedbow@grguth, If you could export the forms that would be great. Please but a description the body field of what should happen with the form and the problem you are seeing.
Thanks
Comment #19
grguth commentedAttached the two webforms.
Comment #20
grguth commentedI may not have clearly stated what these two test forms are supposed to do. There is a selection field, and then a fieldset containing another field. Depending on what option is selected in the first field, the fieldset and its field are either displayed or not. In RC2, the fieldset does open and close as the options are selected. In 1.0, this doesn't happen, but as previously mentioned, the problem goes back to building the forms. In RC2, the ability to make the fieldset conditional appears when you build the form, but in 1.0, the option isn't there. Naturally, the webform exports are different because the webform conditional fields are never inserted in 1.0. So yes, the exported nodes are different, but the problem really occurs during webform definition. If you build the form in RC2, and then install 1.0, the webform works just fine. You just can't modify or build an equivalent with 1.0.
Comment #21
tedbow@grguth, I see the problem you are describing. It goes away when I am using the 6 dev version. Can you try this version? Does this fix it for you?
Comment #22
tedbowComment #23
grguth commentedDownloaded the 1.0+2-dev version last night, tried it today, and its OK.
Comment #24
blackspiraldancer commentedJust my 2 cents - I tried with Webform 6.x-3.17 and Webform Conditional 6.x-1.0 with no luck.
After reading this issue, I've replaced Webform Conditional with the 6.x-1.0+2-dev and run the update.php. Everything went in place without editing anything.
Comment #24.0
blackspiraldancer commentedsmall mispelling
Comment #25
tabestan commentedI have the same issue.
My webform has a select-option field where one of the option if the trigger. Using the Garland theme, it works as expected. The issue is when I use a custom theme. The field that is supposed to be hidden is visible and there's no display:none/block
<div class="webform-component webform-component-radios" id="webform-component-stuffid" style>I have the latest version of the webform and webform_conditional modules.
Comment #26
avpadernoComment #27
avpadernoI am closing this issue, which is for a not supported Drupal version.