[Forminator Pro] Allow Group Label for Name Field

1

The Forminator Name field has a toggle for Single name (input box) or Multiple names (First, Middle, Last). Each of course has its own label. But in a form that requests two names, do we need to be explicit in the label of each field?

Example:
– Father First Name
– Father Last Name
– Mother First Name
– Mother Last Name

It would seem more elegant if the Name fields were grouped so that we could have:
– Father (First, Last)
– Mother (First, Last)

Am I missing something that exists in styling?

Thanks!

  • splaquet
    • WordPress Warrior

    Personally, I don’t find enough native styling ability when using the multiple fields selection.

    It’s either:
    – use multiple field option and edit layout with custom css
    – use individual fields and lay them out exactly how you’d like

    It’s a shame, but my option is typically the second.

    Sorry Tony G … I realize that’s not the answer you were looking for :wink:

  • Nebu John
    • FLS

    Hi Tony G ,

    I hope you are keeping well today.

    The label field is not mandatory; you can always leave it blank if not required. You can place the label for the first field only, and the name filed will look grouped.

    Will this work for you? Or can you please explain this with an example if I understood it wrong?

    Kind Regards,
    Nebu John

  • Tony G
    • Mr. LetsFixTheWorld

    Both splaquet and Nebu John are correct. There is an awkward “clunkiness” with the complex fields that require us to make choices about whether to use them for their convenience, or to use separate fields for more versatility. With this application and another that I just posted, the best option is usually not to use the convenience controls. That’s really at the heart of my most recent experiences.

    John – Indeed, I have been doing what you suggest here. The first field is labelled for the group, and other fields have no labels, the “label” is in the placeholder or description. Just the fact that we’re talking about this confirms that a bit of funky effort is required to achieve the result. I don’t mind that, really – I often recommend such work-arounds when they are required.

    In this case I’m looking for an optional FieldSet container to encapsulate each of these convenience controls (Name, Address, etc) that includes other controls. So for example, with two names we will see “Your Name” and “Manager Name”, where each input field gets to use its own label as-designed. Or for Address we might wrap that in a Group for “Billing Address” and “Shipping Address”.

    Yes, right now we can Style the group, but we can’t label it. We need to take the extra step to put an HTML field before the group. This is another one of those “sure it works but it’s a small hassle” details where the UX is not optimal for the form designer.

    Overall I think the best way to approach this is to allow for designer groups, where we can create our own named field-groups, wrapped in our own tags of choice – Div, Span, FieldSet, etc. Then we can create our own convenience controls, like AddressS2 that has Street2, which is extremely common, or a LocalAddress that doesn’t have a country field, and where we always use the same default descriptions and placeholders.

    In short, the convenience controls are OK … until we realize that they are only a convenience for a limited set of applications. That’s OK, really. But it seems user-defined fields is the next step to overcome the limitations of the builtin convenience fields.

    Perhaps the request for now can be summarized as : Please add an option to all controls for a FieldSet wrapper, with Legend, that allows us to define the purpose of a control group for the user. Conditional Disable on the field (control group) must include the FieldSet if there is one.

    Any other ideas to skin this cat?

    • Tony G
      • Mr. LetsFixTheWorld

      OK, here’s another option: I just tried to wrap a group of Forminator fields with two HTML fields. No joy. The HTML field is “smart” and that precludes such creativity.

      Example:
      field HTML : <fieldset><legend>Test</legend>
      field Name : first, last
      field Address : street, csz
      field HTML : </fieldset>

      Nope, the HTML field auto-completes unclosed tags, and each HTML field is then wrapped in its own Div.

      We could solve this challenge if the HTML control has an option to Not modify any HTML, and to Not wrap the field in Div tags. This could mess up forms for those who aren’t careful, but it also opens up new possibilities … without requiring DEV to make broad changes anywhere else!

      “With great power comes great responsibility”.

      Now, I need to look to see if there is a hook that shortcuts the fixing and wrapping of fields. THAT would be the proper solution to all such woes. See how that works? THAT is why I ask for hooks and not changes!

    • Tony G
      • Mr. LetsFixTheWorld

      In case someone else thinks of this, I’m aware that we can have Sections in a Form, but a section truly breaks up parts of a form, and it’s over-kill compared to a smaller FieldSet.

      This is an example of what I’m trying to do (created in seconds at w3Schools) :
      [attachments are only viewable by logged-in members]