Chapters

29 Chapters | 1:34:37 |

01

Introduction

1:00
02

ManyToOne Doctrine Relationships

4:40
03

Sharing Data between Fixture Classes

1:49
04

Restricting Edit Access to Owners

1:53
05

Using a shortcut Base Controller Class

2:30
06

Using PHPDoc for Auto-Completion

1:26
07

OneToMany: The Inverse Side of a Relationship

5:37
08

Doctrine Extensions: Sluggable and Timestampable

4:30
09

Using the slug in the Event URL

2:04
10

Adding createdAt and updatedAt Timestampable Fields

1:41
11

Creating a Custom orderBy Query

2:11
12

ManyToMany Relationship

2:37
13

Using the ManyToMany so Users can Attend an Event

4:53
14

More with ManyToMany: Avoiding Duplicates

2:51
15

JSON up in your Response

2:50
16

Come on, Set the Content-Type Header!

3:19
17

Adding the AJAX Touch: JavaScript

2:16
18

Customizing Error Pages and How Errors are Handled

6:01
19

Render another Controller in Twig

4:28
20

Creating a Pretty CSV Download

4:19
21

Your Very First Service

4:42
22

Symfony Overlord: The Service Container

4:58
23

Configuration Loading and Type-Hinting

2:01
24

Dependency Inject All the Things

3:14
25

Twig Extensions and Dependency Injection Tags

4:33
26

Doctrine is in your Lifecycle (with Callbacks)

2:08
27

Doctrine Event Listeners

5:59
28

Doctrine Listeners on Update

2:48
29

Keep Going!

1:19

This tutorial has a new version, check it out!

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

Buy Access to Course

08.

Doctrine Extensions: Sluggable and Timestampable

|

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

9 Comments

Sort By

Login or Register to join the conversation

Dimitry K 8 years ago

Ryan thank you again for amazing video. Just wanted to add a "pro-tip". In the video you take shortcut and recreate all the schema when adding `slug`. In real-life scenarios most of the time slug will have to be added to already existing database and thus dropping and recreating schema wouldn't be an option. There's few good examples and proper explanation of how to add slug to existing database in this thread http://stackoverflow.com/qu...

|

weaverryan SFCASTS Dimitry K 8 years ago edited

Yo Dimitry K!

Good pro tip indeed! Life is easy with migrations if you haven't deployed yet... not so easy once you *have* deployed.

For data migrations like this that can't be easily accomplished by writing some SQL, we here at KnpU typically write custom, single-use console commands. That's a nice way to get access to Symfony's normal tools (like the EntityManager). We also always make sure to write them in a way where we can restart them if something explodes (because often with data migrations, you are handling a LOT of data, and it's always possible something will go wrong). For example, in this case, we would only try to set the slug on records that don't already have a slug (so that if we restart the command, it doesn't start way back at the beginning).

Glad you added the comment - this data migration stuff is something we handle all the time in the real world!

Cheers!

1 |

Shaun T. 8 years ago

Hey thanks for the great content!

I just installed added the Blameable to my entities and I am finding that it doesnt work when I try to load data using fixtures, any idea why this is?

|

Victor SFCASTS Shaun T. 8 years ago

Hey Shaun,

Did you follow this instruction: https://github.com/Atlantic... ? Also, StofDoctrineExtensionsBundle do not enable any behavior by default, you need to enable it manually in its bundle configuration in order to use it. And yeah, don't forget to clear the cache just in case ;)

Cheers!

|

Shaun T. Victor 8 years ago

Thanks for your reply Victor, yes I have enabled the behaviour in config/packages/stof_doctrine_extensions.yaml

stof_doctrine_extensions:
default_locale: en_US
orm:
default:
blameable: true
timestampable: true

I also cleared the cache however I still get the same error:

SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'created_by' cannot be null

I am wondering if there is an active 'user' for blameable to set when a data fixture file is being run?

|

Victor SFCASTS Shaun T. 8 years ago

Hey Shaun,

I think I know the problem: this behavior sets up created_by to the *current* user, but since you're in console - there's no current user. For your fixtures, you need to manually set up the proper user. Maybe there's a smarter solution, but I don't know if it exists :)

Cheers!

|

Victor SFCASTS 8 years ago

Hi, Ryan!

What about KnpLabs/DoctrineBehaviors bundle? It seems also a very popular bundle that looks like StofDoctrineExtensionsBundle with similar features. Do you use it? What bundle do you like more to use in your projects?

Thanks!

|

weaverryan SFCASTS Victor 8 years ago

Hey!

Actually, I don't use this - and I somehow haven't even really seen it yet (unfortunately, there is an ocean between me and the main Knp office, so I can miss things)! But I really like it - in many cases, the functionality that's similar to StofDoctrineExtensionsBundle looks easier to implement - for example Sluggable. I'd like to try this and tell more people about it.

Thanks!

|

Victor SFCASTS weaverryan 8 years ago

Yes, it's a bit simple for me too. And it has less magic than in StofDoctrineExtensionsBundle :)

|

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
        "stof/doctrine-extensions-bundle": "~1.1.0" // v1.1.0
    }
}

Previous Chapter

Next Chapter