symfony 1.2.1 released

The release of symfony 1.2, Jobeet and the Doctrine book was echoed with a lot of feedback. Thanks a lot for that. Personally I am very happy with the quality of our 1.2 release, because I expected more nontrivial bugs :-) Of course when claiming such good quality, we really should have made our homework, which I am now presenting. Be assured that we will continue to make this release better. And start working on 1.3 next year.

Todays release 1.2.1 addresses some of the bugs reported to us during the last two weeks. We concentrated on those issues that are most important to new users which we are attracting with Jobeet. And more important, we fixed a Bug which would prevent you from successfully running tomorrows Jobeet day. So if you want to be prepared, update today!

Changelog

  • Sorting does not work in Admin Generator because fields are always marked as calculated (see ticket #5123)
  • calling setPluginPath() did not work correctly in plugin:publish-assets (see ticket #5123)
  • sf_route object in exception and log kills PHP (see ticket #5178)
  • sfValidatorDoctrineChoice replaces "froms" and "joins" of custom queries (see ticket #5192)
  • clob datatype in schema.yml was not treated correctly by forms and filters (see ticket #5263)
  • certain urls could not be generated correctly when passing in 0 as parameter value (see ticket #5175)
  • Propel Logging is less usable than with Propel 1.2, because it does not replace placeholder values (see ticket #5180)
  • DoctrinePlugin does not allow top level schema elements (see ticket #5180)
  • renderLabel() does not honor for option (see ticket #5220)
  • Doctrine Admin generator Batch deletion does not work (see ticket #5231)
  • Overriding the Admin Generator configuration did not work correctly (see ticket #5137 and ticket #5140)

Additionally two performance enhancements have been contributed by community fellow "Wicked", thanks! (Looking forward to more :-))

Upgrade

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

$ pear upgrade symfony/symfony-1.2.1

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

and enjoy your shiny new symfony 1.2.1!

Comments

Nice and quick release!
Thanks friends !!!. I'm surprised about your quick answer. Thanks again.
I freezed Symfony 1.2
How do I upgrade?

unfreezed, do Pear upgrade
then freeze again?
The debug toolbar still shows 1.2.0-DEV. Is this O.K.?
I just upgraded via svn to revision 13966. When I check the version it reports 1.2.0-DEV.
by

$ pear upgrade symfony/symfony-1.2.1

I upgraded symfony 1.0.* (previous version) to 1.2.1, but no upgrade the symfony folder under jobeet/lib.

What can I do?
About the performance enhancements. Is stripComments used by cache or is it something you have to use yourself?
Upgrading from 1.2.0 to 1.2.1 gives me following error

Call to undefined method backendConfiguration::getLibDirs
@Kai,@Brett:
I forgot to update the version in dev. This is fixed now.
@Douwe:
its used by the core compilation generation once after the cache has been cleared
@Andrea:
Somebody reported this in IRC as well, it works for me. Do you have a SVN a PEAR Version?
I just upgraded symfony via pear.
Afterwards i issued a symfony propel:build-all-load in my project followed by a symfony cc.
Still my debug toolbar shows version 1.2.0. What gives?

Thanks, Kai
Hi there!
I have a problem installiing Symfony 1.2.1 in a new server (dreamhost)... when I type:

php lib/vendor/symfony/data/bin/symfony -V

I get:
Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /jobeet/lib/vendor/symfony/data/bin/symfony on line 16

has any one else had this problem too?

Best,
Gustavo
Hi again...
It was for my PHP version... if anyone else has this problem in Dreamhost, I had to type: "/dh/cgi-system/php5.cgi" instead of "php"
Good luck!
@Fabian Svn version

Comments are closed.

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