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

18.

Using More Fields: email and repeated

|

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

5 Comments

Sort By

Login or Register to join the conversation

Shairyar Baig 8 years ago

Hi Ryan,

I am seeing "Updated 4 days ago" next to the tutorial heading, just out of curiosity how can i know what was updated?

Regards,
Baig

1 |

weaverryan SFCASTS Shairyar Baig 8 years ago

We're working on that - the "Updated" feature is not useful yet! In this case, it was a very minor tweak of some non-important screencast metadata. That's something we're planning on making *much* more useful soon - I also want to see exactly *what* has been updated!

1 |

Shairyar Baig 8 years ago

Hi Ryan,

I am hoping that you can push me in right direction.

I am working on a product where on an form fields are hard coded in a formtype class just like any form on a website but now i need to allow user to create more fields using an admin panel. The admin panel is all taken care of but i am stuck at how to allow them to create more fields and make sure they appear on front end with the form.

Cant seem to find any bundle either that does this.

Baig

|

weaverryan SFCASTS Shairyar Baig 8 years ago edited

Hey :)

Hmm, so this is not a problem I've had to solve personally - but it is a problem that others have, so it's good that you searched first for a bundle / existing solution. But, here's one potential direction:

1) Somehow, your users create "new" fields in the admin panel. I'm assuming that this "field creation" is a different screen than where people actually fill out the forms (it's like a schema-creation tool, in a sense). Somehow, you save these to the database - with information about the field types, etc

2) Create a new form class - e.g. DynamicFieldsType. Allow this type (in configureOptions) to have an option passed in - something like "fields", which would be an array of information about the fields that should be added. You'll be able to reference this "fields" option in buildForm(). You'll send this information in via the controller:


$form = $this->createForm(DynamicFieldsType::class, null, ['fields' => $fieldsInfo]);

3) In buildForm, use this "fields" option to completely, dynamically build your form. If you need validation, you'll need to add it via the "constraints" option for each field (since there is no entity behind this).

4) Finally, you can use this form directly if you want (like I've shown above). OR, if these fields are part of a bigger form, you'll need to embed this form in your main form (e.g. MainAdminType). In that case, you'll also need to pass a fields option to the main type so that you can pass this option into the child type (DynamicFieldsType). Or, you could also inject the EntityManager into DyanmicFieldsType and register it as a service.

I hope that somewhat gives you some ideas - at least from someone who has not actually had to solve this before :). There are probably even "cooler" solutions involving form events... but I don't see the point: just query the DB for the fields you need and dynamically build the form.

Cheers!

|

Shairyar Baig weaverryan 8 years ago

Thanks Ryan

|

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