From the Formidable documentation, we should be able to use something like this in an HTML form field
[if x equals="Yes"]Your conditional content here[/if x]
Worked before and now it doesn't.
Yes, the HTML field follows a page break.
Any suggestions for a workaround?
Thanks
Can you be clearer on what you're trying to do? I have a feeling it's not going natively be able to do what you want, since the condition is only going to run when the page is displayed and then never again afterward. Also, you mention "after the page break". Does it work if you move it before the page break. And finally, the condition you have in your screenshot can be reduced to [If 25 not_equal=""]Hi [25][else]No name entered[/if 25]
<p>Thanks for the reply, Rob. It’s absolutely natively possible, as indicated in my post, it was working before, and also indicated in the link to the documentation.</p><p>Appreciate your willingness to help, and suggest that you may want to check before you make statements like ‘not going to natively be possible’, and then go on to give erroneous info thereafter as fact. Could send a less experienced developer down an unnecessarily unpleasant and confusing path.</p><p>This has been a much-used, well-documented, fully supported feature for quite some time.</p><p>One workaround is also in the linked documentation. Just use multiple HTML fields to display the desired content, using conditional logic to show and hide multiple HTML fields.</p><p>However, that’s a less than efficient or effective way to achieve the desired form behavior, it also introduces a level of technical overhead and additional maintenance. That’s why I was seeking a solution similar to the currently non-functional native solution.</p><p>HTML fields are great for building flows and experiences for users where indicating purpose and providing additional context is essential for helping them move through a form they may have never seen before or may not frequent that often. I often use them to introduce a little friction to actually slow down the flow a little to ensure folks understand where they are and what they’re doing.</p>
Exactly, the same issue I have right now.
Also, I can't make multiple conditionals work in the same HTML field, regardless whether they're nested or just one after the other.
I hope they fix this soon.
They’ve got a fix in the works. You can submit a support ticket at support.formidableforms.com and they’ll give you access to a pre-release that addresses the issue.
<p><p>Thanks. I'm still waiting for them to respond.</p><p> </p><p>Update: They shared me a pre-release version too, and it works.</p></p>
Yup. But just for HTML fields only and not the Paragraph and Hidden fields. They shared me Version 6.25.2b.
Glad that worked out. I'm too close to launch, so I have to keep versions locked down until I work through everything and go live. I've used the show/hide fields for now, when I can. It's a lot noisier in the build, and a bit slower in the overall audience experience, but that's ok for the launch, as the audience will be experiencing an entirely new way of interaction with and within the organization. And as is common for many small non-profits, there's precious little capacity to support member self-serve issues. 😛
Please login or Register to submit your answer
Staff replied 1 month ago
If you can reach out to our support team, we have a pre-release fix for this issue we can provide. We don’t provide files in the community site.
replied 1 month ago
Thanks, @Steve.