Closed (duplicate)
Project:
Webform
Version:
7.x-4.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2014 at 22:05 UTC
Updated:
28 Mar 2015 at 14:52 UTC
Jump to comment: Most recent
Comments
Comment #1
adanielyan commentedI have the same issue. Can't use any field values from previous pages on other pages on paginated forms.
Comment #2
danchadwick commentedI would need to read the code to figure out whether this is supposed to work, but it sure sounds like it should. Remember that form_keys within fieldsets much include the parents as a path. Maybe this is the cause of your issue?
Otherwise it would be great if someone could do some digging and figure out what is going on here. I can't personally debug every issue. ;)
Comment #3
adanielyan commentedThank you for responding!
In fact none of the [submission:] tokens work on the form, even the [submission:sid]. And I don't have any fieldsets. I tried this on a clean Drupal installation with only webform, views, and token modules installed. I am struggling with this issue for a few days now and don't know where to start digging in. Any advice would be helpful.
Comment #4
salvatore.riegler commentedSubscribing. I'm having the same issue.
Comment #5
danchadwick commentedSubmission tokens are not valid as default values or in the description field for components. The submission doesn't exist when the form is being filled out (unless there is already a draft or the user is editing an existing submission).
I suspect that this sort of functionality would be added via the conditionals interface, where value can be set when other values are changed. Tokens could be supported there.
This would be pretty complicated to implement, as javascript support would be needed for intra-page conditionals. I do like the feature, however, and would be receptive to a patch.
Comment #6
danchadwick commentedComment #7
danchadwick commentedNow implemented. #2415849: Conditional actions: set values, checked, unchecked.