Symfony 2.0.13 released

April 30, 2012 • Published by Fabien Potencier

Warning: Symfony 2.0 is no longer supported. Consider upgrading your applications to the most recent Symfony version.

Symfony 2.0.13 has just been released.

The CHANGELOG has all the details about the changes and you can even have a look at the full diff.

If you are starting a new project, you can get the Symfony Standard Edition distribution on the download page.

If you already have a project based on the Symfony Standard Edition 2.0.x, you can easily upgrade to 2.0.12 by getting the new deps and deps.lock files.

Then, run the vendors script (it also clears your cache):

$ ./bin/vendors install

Remember that the Symfony2 Components are also available as standalone libraries. You can get them via their dedicated read-only repositories on Github (https://github.com/symfony/Finder for instance), install them via PEAR (pear install symfony2/Finder), or even install them via Composer.

Published in #Releases

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

Comments

Andrej Hudec said on May 1, 2012 at 13:27

"...you can easily upgrade to 2.0.12..." It should be 2.0.13 :)

Yoann PETIT said on May 1, 2012 at 20:14

Hi Fabien!

paramConverter doesn't work anymore. In 2.0.12, it works fine and I don't see any changes about that in changelog.

My test with a new project:

use Acme\DemoBundle\Entity\Member;

class DemoController extends Controller { /** * @Route("/hello/{id}", name="_demo_hello") * @Template() */ public function helloAction(Member $member) { return array('name' => $member->name); }

Error:

Controller "Acme\DemoBundle\Controller\DemoController::helloAction()" requires that you provide a value for the "$member" argument (because there is no default value or because there is a non optional argument after this one).

Yoann PETIT said on May 1, 2012 at 21:47

Ok, you revert PR #117. A new version is intended or should we wait?

Evan Owens said on May 2, 2012 at 04:45

I was able to get paramConverter working again by removing SensioFrameworkExtraBundle from deps.lock

Yann Gallis said on May 2, 2012 at 14:13

Hi,

Since the 2.0.13 update, i can't upload files anymore. Do you have the same problem ?

public function getAbsolutePath() { return null === $this->path ? null : $this->getUploadRootDir().'/'.$this->path; }

public function getWebPath()
{
    return null === $this->path ? null : $this->getUploadDir().'/'.$this->path;
}

protected function getUploadRootDir()
{
    // the absolute directory path where uploaded documents should be saved
    return __DIR__.'/../Resources/public/'.$this->getUploadDir();
}

protected function getUploadDir()
{
    // get rid of the __DIR__ so it doesn't screw when displaying uploaded doc/image in the view.
    return 'images/dossiers';
}

public function upload()
{
    // the file property can be empty if the field is not required
    if (null === $this->image) {
        return;
    }

    // we use the original file name here but you should
    // sanitize it at least to avoid any security issues
    $dateFile = $this->getDate()->format('d-m-Y-G-i-s');

    // move takes the target directory and then the target filename to move to
    $this->image->move($this->getUploadRootDir(), $dateFile.'-'.$this->image->getClientOriginalName());

    // set the path property to the filename where you'ved saved the file
    $this->path = $dateFile.'-'.$this->image->getClientOriginalName();

    // clean up the file property as you won't need it anymore
    $this->image = null;
}

public function removeUpload()
{
    if ($file = $this->getAbsolutePath()) {
        unlink($file);
    }
}

public $image;

Alfonso said on May 2, 2012 at 19:39

Hi Yann. I have the same problem as you and I'm trying to solve. If I succeed I'll let you know.

Yoann PETIT said on May 2, 2012 at 20:14

Hi, I don't have this problem but I don't use getClientOriginalName().

Fralex Fralex said on May 2, 2012 at 21:54

On upgrade to 2.0.13 (from 2.0.12) i get this message

Installing/Updating doctrine-dbal D lib/vendor/Symfony/Component/Console D lib/vendor/doctrine-common "doctrine-dbal" has local modifications. Please revert or commit/push them before running this command again.

What can i do to upgrade to 2.0.13?

Loïc Vernet Certified said on May 3, 2012 at 13:12

@Fralex Fralex, you can manually delete theses files so they can be updated. It comes from modifications you have done in these files or perhaps line endings...

Yann Gallis said on May 3, 2012 at 16:37

#10

@Alfonso

Thanks. I'll let you know too ... Not find for now ...

Pierre Minnieur Certified said on May 4, 2012 at 13:26

#11

It's a very bad practice to post your upgrade problems and especially code in the comments. Use the symfony-users mailing list instead: http://groups.google.com/group/symfony2

Damien Biasotto said on May 9, 2012 at 09:43

#12

@Evan Owens:

Thanks a lot ! It works for me from a fresh install.

Alex Tabaksmann said on May 11, 2012 at 11:30

#13

Hi,

im getting following Exception after upgrade to 2.0.13. Any ideas how to fix?

[1/2] ErrorException: Catchable Fatal Error: Argument 2 passed to Twig_NodeVisitor_SafeAnalysis::setSafe() must be an array, null given, called in /home/atabak/vhosts/atabak-frontend2/vendor/twig/lib/Twig/NodeVisitor/SafeAnalysis.php on line 78 and defined in /home/atabak/vhosts/atabak-frontend2/vendor/twig/lib/Twig/NodeVisitor/SafeAnalysis.php line 21