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
Say hello to the the second release candidate of symfony 1.1
by Nicolas Perriault – June 09, 2008 – 4 comments

The second release candidate of symfony 1.1 has been released today. Here's a quick changelog:

  • Added the ability to merge forms
  • Secured non-production controllers by default by inserting an IP check for 127.0.0.1 into those controllers.
  • Refactored renderPartial() and renderComponent() in sfAction (code has been splitted to create a getPartial() and a getComponent() method)
  • Fixed sfForm cannot handle sfValidatorFile in embed form
  • Fixed internal URI when a route has some default parameters not present in the pattern
  • Fixed cloning unbound sfForm triggers unnecessary validation
  • Fixed I18n forms saving twice the i18n objects, once with empty default objects and once with bound objects
  • Fixed sfWidgetFormSchema rendering when there are only hidden fields
  • Fixed yml validator file can be overriden by a remote attacker
  • Propel schema inheritance is now supported by Yaml schema syntax
  • Syck extension support has been removed
  • Better phpdoc for the whole code

To upgrade an existing project based on another 1.1 beta, you have to run the following commands:

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

To upgrade a project using symfony 1.0, you're invited to carrefully read the UPGRADE file.

The next step will be the release of symfony 1.1 stable.

Add a Comment

You must be connected to post a comment.

Comments RSS

  • gravatar
    #1 IsRobot said on the 2008/06/10 at 15:04
    For those wanting to upgrade symfony using PEAR you may need to specify the channel/pakage version e.g.
    pear upgrade symfony/symfony-1.1.0RC2
  • gravatar
    #2 Peter Blazso said on the 2008/06/10 at 19:29
    IsRobot:
    For me the following command also worked with no problem at all:
    pear upgrade symfony/symfony-beta
  • gravatar
    #3 fabien said on the 2008/06/10 at 19:55
    @Peter: You really need to use symfony/symfony-1.1.0RC2 because symfony/symfony-beta will install the latest beta or stable. So, next time we release a 1.0 version, it will install it instead of 1.1.
  • gravatar
    #4 Luã de Souza said on the 2008/06/13 at 04:53
    "The next step will be the release of symfony 1.1 stable."

    And i can't wait to use it! :D
    Nice work.