When you have a multistep form then the conditions for field states might use the fields from other (mostly logical previous pages). In this case the conditions are not evaluated because this is done with javascript and it has no idea about the fields from other pages.

In this module I tried to create WebformHandler that will try to evaluate the conditions.
I think this feature may be useful.

Please help to develop it.

The initial code could be found here https://github.com/artemvd/webform_crosspage_conditions

Comments

a.dmitriiev created an issue. See original summary.

a.dmitriiev’s picture

a.dmitriiev commented

I tried to find the discussion where this topic is referenced, but with no luck. Maybe somebody can also point the related issue to me.

Thanks.

jrockowitz’s picture

jrockowitz commented
Status: Active » Closed (won't fix)

I added a reference to this project to the list of Webform Add-Ons. Hopefully, this will encourage more people to get involved.

xlith’s picture

xlith commented
Category: Feature request » Bug report
Status: Closed (won't fix) » Needs work

I tried the addon on my site by it doesn't work. Maybe i did something wrong.

a.dmitriiev’s picture

a.dmitriiev commented

thank you @jrockowitz

mmaciusowicz-rr’s picture

mmaciusowicz-rr commented

This is possibly something that can be addressed together with server-side conditional validation. Firstly, this would help prevent situations when validation is applied to fields that are not properly displayed. Secondly, both issues seem to be related to identifying when a given state and condition is applicable, and then modifying the element accordingly. I have done some work on a patch that may help address both issues: https://www.drupal.org/node/2875949#comment-12198843

jrockowitz’s picture

jrockowitz commented
Status: Needs work » Fixed

@see #2900719: Server side Conditional Logic using #states API

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.