I'm running an admittedly complex webform - a 'branching' multipage survey.
The issue I'm finding is that when going from one conditional page to the next, sometimes the sub-pages load, and sometimes they don't.
An export (from webform_share) is attached for reproducing the issue.
If you choose an area of expertise as computer science, you'll be taken to a subpage that lists areas of computer science you can choose. Two of these are deeper level pages - Foundations and Theory, and Software Engineering. If you choose both, you get both subpages (indicates the conditionals are correct). If you choose only Software Engineering, you not only don't get the subpage, you don't even get the next (non-conditional) page.
It happens in multiple places. For example, if you don't choose any areas of 'Expertise or Interest' you should go to Section 3. It skips to Section 4.
I'm really stumped. I've quadruple checked that all the conditional fields and weights look right, and am left thinking there must be a bug in here somewhere.
If I'm trying to do something unsupported, or if I'm doing it wrong, PLEASE let me know. :)
| Comment | File | Size | Author |
|---|---|---|---|
| webform-webform-6666.txt | 68.7 KB | srees |
Comments
Comment #1
srees commented*bump*
Comment #2
quicksketchThe problem you're describing does seem to be a misconfiguration issue. In Webform's conditionals, you're allowed to not only skip individual components, but entire pages.
According to your configuration, you've skipped each individual component on a page, which is a fine way of handling the problem; though a bit more tedious. However after marking each component as conditional, you've also marked the "End of page" component as conditional on the same criteria. Webform thinks of these page breaks as "Beginning of next page". If you put a conditional on that component, the *entire page* will get skipped. So that's why you're seeing two pages skipped when "foundations_and_theory" is not selected, because it's the conditional for all the components on a page AND the conditional for the entire next page. Removing the conditionals on the page breaks should fix the problem.
Or alternatively (what I'd recommend for simplicity), if you want to skip entire pages put the condition only on the page break component before the page you want to skip. Renaming your page breaks from "end_of_page_x" to "start_of_page_y" might also help avoid confusion.
Thanks for your e-mail and interest in Webform.com. Using Webform.com may have avoided this problem since the latest version of Webform has a revamped UI for conditionals, which makes things easier to understand and configure than the 3.x version of the module.
Comment #3
srees commentedThanks quicksketch! This worked.