Rich's stuff

Came across this one today whilst integrating some new code into my current Symfony2 project. The project has 2 custom Twig extensions – one with some filters in, one with some custom methods. When creating the latter, I’d copied the class from the former and tweaked to suit. In doing so, I’d left these lines in:

    /**
     * Name of this extension
     *
     * @return string
     */
    public function getName()
    {
        return "myfirstextension";
    }

The Twig documentation states that all extensions should be named uniquely, unless you need to replace any existing extensions, in which case you should name them the same. See here for a better explanation :-) Great for extensibility and adjusting extensions that maybe you don’t have control over. Not so good when both extensions do something different and you don’t quite understand why it’s not working….

Anyway, quick question in the #symfony IRC channel and Stof came to the rescue. Give that man a medal :-) and name your extensions uniquely if you don’t want them to overwrite others!

Came across this one today whilst integrating some new code into my current Symfony2 project. The project has 2 custom Twig extensions – one with some filters in, one with...

Quick post this, as I know I’ll forget/lose this code otherwise… Sometimes you need the ability to force a logout of a user. The example I’ll use here is a user requesting their account be deactivated – you assume that upon confirmation of the deactivation the user’s model is marked as such, and the user is subsequently logged out and shown a confirmation page:

// Update your model here. Example:
$user = clone $this->get("security.context")->getToken()->getUser();
$user->setEnabled(false);
$user->save();
 
// Log the user out
$this->get("request")->getSession()->invalidate();
$this->get("security.context")->setToken(null);
 
// Flash var to enable the user to see the deactivation success page
$this->get("session")->setFlash('deactivate_account.success', true);
 
// and redirect to success page
return new RedirectResponse($this->get("router")->generate("deactivate_account_success"));

Your deactivation page should allow viewing without requiring authentication (anonymous users can view it). The above code should be self-explanatory – invalidate the current session, and set the security token to null (rather than the previously-authenticated token). The flash variable I set so that viewing of the success page is one-shot rather than being permanently viewable. Just my preference :-)

Quick post this, as I know I’ll forget/lose this code otherwise… Sometimes you need the ability to force a logout of a user. The example I’ll use here is a...