Form Theme Block Naming & Creating our Theme!

Hi,
I have a problem with theme block code actually I have duplicate validation errors:

`
{%- block form_row -%}

{%- set widget_attr = {} -%}
{%- if help is not empty -%}
    {%- set widget_attr = {attr: {'aria-describedby': id ~"_help"}} -%}
{%- endif -%}

{{- form_label(form, null, {
    label_attr: { class: 'sr-only' }
}) -}}
{{- form_errors(form) -}}
{{- form_widget(form, widget_attr) -}}
{{- form_help(form) -}}

{%- endblock form_row -%}
`

I searched for symfony documentation <a href="https://symfony.com/doc/current/form/form_customization.html#form-form-view-variables&quot;&gt;https://symfony.com/doc/current/form/form_customization.html#form-form-view-variables&lt;/a&gt; and I find next:

remove {{- form_errors(form) -}} from form_row block and add it above form_row(s) rendering like:

`
{{ form_start(registrationForm, {

    attr: { class: 'form-signin' }
}) }}
    <h1 class="h3 mb-3 font-weight-normal">Register</h1>
    {{ form_errors(registrationForm) }}
    {{ form_row(registrationForm.email, {
        attr: { placeholder: 'Email' }
    }) }}
    {{ form_row(registrationForm.plainPassword, {
        attr: { placeholder: 'Password' }
    }) }}
    {{ form_row(registrationForm.agreeTerms) }}
    <button class="btn btn-lg btn-primary btn-block" type="submit">
        Register
    </button>
{{ form_end(registrationForm) }}

`

This code works for me and it doesn't have duplicated validation error messages.

I am using to Symfony 5.1 and "symfony/form": "5.1.*".
My question: Am I doing something wrong and what is explanation for duplicate error messages.

@Vladimir Žarčanin,

Hey that looks weird. It shouldn't be duplicated in this case. Can you create a gist with related files or maybe github repo for more information?

Cheers!

Same here ;)
This happens because the errors are rendered on every form_label and not on the form_row.
Not sure if this has changed since in the bootstrap_4_layout.

Just remove the error rendering from the custom override.

That sounds very possible - thanks for posing the solution elkuku :).

Actually while following the tutorial and digging through the symfony docs I found a big red note here: https://symfony.com/doc/cur...

I love documentation :D :D :D

"There is a password_widget block but, when the label is being rendered, there is not a password_label block."

How does it know that it needs password_label block?

In here I dont see:

`{%- block password_widget -%}

{%- set type = type|default('password') -%}
{{ block('form_widget_simple') }}

{%- endblock password_widget -%}`
{%- block form_widget_simple -%}

{%- set type = type|default('text') -%}
{%- if type == 'range' or type == 'color' -%}
    {# Attribute "required" is not supported #}
    {%- set required = false -%}
{%- endif -%}
<input type="{{ type }}" {{ block('widget_attributes') }} {% if value is not empty %}value="{{ value }}" {% endif %}/>

{%- endblock form_widget_simple -%}`

Hey Lijana Z.!

Sorry for the slow reply!

There is a password_widget block but, when the label is being rendered, there is not a password_label block."
How does it know that it needs password_label block?

Good question :). Here's what the process looks like internally:

A) The form system starts to render the "label" for a "password" field. It asks: "which block should I use to render this"?

B) To determine that, it first looks for a block called "password_label". It always first looks for a block that is the "field type" an underscore and then "label" (because it's rendering a label). For example, when the form system needs to render the label for a "textarea" it also looks for textarea_label first. By default, pretty much no field types have a custom "TYPE_label" block.

C) Because there is no "password_label" block, the form system automatically then looks for "form_label". That's just how the system works - it always falls back to using "form".

This is a slight over-simplification, but the general idea is accurate: it looks for password_label first and if it is not found, falls back to form_label. The reason you don't see this logic inside the form_widget_simple or password_widget blocks is that the logic lives one level higher: this logic lives at the layer that is responsible for rendering the blocks. It's a crazy function, but the logic that renders the blocks and has all this "fallback logic" is this one: https://github.com/symfony/symfony/blob/b1bee601197e2a07ef3fd3274e46231b26e28824/src/Symfony/Component/Form/FormRenderer.php#L130

Cheers!

thanks