Registration Form

Hey Vlad,

It's called Live Templates in PhpStorm and you can create your own templates! Here's a screencast about it:
https://knpuniversity.com/s...

Cheers!

That's terrific, Victor! I haven't gotten to that tutorial yet, but I certainly will.
73,

Hey Aditya Kothadiya!

Hmm, so, we do 2 things:

1) We add some code to getRoles() to guarantee that the array returned always contains ROLE_USER. But, that's not your problem - that has nothing to do with how the roles property is stored (source: https://knpuniversity.com/screencast/symfony-security/dynamic-roles).

2) Do you have private $roles = array();? The fact that it is trying to insert as NULL tells me that this property may not have been initialized to an empty array. Also, are you using the json_array type?

Let me know! I'm sure it's something small :).

Cheers!

Yes, I didn't not initialize $roles as an empty array. I had below -

/**
* @ORM\Column(type="json_array")
*/
private $roles;

I initialized it to an empty array and now the problem is solved! Thanks a ton for a prompt reply.

Hey Marcin,

Thank you for your interest in SymfonyCasts tutorials! Yes, it's on our plan to release a new Security tutorial for Symfony 5 track. Not sure will it be the next Symfony5-related course or after one more course, but we will definitely release this some day. We also will try to cover reset password feature there, actually we have a new bundle that helps with resetting passwords, you can check it our here: https://github.com/SymfonyC... . Unfortunately, I don't have estimations for you yet when the new Symfony 5 security course might be released, sorry.

Btw, you're looking at Symfony3 course about security, we also have an updated one for Symfony 4 that is the latest available course about Symfony security. You can find it here: https://symfonycasts.com/sc... . Feel free to follow it on Symfony 5 project and if you will have any problems - aks them in comments below the video, we will definitely try to help you solving them!

Cheers!

Hey Dennis E.!

Huh, interesting! From everything I'm looking at, this should work. Actually, the important part is the label => false inside first_options and second_options - the label => false on the top level does nothing (it's fine to keep it - just pointing out where things do and don't matter). Question: if you set 'label' => 'Foo', does the label show up as Foo?

Also, is it any different if you render the fields individually?

{{ form_row(form.plainPassword.first) }}
{{ form_row(form.plainPassword.second) }}

And finally, if you click into the form profiler, and find the plainPassword.first and plainPassword.second fields, under "View Variables", what is the value of the "label" variable for each?

Cheers!

Hi Ryan,

Silly me. In my twig template file I had the following:

            {{ form_row(form.plainPassword.first, {
                'label': 'Password'
            }) }}
            {{ form_row(form.plainPassword.second, {
                'label': 'Repeat password'
            }) }}

That's why the labels were being set. Sorry!

Ah! Nice catch! It's those subtle things that are the toughest to see! :)

Hey Jay,

Yea, it's a Symfony Plugin - you should install it first and most probably restart your PhpStorm after installation.

Oh, and btw, if you already have this template - you won't see this "Create template" option - it works only for non-existent templates.

Cheers!

Thanks Victor,

I had installed this, but looking into it this morning it looks like it was not enabled. Crazy!

Ah, good catch! I forgot to notice about it :)

Yea, this plugin isn't enabled by default.

\src\AppBundle\Form\UserRegistrationForm:

<?php

namespace AppBundle\Form;

use AppBundle\Entity\User;

use Symfony\Component\Form\AbstractType;

use Symfony\Component\Form\Extension\Core\Type\EmailType;

use Symfony\Component\Form\Extension\Core\Type\PasswordType;

use Symfony\Component\Form\Extension\Core\Type\RepeatedType;

use Symfony\Component\Form\FormBuilderInterface;

use Symfony\Component\OptionsResolver\OptionsResolver;

class UserRegistrationForm extends AbstractType

{

    public function buildForm(FormBuilderInterface $builder, array $options)

    {

        $builder

            ->add('firstName')

            ->add('lastName')

            ->add('email', EmailType::class)

            ->add('plainPassword', RepeatedType::class, [

                'type' => PasswordType::class

            ])

        ;

    }

    public function configureOptions(OptionsResolver $resolver)

    {

        $resolver->setDefaults([

            'data_class' => User::class,

            'validation_groups' => ['Default', 'Registration']

        ]);

    }

    public function getBlockPrefix()

    {

        return 'UserRegistrationForm';

    }

\src\AppBundle\Form\OrganisationCreationForm.php:

<?php

namespace AppBundle\Form;

use AppBundle\Entity\Organisation;

use AppBundle\Entity\User;

use Symfony\Bridge\Doctrine\Form\Type\EntityType;

use Symfony\Component\Form\AbstractType;

use Symfony\Component\Form\FormBuilderInterface;

use Symfony\Component\OptionsResolver\OptionsResolver;

class OrganisationCreationForm extends AbstractType

{

    public function buildForm(FormBuilderInterface $builder, array $options)

    {

        $builder

            ->add('name')

            ->add('address')

            ->add('website')

            ->add('phoneNumber')

            ->add('admin', EntityType::class, [

                'class' => 'AppBundle\Entity\User',

            ])

        ;

    }

    public function configureOptions(OptionsResolver $resolver)

    {

        $resolver->setDefaults([

           'data_class' => Organisation::class,

        ]);

    }

    public function getBlockPrefix()

    {

        return 'OrganisationCreationForm';

    }

Hey Javier!

Do you want to add many users at a time or only one ?
If only one is the case, then you can embed User's form into Organization form, like this:

// \src\AppBundle\Form\OrganisationCreationForm.php:
public function buildForm(FormBuilderInterface $builder, array $options)
{
    // other fields...

    $builder->add('admin', UserRegistrationForm::class);
}

You can read more about embeding forms here:
http://symfony.com/doc/current/form/embedded.html

Have a nice day!

Hey Vlad,

Yes, you're totally right here!

Cheers!

Hey Mike,

1) Inside controllers, you can use shortcut "$this->getUser()" - that's a better way to get currently logged in user. And one line of code is not a code duplication ;)

2) That's actually up to you - do as you like most ;) There's no a strong reason doing so, except when you want to group those things separately.

Cheers!

Hey Simon,

You can use different validation groups for it, check out this screencast: https://knpuniversity.com/s... . This should fix your problem. Or you can add NotBlank validation constraint to the form field not to the property of your entity. But validation groups is the right way here, I think.

Cheers!

Thanks victor , Brilliant. I hadn't got that far in the series.

It's not obvious that it exists before someone tells you, once you know about it, it's another amazing feature of Symfony!

I can't believe I have stayed away from Symfony for so many years, I was scared that it would eat me alive, but in fact you get so much power for very little effort. I think the amazing teaching skills of victor are a lot to do with how quickly I have fallen in love with the framework.

You're welcome!

Haha, I agree with you :) It's not so scary when you have a good resource for learning. Btw, Symfony has pretty good docs and most of them is also written by Ryan.

I just wonder what framework did you use before Symfony?

Cheers!

I still use Codeigniter for the primary project i work on. I am starting to look at how i might rewrite that in Symfony. The problem is the 150 existing tables i have. it would take some time to re write them in Doctrine.

Hey Dan,

Is it? Let's figure it out... You'll see this "Cannot check if an unsubmitted form is valid..." error only when the form is not submitted, see this inverted logic in if statement inside isValid(): https://github.com/symfony/... . In other words, if you call isValid() on the form which was not sent, i.e. when "isSubmitted = false" - you'll get that exception which means you should call isSubmitted() first before isValid() to avoid throwing that exception, right? Because we totally do not want to see that exception. So note is valid as for me :)

Cheers!

Thanks for your reply Victor. I must be completely misunderstanding the note in this tutorial. It says "In the forms tutorial, we also added $form->isSubmitted() in the if statement, but you technically don't need that: isValid() checks that internally."

The note tells us to use`
if ($form->isValid())`
instead of`
if ($form->isSubmitted() && $form->isValid())`
.

As you say, isValid() does check internally if the form is submitted, but if it's not, it throws an exception, which is not what we want here.

Exactly that Patrick

In older Symfony's version you could call "$form->isValid()" without calling "isSubmitted()" and nothing would break, but in Symfony4 (probably since version 3.4?) it throws an exception. So, just don't forget to call both methods whenever you are working with a forms :)

Thanks for you reply, Diego. Ah, okay. Yes, that's exactly what I was pointing out - that it may be useful to note that the tip given in this tutorial doesn't apply to SF4.

Hey Hank

Look's like something is calling "$form->handleRequest($request);" twice, I would need to check your controller's action code so I can help you debugging

Cheers!

Thanks Diego you were right!

Excellent, let's keep learning! :)

Sorry, my fault, there was a typo in my buildForm method. :(

Hey Roberto,

I'm glad you had found the bug quicker than I replied to you :)

Cheers!

Hey Yang!

Ah, thanks! Always happy to see you going through things and asking good questions :).

1) You're right! Actually, the href and template are correct, but the language is wrong. It should say "Register" (this is actually what we do in the video). I've just updated the code block to show this. Thanks for pointing that out! (ref https://github.com/knpunive...

2) Glad you already found the solution about the repeated fields - good digging! About the labels, labels - whether you're dealing with a normal field or a repeated field - can *always* be modified in either the form class or the template. Which is better? Probably the template, because I consider this - along with other things like setting a "class" on your element - to be *presentation* logic. Also, on larger teams that have frontend devs, you will want to keep this stuff in your template so that frontend devs can find it without searching around for crazy PHP files :).

Cheers!

Regarding 2)

Do I see it right that the 'invalid_message' parameter *can't* be set in the twig template and *only* in the form? That would be presentation logic as well if I see it correctly.

Hey Mike P.

You are correct, that would be considered presentation logic aswell, but, it can be changed in a twig's template. You can override almost every value the form has, you can try something like this:

{{ form_row(form.password.first, {
    'invalid_message': 'password custom error message'
}) }}

Only check that the keys passed to form_row matches to the ones from the Form object.

Cheers!

Thanks for that fast reply!
I can tell you, this doesn't work:

{{ form_row(form.plainPassword.first, {
                        'label': 'Password',
                        'invalid_message' : 'The password fields must match.'
                    }) }}
                    {{ form_row(form.plainPassword.second, {
                        'label': 'Repeat Password',
                        'invalid_message' : 'The password fields must matchs.'                    }) }}```


Label works, but error message is " This value is not valid.". If I type invalid_message into the ->add() method it works perfectly. Maybe its a quirk due to using the RepeatedClass?

->add('plainPassword', RepeatedType::class, [

            'type' => PasswordType::class,

        ]);

Hey Mike P.

You are right, that doesn't work, sorry for miss leading you. Error messages comes from Constraints, like:

// User.php
/**
* @Assert\NotBlank(message="This field should not be blank")
*/
private $plainPassword;

You can change them right there or using a translation file