Master Symfony2 fundamentals

Be trained by SensioLabs experts (2 to 6 day sessions -- French or English).

Discover the SensioLabs Support

Access to the SensioLabs Competency Center for an exclusive and tailor-made support on Symfony

Fabien Potencier
Symfony 2.3.1 released
by Fabien Potencier – June 11, 2013 – 10 comments

I've just released Symfony 2.3.1 which mainly fixes three annoying bugs that we have discovered in Symfony and the Symfony Standard Edition:

  • a regression in the handling of console command exit code;
  • a regression in the management of service aliases in the container;
  • a typo in the Doctrine entity generator.

Comments RSS

  • Metfan
    #1 Metfan said on the 2013/06/11 at 16:42
    how be sure to get the right version (2.3.0 vs 2.3.1) without composer.lock?
  • Shady
    #2 Shady said on the 2013/06/11 at 17:04
    Nice work :)
  • Sanpi
    #3 Sanpi said on the 2013/06/11 at 17:13
    @ulrich Use the tilde operator: (ie: "~2.3.1")
  • Christophe Coevoet
    #4 Christophe Coevoet said on the 2013/06/11 at 17:14
    @Ulrich running "composer update symfony/symfony" will update Symfony to 2.3.1. and your project should have a lock file
  • Peter Kokot
    #5 Peter Kokot said on the 2013/06/11 at 21:33
    Thanks for the release. Some useful fixes are included indeed. If anyone doesn't know yet how to be sure to have symfony project updated you can check diff tool on GitHub, for instance:
  • Andrew
    #6 Andrew said on the 2013/06/13 at 04:56
    After updating from 2.3.0 I'm getting an error, PHP Fatal error: Class 'Symfony\\Bundle\\WebProfilerBundle\\WebProfilerBundle' not found. I can't find a solution to this problem. The WebProfilerBundle exists where it should in vendors.
  • Andrew
    #7 Andrew said on the 2013/06/13 at 07:05
    FYI, My php-intl was out of date on centos 6.4. I compiled the latest library following this guide, . Updated with composer and everything is functioning as I'd expect. Why has this dependency been required in the latest release? I can't see anything in the document regarding this requirement either.
  • Art Hundiak
    #8 Art Hundiak said on the 2013/06/18 at 13:16
    Perhaps we could update the composer installation command on the download page? It still shows 2.3.0.
  • Leandro Loiacono
    #9 Leandro Loiacono said on the 2013/06/28 at 12:37
    I have a 2.2.3 project on my osx 10.8.4
    When y try to execute the command php composer.phar update or php composer.php update symfony/symfony I get "Nothing to install or update"
  • Vincent Gross
    #10 Vincent Gross said on the 2013/06/30 at 22:19
    If i download the project with composer command "php composer.phar create-project symfony/framework-standard-edition path/ 2.3.0" everything works fine but if i make à git repo with this project, when i clone the repo and install vendor i have random error 500 like @Andrew error. When i look the difference between the project initial and the project in a clone of the repo with the linux diff command, i have different files for vendor/autoload, vendor/composer/autoload_real and vendor/composer/installed.json. I don't know why i have this behaviour ?