Closed (fixed)
Project:
Webform
Version:
7.x-4.0-alpha9
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Aug 2013 at 17:34 UTC
Updated:
21 Aug 2013 at 07:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
quicksketchThanks @drubin for making a new issue. So if I understand this correctly, this situation only occurs if your first page contains *only* markup components? If you add a textfield to the first page the error goes away?
Also glad to see use of Surveyor. :)
Comment #2
quicksketchRe-reading your request, I'm not sure that's what you were saying. What's on the first page of your form?
Comment #3
drubin commentedI started fresh and retested:
If I have a one page form with same-page conditionals -no notice.
If I add a pagebreak and put only markup on the firstpage I get the above notice on the second page.
If I add a textfield to the first page, the notice no longer shows up on the second page.
When I remove the textfield from the first page the notice returns on the second page.
Comment #4
quicksketchOkay, great! So this seems like an easy problem to solve. The $form_state['values']['submitted'] array is probably empty just because there isn't any data that's actually submitted by the first page (markup components don't submit any data). Sounds like we're just missing a simple IF statement.
Comment #5
quicksketchThis patch should solve the problem. Considering it's so trivial, I've committed it to the project directly. This seems to only affect the 4.x branch of the module, so no need for a backport. Thanks again for the report!
Comment #6
quicksketchComment #7.0
(not verified) commentedAdded code tag