Hidden Fields Broken, Can’t Skip Pages/Form Steps, reCAPTCHA Ruins Aesthetic

  • Resolved FAOU

    (@faou)


    3 months, 2 weeks ago

    We just bought a subscription to the pro version, and it’s not going well. We are switching over from Forminator, and there is no support for the migration. In fact, I am starting to realize it’s because switching from Forminator to Fluent Forms is very uncommon. Forminator is way, way better than the free version of Fluent Forms, but Fluent Forms Pro is supposed to be better than Forminator (free or pro). Forminator is missing things like confirmation emails (aka double opt-in) and built in support for custom field values. Our initial experience with Fluent Forms Pro is frustrating.

    1. Hidden fields do not work right. Hidden fields have so many uses. They are like variables that you can set so that you do not have to change them again everywhere in the form. For example, if we made an intake form with Forminator, we could just duplicate it and change the value of the hidden field that we stored the company name in to avoid changing it everywhere in the form. You cannot do this with Fluent Forms (free or pro). After extensive attempts, we have to conclude that hidden fields in Fluent Forms cannot be used in the form at all, not in calculations or anything. They are pretty much broken.
    2. That leads us to the documentation. It is pretty bad. The developers clearly know how to code. The new features they have been adding are part of why we’re trying to switch. Nonetheless, the English often does not make sense, and the documentation rarely includes examples. For example, nowhere in the documentation does it say how to get the value from the first name field to do something as basic as address the person by name in subsequent pages of the form. I had to go back and forth between saving a form placing it on a page and inspecting that page to find the input name to use (names[first_name]) and then editing the form. Frustrating!
    3. Forces the Google reCAPTCHA icon to be on the WHOLE PAGE (you cannot close it or even scroll past it), like an unauthorized, unpaid ad for Google!!! Awful! Fluent Forms has no option to just place it somewhere inline in the form like Forminator. Fluent Forms has no respect for its customers’ aesthetic and the presentation of their forms. That alone is unacceptable.
    4. There is no option to skip pages conditionally! Google Forms has this ability for free! With Google Forms you can do far more advanced logic than with Fluent Forms by setting up a question to lead someone to a specific section of the form. At the very least, I expected Fluent Forms Pro to have a way to make steps/pages of multi-step forms conditional. The work arounds for this are ridiculously redundant.

    All that is to request the following:

    1. Please immediately fix the hidden fields bug so that it can be used as {dynamic.hidden} throughout forms. This is critical.
    2. Please put more examples in your documentation and tutorials. You all make flashy videos, but the videos avoid most of the complexity to seem simpler than real cases are.
    3. Please immediately stop placing the Google reCAPTCHA branding on every webpage with a Fluent Form! There should be an option to place it in one place on the form and not all over.
    4. Please give form steps conditional functionality.
    • This topic was modified 3 months, 2 weeks ago by FAOU.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter FAOU

    (@faou)

    Just found out (only via trial and error, there’s no info about this from Fluent Forms) that subscriptions cannot even be dynamically priced! In fact, it’s not just subscriptions; there is no way to set any of the payment fields’ prices to the value of a numeric field calculation. The calculation features in Fluent Forms are rendered somewhat useless for anything other than a quote calculator because the values cannot be used in the billing or payment features.

    Also, there is no official way to hide the calculation fields, so they have to be conditioned to be hidden. Forminator allows you to condition the calculations to be visible or not, but it also has a quick and easy checkbox option to just set it to be a hidden field.

    Plugin Support Amimul Ihsan Mahdi

    (@amimulihsanmahdi)

    Hello @faou,

    Thank you for reaching out and sharing your feedback with us. We sincerely apologize for the frustration and inconvenience you’ve experienced since switching to Fluent Forms Pro. We understand how important it is to have a seamless migration and a tool that fully meets your needs, especially when you are making such a significant transition. Unfortunately, Fluent Forms currently does not have any migration tool to migrate from Forminator, the only available options are WPForms, Contact Form 7, Gravity Forms, Ninja Forms & Caldera Forms. I have added this as a feature request and forwarded to our team.

    Regarding the hidden field, you can make any field hidden using the container class ‘ff-hidden’ as shown in the screenshot. For more information, you can follow our documentation. In this way, you can make a numeric field hidden and do your calculations.

    As for the documentation, our documentation team is continuously updating the documentations. I have forwarded your suggestion to our team so that they can make necessary changes. In addition, if you would like to refer a previous field in the step/conversational form, you can use the shortcode {dynamic.name_attribute} as shown in the screenshot.

    For the reCaptcha issue, the reCaptcha icon is loaded by Google. Unfortunately, its placement is controlled by their service. However, you can hide this icon using custom CSS. I have listed the CSS below for your reference, you can use it on your form’s Custom CSS/JS section

    .grecaptcha-badge { 
        visibility: hidden;
    }

    Furthermore, if you would like to hide a step based on conditional logic, you can hide the step by adding all the fields to a container. A container supports conditional logic so if you set the conditional logic on the container, the form step will be shown based on conditional logic.

    For subscription field, the calculation is not available. I have added this as a feature request. However, you can set calculation on custom payment amount field, please see this screenshot. The calculation will work same like the numeric field and you can follow the documentation. If you would like to hide a calculated field, you can use the container class ff-hidden as mentioned above.

    We value your feedback as it helps us improve, and we apologize again for the difficulties you’ve faced. We are here to support you, so if you face any further difficulties, please let us know via this support thread. We’re also available through our official support portal if needed.

    Thank you

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.