What is Symfony?
Get started
Documentation
Community
Services
News

Latest News

Symfony 2.0.14 released

by Fabien Potencier – May 18, 2012

What happened last week in Symfony?

This week, Symfony 2.1 updated its minimum required PHP version to 5.3.3, which contains a lot of bug fixes. Meanwhile, Dependency Injection and Session were the most active components in the repository.

Upcoming Events

The Symfony Community organizes events all over the world on a regular basis. Here are the next ones.

France, Paris — Symfony Live Paris 2012

from June 06, 2012 to June 09, 2012

Spain, Castellón — deSymfony 2012

from June 15, 2012 to June 16, 2012

Brazil, Belo Horizonte — sfcon 2012

on June 23, 2012, from 08:00 to 18:00

United Kingdom, London — Symfony2 Lightning Talks - London

on June 28, 2012, from 19:00 to 22:00
About

Blog

Symfony 2.0.9 released
by Fabien Potencier – January 06, 2012 – 15 comments

Symfony 2.0.9 has been released earlier than expected to fix some annoying problems in 2.0.8:

it comes with Twig 1.5.1, which fixes a regression that made the form_theme tag fail;
it comes with a fix for the Filesystem class;
the composer.json file for 2.0.8 had the wrong version in it.

The CHANGELOG has all the details about the changes done in this release and you can also 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.9 by getting the new deps and deps.lock files.

Then, run the vendors script:

$ ./bin/vendors install

And don't forget to clear your cache:

$ php ./app/console cache:clear

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.

Add a Comment

You must be connected to post a comment.

Comments

#1 Peter Kokot said on the 2012/01/06 at 10:19

Bravo!
#2 Oleg Zinchenko said on the 2012/01/06 at 11:04

Yeah, Twig 1.5.1 is great.
#3 Gabor Toth said on the 2012/01/06 at 12:22

If you have issues with SensioGeneratorBundle, just version=origin/2.0 to your deps file.
#4 enrico stano said on the 2012/01/06 at 13:16

after the "dev_old" cache folder problem (solved deleting such folder), I have this error

RuntimeException: Failed to write cache file "/srv/http/Symfony/app/cache/dev/classes.php".

on app_dev.php and a 404 on app.php

could anyone help me, please? thank you.
#5 Georgi Katsarov said on the 2012/01/06 at 14:03

enrico stano, your cache folder doesn't have write permissions.
#6 Jan Eichhorn said on the 2012/01/06 at 14:43

What about using Version 1.1.0 of JMS Security Extra Bundle?
The DEPS points to 1.0.x

[JMSSecurityExtraBundle]
git=http://github.com/schmittjoh/JMSSecurityExtraBundle.git
target=/bundles/JMS/SecurityExtraBundle
version=origin/1.0.x
#7 enrico stano said on the 2012/01/06 at 15:36

Georgi Katsarov, the cache folder permissions are ok. Any other idea?
#8 Sebastian Busch said on the 2012/01/06 at 15:58

@Fabien if you run "./bin/vendors install" it is not necessary to clear the cache, as the bin/vendors script does this as the last step.
#9 Florin Patan said on the 2012/01/07 at 20:55

Hi,

I've just downloaded v2.0.9 to use it to upgrade from 2.0.8 and I've noticed that we now have the vendor/bundles/Doctrine/Bundle/DoctrineBundle folder as well.

I've tried using it as opposed to the old folder (which still exists in 2.0.9) but I'm receiving the following error message:

Fatal error: Call to undefined method Symfony\Bundle\SecurityBundle\DependencyInjection\SecurityExtension::addUserProviderFactory() in /var/www/demo/vendor/bundles/Doctrine/Bundle/DoctrineBundle/DoctrineBundle.php on line 39

Call Stack:
0.0040 637656 1. {main}() /var/www/demo/web/app_localhost.php:0
0.0447 2785072 2. Symfony\Component\HttpKernel\Kernel->handle() /var/www/demo/web/app_localhost.php:40
0.0447 2785232 3. Symfony\Component\HttpKernel\Kernel->boot() /var/www/demo/app/bootstrap.php.cache:544
0.0548 3068096 4. Symfony\Component\HttpKernel\Kernel->initializeContainer() /var/www/demo/app/bootstrap.php.cache:513
0.0561 3076504 5. Symfony\Component\HttpKernel\Kernel->buildContainer() /var/www/demo/app/bootstrap.php.cache:779
0.0818 3514456 6. Doctrine\Bundle\DoctrineBundle\DoctrineBundle->build() /var/www/demo/app/bootstrap.php.cache:848

I've reverted the changes in autoload.php and AppKernel.php to be the ones that are in 2.0.x branch but it would be good to know if that folder ended up there by simple mistake or there was some merge that shouldn't have been done in GIT.

Thank you all for the hard work you've done for this project.

Kind regards.
#10 Nicolás Moreira said on the 2012/01/09 at 00:25

Muy bueno!!, gracias SensioLabs. Saludos desde Uruguay.
#11 kyo zhou said on the 2012/01/09 at 02:20

hi, when I tried to upgrade to 2.09, I got there errors:
> Installing/Updating symfony
HEAD is now at 3e9d937 updated VERSION for 2.0.9
> Installing/Updating twig
fatal: Could not parse object '5bba14970604a26469af90b605d10c716b3af411'.
> Installing/Updating monolog
fatal: Could not parse object 'b704c49a3051536f67f2d39f13568f74615b9922'.
> Installing/Updating doctrine-common
fatal: Could not parse object 'b886898821288d305862ee9c567cc5b5cbb4c0dc'.
> Installing/Updating doctrine-dbal
fatal: Could not parse object 'ae358bd94ec09d7d3ad92ca7820e67825ad9e5f4'.
> Installing/Updating doctrine
fatal: Could not parse object 'da0e3439aba4c8bf5e8a6ee4ccee5ce2624be8d1'.
> Installing/Updating swiftmailer
fatal: Could not parse object '982b4c9498b7dd85e70f6d35e65d909c888e6345'.
> Installing/Updating assetic
fatal: Could not parse object 'f829ad23d23c87480151a21faad49fefe7c09e5d'.
> Installing/Updating twig-extensions
fatal: Could not parse object 'a05ab5ed18a51ae45f3dcc2d0c4ec9b3a6386987'.
> Installing/Updating metadata
fatal: Could not parse object '8717ad2a5689480765d9ffafe925cd8a2457e582'.
> Installing/Updating SensioFrameworkExtraBundle
fatal: Could not parse object '1c7e92f466d11f83130b0c1271f44d067a2c3b31'.
> Installing/Updating JMSSecurityExtraBundle
fatal: Could not parse object '541a4c242328dc04b99540c75346cc74a7c0cfb5'.
> Installing/Updating SensioDistributionBundle
fatal: Could not parse object '20b66a408084ad8752f98e50f10533f5245310bf'.
> Installing/Updating SensioGeneratorBundle
fatal: Could not parse object 'dd37fc4487bc09ac01bdcf89e0ff4ee4484b7fab'.
> Installing/Updating AsseticBundle
fatal: Could not parse object '41b5913b5086a0909af92adcb4a6005ee0051b16'.

How can I fix it?
#12 Mell Zamora said on the 2012/01/09 at 08:14

Yay! This is what I love about Symfony2 very active development.
#13 Michael O'Toole said on the 2012/01/12 at 10:45

For some reason we have been having real issues with the deps file. Not sure if there are others who have had same issues. Using the http:// git service for installing recently (intermittently admitted) causes RPC failures.

Simply changing the deps to the below fixed the issue.

[symfony]
git=git://github.com/symfony/symfony.git
version=v2.0.9

Using the git:// method is generally more reliable and actually faster from our experiences so far.
#14 Innokenty Sokolov said on the 2012/01/16 at 18:34

nice, twig updt )) thx.
#15 Calin Rada said on the 2012/01/17 at 09:35

Hey. Since i've installed 2.0.9 i have a problem - doctrine flush() is inserting 2 rows. Does anyone experienced this ? My test code:

$c = new Category();
$c->setName('Category');
$c->setDescription('Lorem ipsum dolor sit amet');
$c->setIsPublished(1);
$c->setPosition(1);

$em = $this->getDoctrine()->getEntityManager();
$em->persist($c);
$em->flush();