Closed (cannot reproduce)
Project:
Webform Conditional (Same Page Conditionals)
Version:
7.x-1.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
10 Jul 2012 at 22:27 UTC
Updated:
10 Apr 2014 at 14:21 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
zany commentedComment #2
kyleoliveira commentedFieldsets weren't responding to the conditions I was setting. This patch fixes that problem for me. Thanks zany!
Any chance this will get put into an upcoming release tedbow?
Comment #3
densolis commentedAll,
I am helping Ted with this module and will be talking with him tomorrow (8-30-12). I will bring this to his attention. Either Ted or I will follow up in the next couple of days
Dennis
Comment #4
densolis commented@kyleoliveira
I will test out the patch and get back to you I'm pretty new, so it might take me while.
Dennis
Comment #5
densolis commentedHi zany, kyleoliveira
I just completed a re-write of the user documentation. In that process, I exercised the development (7.x-1-dev) version of Webform Conditional module pretty extensively, but I could no duplicate your issue. Since I can not duplicate your issue, I'm not quite sure how to tell if the patch works.
Can you please see if this is still an issue with the 7.x-1.dev version of Webform Conditional. If it is still an issue, can you please provide an exported Webform node with the problem? That would help me immensely. Instructions are here.
Thanks,
Dennis
Comment #6
zany commentedUse this module to hide (toggle) a "Fieldset". It won't work because the selector is assumed to be
webform-component-SOMEID. But fieldsets actually get a class ofedit-submitted-SOMEID. Look at the HTML source of the form.Comment #7
densolis commentedZany,
I believe that I did the exactly the same thing as you did, but could not repeat your error. You can check out the following link at sixmiletech.com, which does what you want. I have updated the example on the sixmiletech.com site so it is a bit more intuitive. However, the revised example will not be available for a day or so. So I've attached a copy of the webform conditional demo that will be posted to the above sixmiletech.com web site. You can load it via Node Import and try it. You can also try the existing demonstration as it provides the functionally you require.
I would like to get this issue resolved, but I'm going to need your help. Can you please send me an export of the node that has the problem? If you do not know how to export the node, please read these instructions. If you have any questions, please me know and I will be glad to answer those questions.
Dennis
Comment #8
zany commentedDenis,
it seems CSS IDs are generated different for you. I'll try to figure this out. Thanks!
Comment #9
zany commentedwebform's components/fieldset.inc clearly specifies
'#attributes' => array('class' => array('webform-component-fieldset'), 'id' => 'webform-component-' . $component['form_key']),but this gets overridden in some setups with a CSS ID of edit-submitted-*form-key*.
I couldn't locate that though.
Closing this.
Comment #10
tedbowComment #11
zany commentedI can't seem to locate what triggers this behavior. But there is this code in includes/form.inc's form_builder() function:
Thats's were the wrong IDs come from. I guess somewhere down the chain #attributes['id'] isn't propagated to #id.
For reference, attached is a patch on webform that works fine with webform_conditional.
Comment #12
Stalski commentedThe explanation is correct.
I needed it in the select component , so I added :
So even the str replace is needed for me. After that it works.
It can easily be reproduced on longer existing sites where webform module was installed in early stages. Somewhere along the way, in the same 7.x-3.x branch of webform, it got fixed.
Comment #13
steeph commented#11 works for me. But not for fieldsets that are inside another fieldset.