Chapters

41 Chapters | 4:45:40 |

01

Form Type Class

9:11
02

Handling the Form Submit

8:44
03

Success (Flash) Messages

6:50
04

Bind Your Form to a Class

7:32
05

Field Types & Options

4:45
06

DateTimeType & Data "Transforming"

6:25
07

EntityType: Drop-downs from the Database

7:33
08

EntityType: Custom Query

5:27
09

HTML5 & "Sanity" Validation

6:19
10

Validation Constraints with @Assert

5:13
11

Form Rendering Functions: form_*

5:22
12

Form Rendering Variables

5:16
13

The Edit Form

7:18
14

Registration Form

7:15
15

Adding Extra "Unmapped" Fields

6:58
16

UniqueEntity & Validation Directly on Form Fields

6:40
17

Agree to Terms Database Field

6:03
18

Agree to Terms Checkbox Field

5:35
19

All about Form Themes

8:01
20

Form Theme Block Naming & Creating our Theme!

6:22
21

Form Theming & Variables

8:42
22

Form Theming a Single Field

4:07
23

Custom Field Type

6:24
24

Data Transformer

9:09
25

Custom Field: configureOptions() & Allowing Empty Input

4:42
26

Leveraging Custom Field Options

5:35
27

Autocomplete JavaScript

8:19
28

Autocomplete Endpoint & Serialization Group

5:26
29

Hooking up the AJAX Autocomplete

8:20
30

The buildView() Method

7:09
31

Form Type Extension

10:09
32

Tweak your Form based on the Underlying Data

8:35
33

Form Model Classes (DTOs)

9:59
34

Custom Validator

8:59
35

Setup: For Dependent Select Fields

6:41
36

Form Events & Dynamic ChoiceType choices

6:01
37

Dynamic Form Events

7:40
38

PRE_SET_DATA: Data-based Dynamic Fields

4:25
39

JS to Auto-Update the Select Options

10:18
40

Clear that Location Name Data

5:09
41

A bit of Security Cleanup

7:02

This tutorial has a new version, check it out!

> Symfony 4 > Symfony 4 Forms: Build, Render & Conquer!

Buy Access to Course

20.

Form Theme Block Naming & Creating our Theme!

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

9 Comments

Sort By

Login or Register to join the conversation

Milica-S 5 years ago edited

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">https://symfony.com/doc/current/form/form_customization.html#form-form-view-variables</a> 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.

|

sadikoff Milica-S 5 years ago

@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!

|

elkuku sadikoff 5 years ago

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.

1 |

weaverryan SFCASTS elkuku 5 years ago edited

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

|

elkuku weaverryan 5 years ago

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

|

weaverryan SFCASTS elkuku 5 years ago

I love documentation :D :D :D

|

Lijana Z. 6 years ago edited

"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 -%}`

|

weaverryan SFCASTS Lijana Z. 6 years ago edited

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!

|

Lijana Z. weaverryan 6 years ago

thanks

|

Symfony 4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.10.2
        "doctrine/doctrine-bundle": "^1.6.10", // 1.10.2
        "doctrine/doctrine-migrations-bundle": "^1.3|^2.0", // v2.0.0
        "doctrine/orm": "^2.5.11", // v2.7.2
        "knplabs/knp-markdown-bundle": "^1.7", // 1.7.0
        "knplabs/knp-paginator-bundle": "^2.7", // v2.8.0
        "knplabs/knp-time-bundle": "^1.8", // 1.8.0
        "nexylan/slack-bundle": "^2.0,<2.2.0", // v2.0.0
        "php-http/guzzle6-adapter": "^1.1", // v1.1.1
        "phpdocumentor/reflection-docblock": "^3.0|^4.0", // 4.3.0
        "sensio/framework-extra-bundle": "^5.1", // v5.2.1
        "stof/doctrine-extensions-bundle": "^1.3", // v1.3.0
        "symfony/asset": "^4.0", // v4.1.6
        "symfony/cache": "^3.3|^4.0", // v4.1.6
        "symfony/console": "^4.0", // v4.1.6
        "symfony/flex": "^1.0", // v1.21.6
        "symfony/form": "^4.0", // v4.1.6
        "symfony/framework-bundle": "^4.0", // v4.1.6
        "symfony/property-access": "^3.3|^4.0", // v4.1.6
        "symfony/property-info": "^3.3|^4.0", // v4.1.6
        "symfony/security-bundle": "^4.0", // v4.1.6
        "symfony/serializer": "^3.3|^4.0", // v4.1.6
        "symfony/twig-bundle": "^4.0", // v4.1.6
        "symfony/validator": "^4.0", // v4.1.6
        "symfony/web-server-bundle": "^4.0", // v4.1.6
        "symfony/yaml": "^4.0", // v4.1.6
        "twig/extensions": "^1.5" // v1.5.2
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.0", // 3.0.2
        "easycorp/easy-log-handler": "^1.0.2", // v1.0.7
        "fzaninotto/faker": "^1.7", // v1.8.0
        "symfony/debug-bundle": "^3.3|^4.0", // v4.1.6
        "symfony/dotenv": "^4.0", // v4.1.6
        "symfony/maker-bundle": "^1.0", // v1.8.0
        "symfony/monolog-bundle": "^3.0", // v3.3.0
        "symfony/phpunit-bridge": "^3.3|^4.0", // v4.1.6
        "symfony/stopwatch": "^3.3|^4.0", // v4.1.6
        "symfony/var-dumper": "^3.3|^4.0", // v4.1.6
        "symfony/web-profiler-bundle": "^3.3|^4.0" // v4.1.6
    }
}

Previous Chapter

Next Chapter