Chapters

36 Chapters | 1:50:44 |

01

Introduction

0:44
02

Security Fundamentals

3:47
03

Authorization with Access Control

2:08
04

Creating a Login Form (Part 1)

4:46
05

Creating a Login Form (Part 2)

3:57
06

Logging Out and Cleaning Up

5:03
07

Twig Security and IS_AUTHENTICATED_FULLY

2:41
08

Denying Access: AccessDeniedException

4:23
09

Entity Security

4:32
10

Saving Users

3:37
11

Adding Dynamic Roles to each User

4:56
12

Repository Security

4:20
13

Doctrine’s QueryBuilder

2:25
14

The UserProvider: Custom Logic to Load Security Users

3:15
15

User Serialization

2:16
16

Registration Form

3:11
17

Form Rendering

4:38
18

Using More Fields: email and repeated

2:31
19

Handling Form Submissions

4:22
20

Form: Default Data

2:10
21

Cleaning up with a plainPassword Field

1:34
22

Using an External Form Type Class

2:40
23

Registration Validation

3:36
24

Server-Side Validation

4:18
25

Adding a Flash Message

1:35
26

Automatically Authenticating after Registration

0:55
27

Functional Testing

5:04
28

Testing Forms

3:21
29

Controlling Data / Fixtures in a Test

3:23
30

More about Container, the “doctrine” Service and the Entity Manager

1:54
31

After-dinner Mint

3:35
32

Security: Creating Roles and Role Hierarchies

2:50
33

Switching Users / Impersonation

1:09
34

Whitelisting: Securing all Pages, except a few

2:15
35

Accessing the User

1:09
36

Remember Me Functionality

1:44

This tutorial has a new version, check it out!

> Symfony 2 > Starting in Symfony2: Course 2 (2.4+)

Buy Access to Course

20.

Form: Default Data

|

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

Login or register to check out the script

8 Comments

Sort By

Login or Register to join the conversation

MolloKhan SFCASTS 8 years ago

Hey Ryan,

I've a question about formtypes, I have a form builder for an entity with a relationship to other entity, when I create an Edit Action I found that doctrine is making 2 queries, in order to create the select option with the current entity selected
The first one to get the data of the related entity
and the second for the list of records on the Database (In order to show the list of options for that entity)

I'm wondering what can I do to reduce that to only 1 query

Thanks in advance

|

weaverryan SFCASTS MolloKhan 8 years ago

Yo Diego!

Hmm, I don't think that you can: the second query (for the options) is completely unaware of the underlying data in your form (the main entity). Plus, it definitely needs to make the independent query for a "new" action. Now, technically, you *can* avoid the second query if you *really* wanted to, but I think you're probably over-optimizing. You would:

A) In buildForm, get the main entity via $options['data'] (but check to see if this is your object - it will be either null or an unsaved object in "new" mode depending on your setup)
B) If $options['data'] is your persisted main entity, then add a choices key to your EntityType field that is an array of the related objects you want in your list (e.g. $genus->getNotes() to follow with the relationship we use in the new Symfony 3 course)).

At this point, you're basically manually creating the list of choices, instead of letting the EntityType do it for you. Your form should render, but it'll still have that extra query. Finally:

C) Add a join to the related entity when you query for the main entity, so that $genus->getNotes() doesn't require the extra query: https://knpuniversity.com/s...

That *technically* answers your question... but it's not worth it for me :).

Cheers!

|

MolloKhan SFCASTS weaverryan 8 years ago

Thank you very much for your answer

I'm totally agree, option A and B doesn't worth it, it is like reinventing the wheel, but worse.
Option C is not bad at all, if I add a method to the repository, but as you said, it's premature optimizing

Thanks again bro, have a good day.

|

Shairyar Baig 8 years ago edited

I have a dropdown (choice) field on a form that is linked with an Entity and I am able to save the data just fine in database, the problem I am having is when i open the form to edit the details, all form fields are pre-filled with correct information except the dropdown field that is linked with the Entity

This is what my form class looks like and the dropdown (choice) field i am referring to is called 'project'



<?php

namespace ProjectEverest\AdminBundle\Form;

use Symfony\Component\Form\AbstractType;
use Symfony\Component\Form\FormBuilderInterface;
use Symfony\Component\OptionsResolver\OptionsResolverInterface;

class OfferType extends AbstractType
{

    /**
     * @param FormBuilderInterface $builder
     * @param array $options
     */
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $builder
            ->add('interview', 'choice', array('choices' => array(
                'Yes'=> 'Yes',
                'No' => 'No'),
                'placeholder' => 'Interview Outcome'))
            ->add('place', 'choice', array('choices' => array(
                'Yes'=> 'Yes',
                'No' => 'No'),
                'placeholder' => 'Offer Outcome'))
            ->add('project', 'entity', array(
                'class' => 'AdminBundle:Programs',
                'property' => 'name',
                'placeholder' => 'Assigned Program'
            ));
    }
    
    /**
     * @param OptionsResolverInterface $resolver
     */
    public function setDefaultOptions(OptionsResolverInterface $resolver)
    {
        $resolver->setDefaults(array(
            'data_class' => 'ProjectEverest\AdminBundle\Entity\Offer'
        ));
    }

    /**
     * @return string
     */
    public function getName()
    {
        return 'projecteverest_adminbundle_offer';
    }
}

What can i do to make the dropdown show the value saved in database selected by default when editing information.

|

weaverryan SFCASTS Shairyar Baig 8 years ago

Hi Shairyar!

Hmm, I'm not sure about this. What version of Symfony? Some things in this area changed in 2.7.

But strictly speaking, if the `interview` property on the `Offer` object that you're passing into the form has a value of "Yes" or "No" exactly (i.e. you have this string stored in the database), then it should auto-select. But if you're storing something more like a 1/0 in the database, then this will *not* work - as the form can't figure out which option to show for 1/0.

Cheers!

|

Guest 8 years ago

This syntax

$form = $this->createFormBuilder(null, array(
'data_class' => 'Yoda\UserBundle\Entity\User',
)) isn't not working with the last version of symfony..

Go directly to the " Form Type Class Chapter.."

|

weaverryan SFCASTS Guest 8 years ago

Hey Marco!

Hmm, that should still work just fine. The first argument to createFormBuilder is the data, and passing null data is totally fine. The second argument is an array of options, and the data_class option tells the form we want a User object. You're totally right to point out that this can be done exactly the same with an external form class - but this should also work.

So if you're seeing issues, let me know what the error is!

Cheers!

|

Guest 8 years ago

thanks,
My error was thinking that

When we define a data_class like this..
$form = $this->createFormBuilder(null, array(
'data_class' => 'Yoda\UserBundle\Entity\User',
))->getForm();
we don't need to add the elements...

but we still need to define the elements with "->add(email... ) " .

Symfony could detect them automatically.. .

Thanks for ur time a your great tutos

|

Symfony 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.3.3",
        "symfony/symfony": "~2.4", // v2.4.2
        "doctrine/orm": "~2.2,>=2.2.3", // v2.4.2
        "doctrine/doctrine-bundle": "~1.2", // v1.2.0
        "twig/extensions": "~1.0", // v1.0.1
        "symfony/assetic-bundle": "~2.3", // v2.3.0
        "symfony/swiftmailer-bundle": "~2.3", // v2.3.5
        "symfony/monolog-bundle": "~2.4", // v2.5.0
        "sensio/distribution-bundle": "~2.3", // v2.3.4
        "sensio/framework-extra-bundle": "~3.0", // v3.0.0
        "sensio/generator-bundle": "~2.3", // v2.3.4
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.0
        "doctrine/doctrine-fixtures-bundle": "~2.2.0", // v2.2.0
        "ircmaxell/password-compat": "~1.0.3", // 1.0.3
        "phpunit/phpunit": "~4.1" // 4.1.0
    }
}

Previous Chapter

Next Chapter