symfony 0.6.3 released

June 23, 2006 • Published by Avatar of Francois Zaninotto Francois Zaninotto

The new 0.6.3 stable release of symfony is there, up and running, and it is expecting your download. It is not a major release, but it fixes some bugs and brings some small enhancements. As it doesn't break BC, there is no reason why you shouldn't upgrade.

So open a CLI and simply type:

$ pear upgrade symfony/symfony-stable

With this release, you will benefit from the efforts made by the symfony developers during the past two months. Here is a quick changelog:

  • calendar language files update (pl, zh, nl, no, it)
  • new options for the sfFillInFilter filter
  • major sfWebDebug refactoring (no more dependency on prototype)
  • position option to stylesheets in view.yml
  • native support for JSON/AJAX actions
  • better exception layout
  • new sfPropelUniqueValidator validator
  • new component and partial cache
  • updated creole and propel
  • zend framework and ez components bridges
  • new hooks in admin generator generated classes
  • better date support in admin generator
  • new project control panel for CLI replacement in development
  • lot of small tweaks and enhancements in admin generator
  • lot of bugs fixes and small enhancements

There are two warnings about the use of the 0.6.3:

  • If you use i18n Propel support in your schema.xml or if you have problems building you Propel model/sql (error thrown : "XML schema file (PATH/config/schema.xml) does not validate"), you can add a propel.schema.validate = false at the end of your config/propel.ini file. This setting is by default for all new projects.

  • Actions in the routing are now case sensitive. If you have a page with an action named fooBar, your action method must be named exactly executeFooBar.

For more details about the 121 tickets closed since 0.6.2, you can read the custom trac report or the weekly dev news in the wiki.

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

Avatar of pierre
pierre said on Jun 23, 2006
Is there andy documentation out there about the ZF/EZC bridges? I worked with this frameworks already, and I wanna see what this bridge can offer me.
Avatar of François Zaninotto
François Zaninotto said on Jun 24, 2006
Pierre: try the custom extensions chapter in the symfony book

http://www.symfony-project.com/content/book/page/custom_helper.html
Avatar of Mohammad
Mohammad said on Jun 24, 2006
WOW it's wonderful
Avatar of NiKo
NiKo said on Jun 25, 2006
Well, I've just upgraded and now I got a strange message : "Configuration file "/usr/share/php/data/symfony/config/php.yml" specifies that php.ini "magic_quotes_gpc" key must be set to "". The current value is "1" (php.ini location: "/etc/php5/apache2/php.ini"). [err0001]"

... While the settings are corrects in my php.ini :-?
Avatar of NiKo
NiKo said on Jun 25, 2006
The problem seem to be variable type misunderstanding while parsing php yaml conf files in this new version.

Indeed, this is a vardump of the result of the parsing of my php.yml file (in ./util/sfYaml.class.php) :

array(2) {
["set"]=>
array(3) {
["magic_quotes_runtime"]=>
bool(false)
["log_errors"]=>
bool(true)
["arg_separator.output"]=>
string(6) "\&"
}
["check"]=>
array(3) {
["magic_quotes_gpc"]=>
bool(false)
["register_globals"]=>
bool(false)
["zend.ze1_compatibility_mode"]=>
bool(false)
}
}

which is :

set:
magic_quotes_runtime: off
log_errors: on
arg_separator.output: \&

check:
magic_quotes_gpc: off
register_globals: off
zend.ze1_compatibility_mode: off

... so the test in ./config/sfPhpConfigHandler.class.php compare booleans with... php.ini strings.

But maybe it's my config or I missed something...
Avatar of daniel
daniel said on Jun 26, 2006
all my ajax and rico has stopped working with the new update..

what the??
Avatar of Peter
Peter said on Jul 14, 2006
Quite bad that actions and routing are now case sensitive :(
Perhaps we could have additional setting in settings.yml to turn this feature on and off?

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.