Closed (fixed)
Project:
Webform
Version:
7.x-3.18
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
2 May 2013 at 20:17 UTC
Updated:
16 Jun 2013 at 09:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
pixel8r commentedforgot the screenshot to show what i'm talking about.
Comment #2
densolis commentedLet me take a look an it an I will get back to you shortly.
Comment #3
tedbowThis text is actually coming from the Webform module itself so switching to that project.
Comment #4
tedbowThis text is actually coming from the Webform module itself so switching to that project.
Comment #5
quicksketchIf you're doing any kind of conditional actions at all, I'd suggest using the 4.x version of the module, which has significantly improved conditional handling. You no longer need to use keys at all, since all select list options are listed for you. It even supports date and time elements in addition to text and select components. Additionally it supports same-page conditionals natively, so you don't need Webform Conditional any more.
All-in-all, we know the conditional support in 3.x is not very good. If you're using it at all, I suggest upgrading to 4.x. We won't be making changes to 3.x in this case, because it's not as simple as it sounds. If you're using a text field component for example, there are no "keys", so the description would need to change based on the component type used. I'm moving this to fixed so it stays in the queue for any further updates, but long-term this is a "won't fix" for the 3.x branch.
Comment #6.0
(not verified) commentedadded more details