Archives


Master Symfony2 fundamentals

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

Symfony hosting done right

ServerGrove, outstanding support at the right price for your Symfony hosting needs.
servergrove.com

L'audit Qualité par SensioLabs

200 points de contrôle de votre applicatif web.
audit.sensiolabs.com

gravatar
symfony 1.2.9 is ready to use
by Fabian Lange – September 27, 2009 – 4 comments

... but even a pretty stable symfony 1.2 deserves bugfixes from time to time.

Highlights

Let's highlights some changes from the symfony 1.2.9 release changelog (which is worth a read)

ORMs

Doctrine has been updated from doctrine 1.0.10 to doctrine 1.0.12. More details are in the Doctrine Changelog for 1.0.11 and 1.0.12.

Propel had some tasks fixed which were not respecting connection information.

Forms and Admin Generator

After a few fixes now the forms and admin generator like each other much better and respect options passed to them.

Routing

The routing cache has been turned off by default. We found out that this is the much better setting for many projects. The new default config looks like this:

routing:
    class: sfPatternRouting
    param:
      cache: ~

Beside that, the handling of sf_method in tasks is now corrected.

Testing

Lime has been updated and is now more reliable in evaluating the test results.

PHP 5.3 compatibility

While symfony 1.2 should work fine in PHP 5.3, we were able to find code in the sfValidatorFile that needed a fix. We also removed a few notices for some edge cases.

Documentation and Typos

We updated a number of PHPdocs to be more accurate and fixed a few typos here and there. Thank you for the many contributions we had during the 1day1ticket initiative!

How to install

Please upgrade your existing projects by updating the reference to the 1.2.9 subversion tag or by running the PEAR upgrade command:

$ pear upgrade symfony/symfony-1.2.9

If you use the 1.2 branch from our SVN repository, just run the svn update command to upgrade your project.

Last but not least, don't forget to clear your cache by running for doctrine:

$ php symfony doctrine:build-model
$ php symfony doctrine:build-forms
$ php symfony doctrine:build-filters
$ php symfony cache:clear

or when using propel:

$ php symfony propel:build-model
$ php symfony propel:build-forms
$ php symfony propel:build-filters
$ php symfony cache:clear

Seeking testers

You might have read Kris posting about symfony 1.3-alpha1. I fully support his efforts and have made great experience with symfony 1.3 already. So perhaps you can try it as well and give feedback?

Future of symfony 1.2

symfony 1.2 is approaching its end of support, so we are getting even more restrictive on patches. Most likely symfony 1.2.10 will come in about 6 weeks and will be the last version of the 1.2 branch. Upgrading to 1.3 should be easy, but in case you want to stick to 1.2 for any reason, please speak up with any problems you might have before we bring 1.2.10 to you.

Add a Comment

You must be connected to post a comment.

Comments RSS

  • gravatar
    #1 Hamza said on the 2009/09/30 at 23:14
    Nice !
  • gravatar
    #2 Nick said on the 2009/10/01 at 04:33
    With routing cache being off (by default), does this mean the routing.yml file will be read off the hard disk with each request?
  • gravatar
    #3 mppfiles said on the 2009/10/02 at 01:58
    Thanks for closing my ticket! (#5305) :D
  • gravatar
    #4 doremon said on the 2009/10/09 at 09:50
    I use sandbox1.2( symfony 1.2.9 ).Ex : i have action Index( executeIndex ), now i write validateIndex it's not run. But when i change to symfony 1.0.21 it's run. I use php 5.2.11. Please help as soon as possible. Thanks.