Customize everything with Events
Course: FOSUserBundle FTW! Tutorial
Video not working?
It looks like your browser may not support the H264 codec. If you're using Linux, try a different browser or try installing thegstreamer0.10-ffmpeg
gstreamer0.10-plugins-good packages.
Thanks! This saves us from needing to use Flash or encode videos in multiple formats. And that let's us get back to making more videos :). But as always, please feel free to message us.
We can override templates. We can override translations. We can override forms. But there's more than that. For example, after we finish registration, we're redirected to this registration confirmation page. You know what? I'd rather do something else: I'd rather redirect to the homepage and skip this page entirely. How can we do that?
Well, let's do a little bit of digging. If you hover over the route name in the
web debug toolbar, you can see that this is page rendered by RegistrationController.
Back in my editor I'll press Shift+Shift and look for RegistrationController in
the bundle. Specifically, registerAction() is responsible for both rendering the
registration page and processing the form submit.
And check this out: after the form is valid, it redirects to the confirmation page.
Events to the Rescue!
So at first, it seems like we need to override the controller itself. But not so
fast! The controller - in fact every controller in FOSUserBundle is littered
with events: REGISTRATION_INITIALIZE, REGISTRATION_SUCCESS, REGISTRATION_COMPLETED
and REGISTRATION_FAILURE. Each of these represents a hook point where we can
add custom logic.
In this case, if you look closely, you can see that after it dispatches an event
called REGISTRATION_SUCCESS, below, it checks to see if the $event has a response
set on it. If it does not, it redirects to the confirmation page. But if it does,
it uses that response.
That's the key! If we can add a listener to REGISTRATION_SUCCESS, we can create
our own RedirectResponse and set that on the event so that this controller uses
it. Let's go!
Creating the Event Subscriber
Inside of AppBundle, create a new directory called EventListener. And in there,
a new PHP class: how about RedirectAfterRegistrationSubscriber. Make this implement
EventSubscriberInterface: the interface that all event subscribers must have.
I'll use our favorite Code->Generate menu, or Command+N on a Mac, go to
"Implement Methods" and select getSubscribedEvents.
| ... lines 1 - 2 | |
| namespace AppBundle\EventListener; | |
| ... lines 4 - 6 | |
| class RedirectAfterRegistrationSubscriber implements EventSubscriberInterface | |
| { | |
| public static function getSubscribedEvents() | |
| { | |
| } | |
| } |
We want to attach a listener to FOSUserEvents::REGISTRATION_SUCCESS, which, by
the way, is just a constant that equals some string event name.
In getSubscribedEvents(), add FOSUserEvents::REGISTRATION_SUCCESS assigned to
onRegistrationSuccess. This means that when the REGISTRATION_SUCCESS event
is fired, the onRegistrationSuccess method should be called. Create that above:
public function onRegistrationSuccess().
| ... lines 2 - 8 | |
| class RedirectAfterRegistrationSubscriber implements EventSubscriberInterface | |
| { | |
| public function onRegistrationSuccess(FormEvent $event) | |
| { | |
| } | |
| public static function getSubscribedEvents() | |
| { | |
| return [ | |
| FOSUserEvents::REGISTRATION_SUCCESS => 'onRegistrationSuccess' | |
| ]; | |
| } | |
| } |
Oh, and notice that when this event is dispatched, the bundle passes a FormEvent
object. That will be the first argument to our listener method: FormEvent $event.
That's what we need to set the response onto.
Investigating all the Events
Before we go any further, I'll hold command and click into the FOSUserEvents class...
cause it's awesome! It holds a list of every event dispatched by FOSUserBundle,
what its purpose is, and what event object you will receive. This is gold.
Creating the RedirectResponse
Back in onRegistrationSuccess, we need to create a RedirectResponse and set
it on the event. But to redirect to the homepage, we'll need the router. At the
top of the class, create public function __construct() with a RouterInterface $router
argument. Next, I'll hit Option+Enter, select "Initialize Fields" and
choose router.
| ... lines 2 - 10 | |
| class RedirectAfterRegistrationSubscriber implements EventSubscriberInterface | |
| { | |
| private $router; | |
| public function __construct(RouterInterface $router) | |
| { | |
| $this->router = $router; | |
| } | |
| ... lines 19 - 32 | |
| } |
That was just a shortcut to create the private $router property and set it in
the constructor: nothing fancy.
Now, in onRegistrationSuccess() we can say $url = $this->router->generate('homepage'),
and $response = new RedirectResponse($url). You may or may not be familiar with
RedirectResponse. In a controller, to redirect, you use $this->redirectToRoute().
In reality, that's just a shortcut for these two lines!
Finally, add $event->setResponse($response).
| ... lines 2 - 10 | |
| class RedirectAfterRegistrationSubscriber implements EventSubscriberInterface | |
| { | |
| ... lines 13 - 19 | |
| public function onRegistrationSuccess(FormEvent $event) | |
| { | |
| $url = $this->router->generate('homepage'); | |
| $response = new RedirectResponse($url); | |
| $event->setResponse($response); | |
| } | |
| ... lines 26 - 32 | |
| } |
Ok, this class is perfect! To tell Symfony about the event subscriber, head to
app/config/services.yml. At the bottom, add app.redirect_after_registration_subscriber,
set the class, and add autowire: true. By doing that, thanks to the RouterInterface
type-hint, Symfony will automatically know to pass us the router.
Finally, add a tag on the bottom: name: kernel.event_subscriber. And we are done!
| ... lines 1 - 5 | |
| services: | |
| ... lines 7 - 22 | |
| app.redirect_after_registration_subscriber: | |
| class: AppBundle\EventListener\RedirectAfterRegistrationSubscriber | |
| autowire: true | |
| tags: | |
| - { name: kernel.event_subscriber } |
Try it out! Go back to /register and signup as [email protected]. Fill out
the rest of the fields and submit!
Boom! Back to our homepage! You can customize just about anything with events. So don't override the controller. Instead, hook into an event!
Leave a comment!
-
2019-01-08 Diego Aguiar -
2019-01-08 Guervyl -
2018-11-13 Diego Aguiar
-
2018-11-13 Sami -
2017-12-25 Victor Bocharsky -
2017-12-22 Jelle Schouwstra -
2017-10-02 Diego Aguiar
-
2017-10-01 kaizoku -
2017-09-27 Diego Aguiar
-
2017-09-27 kaizoku
-
2017-08-21 weaverryan -
2017-08-17 mattxtlm -
2017-08-16 weaverryan
-
2017-08-16 weaverryan
-
2017-08-15 mattxtlm
-
2017-08-15 Jürgen Schatral
-
2017-08-15 weaverryan
-
2017-08-14 Jürgen Schatral
-
2017-08-10 Diego Aguiar
-
2017-08-10 Jürgen Schatral
-
2017-08-10 Diego Aguiar
-
2017-08-10 Jürgen Schatral
-
2017-08-09 Diego Aguiar
-
2017-08-09 Jürgen Schatral
-
2017-08-09 Jürgen Schatral
-
2017-08-08 Diego Aguiar
-
2017-08-08 Jürgen Schatral
-
2017-07-11 Victor Bocharsky
-
2017-07-10 kaizoku
-
2017-05-25 Michael
-
2017-05-24 Diego Aguiar
-
2017-05-24 Michael
-
2017-05-24 Diego Aguiar
-
2017-05-23 Michael
