When using a condition to either show or hide a form field based on value of a previous field, the value of that conditional field does not show in the email.
I have a radio button field the asks for Routine or Urgent. Another field below that asks for additional information if Urgent is selected.
Putting a condition on the additional information field works, in that it will hide/show depending on the radio button option. BUT if I select Urgent and add some information to the addiontal info field that information is no longer available as a %value[field_key] in an email. It returns blank.
If I remove the condition is works.
Any thoughts
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | node-export_webform_1335298342.txt | 7.62 KB | Anonymous (not verified) |
| #4 | node-export_webform_1335148930.txt | 7.31 KB | tedbow |
| #2 | email_value_issue_example.txt | 10.47 KB | Anonymous (not verified) |
Comments
Comment #1
tedbowNo idea off the top of my head.
If you would like me to take a look at this problem the process would be faster if you could export problem Webform. You can see instructions and the reason here: http://www.sixmiletech.com/content/providing-exported-webforms-issues-we...
Comment #2
Anonymous (not verified) commentedI'm having the same or a similar issue myself on 7.x-1.x-dev - wasn't sure if I should open a new ticket, but it seems like the same issue as here.
If a conditional fieldset is never opened, and the email template uses a %value[fieldset][field] token, when the emails are sent, %value[fieldset] will be removed but [field] will remain if the field is blank. If the field is filled in, then it will behave normally.
I have attached an export to help illustrate this. To duplicate the results, try filling out none of the fields (none are required), then try filling out all of them.
Any insight or help you can give would be great - I don't mind working on this or testing any patches, just need to be pointed in the right direction.
Comment #3
Anonymous (not verified) commentedComment #4
tedbowThis is actually a problem with Webform and not this module.
I have attached a similar webform that uses the multi-page conditionals instead. It still has the same issue. The issue should be reported to Webform.
Try out the form with Webform Conditional disabled. The "Fieldset 1" on page 2 is conditional "selector" on the previous page.
Comment #5
Anonymous (not verified) commentedAh, thanks so much for the help.
I did some digging and found that the code at http://drupal.org/node/991024 is related to this issue - the parent fieldset is being stripped out before the child field is recognized, leaving the child field to be printed.
Luckily, I tried the new token pattern and it seems to resolve the issue completely. I'm attaching a new export to illustrate this, but just to note for others -
This does not work = %value[fieldset_1][text1]
This is the new way, which does work = [submission:value:text1:nolabel]
Comment #6
akshita commentedhave you upgraded the webform ??
I am also having same issue . when you get chance please check the link : http://drupal.org/node/1058018 -- #27 and #28
Thanks
Comment #7
densolis commentedAll,
This is not a webform conditional issue - please see comment # 32 on node on 1058018.
This is a webform issue and has been fixed on version 7.x-4.x version of webform, but has not been and will not be fixed on the 7.x-3.x version of webforms. Please read the webform issue %value[fieldset][field] does not work in email templates for conditional fields for further details.
As far as I've been able to research, you must be on version 7.x-4.x of Webforms for "[submission:value:text1:nolabel]" discussed in comment 5 (see above) to work.
Dennis
Comment #8
densolis commentedUpdated "Assigned".
Comment #8.0
densolis commentedupdate