Using Conditional Wrapper outside form

How To
1

Hello,

I need to display certain information in a sidebar that’s outside a form, but some of it depends on values selected in some of the form fields.

I tried using the Conditional Wrapper element, but it doesn’t seem to work outside the form.

I also thought of trying Bricks’ own Conditions with the Dynamic Data tag {brf_form_live_value} but the problem with that would be that Bricks Conditions will only check the value on page load, and not when the value changes.

Is there a way to connect the Conditional Wrapper element to a form (using the form ID) so that we can use it outside of the form itself?

2

Pro Forms features do not work outside the “Pro Forms” wrapper. Everything needs to be inside the <form>. But in theory, you could even wrap your entire content with the “Pro Forms” element. Wrapping a large section—or even an entire page—in a single is technically valid and perfectly fine as long as the page itself represents one logical form. If your form is complex and requires additional sections (e.g. explanations, progress indicators, or layout areas), it is absolutely acceptable to include them inside the same Pro Forms wrapper. Everything that is not part of the form (such as global navigation or unrelated actions) should remain outside the form element.

3

Thank you Daniele. That was the first idea I tried as well, but immediately ran into a limitation: it doesn’t seem to work out with multi-step forms, because everything inside the form that’s outside the current step gets hidden until we reach that step. The structure I tried was something like:
form

  • div for 1st column
    • fields
    • step 1
    • fields
    • step 2
    • fields
    • step 3
    • fields
  • div for second column
    • live value fields

Now with this structure, the steps seemed to prevent the second column div from rendering. If there was a way to categorically define the start and end of collectively all the steps and then keep all the steps contained within that start and end, we could then have more flexibility to place fields and other data outside of the steps logic that don’t really belong inside the steps themselves.

It could be that it’s already possible and I’m just missing something here.

Speaking of steps, it’ll also be great to be able to place the summary wherever we like, such as a sidebar like my use case. Currently, the summary seems to be tied into the steps logic as the final step.