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

15.

Adding Extra "Unmapped" Fields

|

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

16 Comments

Sort By

Login or Register to join the conversation

Remus M. 7 years ago edited

for me, unless I make plainPassword RepeatedType, it doesn't work.

for those who wonder how,
`->add('plainPassword', RepeatedType::class, array(

            'type' => PasswordType::class,
            'first_options'  => array('label' => 'Password'),
            'second_options' => array('label' => 'Repeat Password'),
        ))`

1 |

MolloKhan SFCASTS Remus M. 7 years ago edited

Hey Remus M.

What's not working for you, the mapped => false option?

|

Remus M. MolloKhan 7 years ago

data.plainPassword
This value should not be blank.

Caused by

ConstraintViolation

LE: sorry about that, i still had plainPassword field from a previous tutorial :)

|

KableCH 7 years ago

For those who may be as confused as I was about this, you can use RepeatedType to render two password fields. Symfony will check for you that both values match. Read more about it on the docs https://symfony.com/doc/cur...
Hope this helps :)

1 |

Victor SFCASTS KableCH 7 years ago

Hey Tobias,

Thank you for sharing it with others! Yeah, if you want to double sure users didn't misprint his password - you can use RepeatedType along with PasswordType.

Cheers!

|

Kevin 4 years ago

Hi,

I was taking a look at the 5.4 docs after watching this video and noticed `PasswordAuthenticatedUserInterface` being implemented to User on one of the examples. Would this be the equivalent of doing the plainPassword technique shown in this vid on newer versions of Symfony?

|

MolloKhan SFCASTS Kevin 4 years ago edited

Hey Kevin

Yes, the main idea here is to avoid adding a property on the User object that will hold the value of plainPassword. So, in this video Ryan teaches how you can add fields to a form that are not mapped to an entity

Cheers!

|

Abdul mannan 5 years ago

why don't we just handle the encoding within the setPassword method in the entity ? Doesn't it make more sense to have it one place rather having encoding code duplicated in multiple places?

|

Victor SFCASTS Abdul mannan 5 years ago

Hey Abdul,

The problem is that PasswordEncoder - that's a *service*, and you don't have access to services from your entities because entities are just simple data objects. That's why we have to pass the entity through some code that will generate the correct password using that service and set it on the entity.

I hope this is clearer for you now.

Cheers!

|

Benoit L. 6 years ago

Hi, how would I transform an unmapped Datetime field into a DateTime object from an array? thank you.

|

MolloKhan SFCASTS Benoit L. 6 years ago edited

Hey Benoit L.

Have you tried setting up the DataType of the unmapped field to a Symfony "DateTimeType"? https://symfony.com/doc/cur...

Cheers!

|

Martin C. 7 years ago

It's great the unmmaped field but I have a problem on my side. The password on the user entity is required. So when I want to register a user I don't pass the isValid method because the password is not set (only the plaintext password), and we're supposed to set the password after validation of the form.

So should I make the password nullable in the database ?

|

ionik Martin C. 7 years ago

Hi,

If you use symfony 4.3
Use validation groups to do validation because of this new feature : https://symfony.com/blog/ne...
https://symfony.com/doc/cur...

1 |

weaverryan SFCASTS ionik 7 years ago edited

Hey ionik!

you're right - this issue is related. We've temporarily disabled this new automatic validation feature on new Symfony 4.3 projects - you can still enable it in validator.yaml, but it's no longer enabled by default: https://github.com/symfony/...

If you started a Symfony 4.3 project during the first few weeks of June, you will have this setting enabled. If it's causing issues, you can disable the "auto_mapping" key in validator.yaml. We're working to add a few more features to make it a bit more flexible before auto-enabling it in the future :).

Cheers!

|

ionik weaverryan 7 years ago

Thanks for your reply of explanation ;)

|

Victor SFCASTS Martin C. 7 years ago

Hey Martin,

You need to add validation constraints to the plainPassword instead of hashed password, because you work with plainPassword in the form. And then you will not need to make the password field nullable in the DB, you still can keep it required, but then it's your job to properly set the password field when user sent you a plainPassword and the form is valid.

Cheers!

1 |

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