symfony 1.2.4 - Fixing two unfortunate regressions

The symfony 1.2.3 release introduced two regressions, and to prove that symfony favors no ORM, both got one :-). Just kidding. I am very sad about this having happened, but thats life, and even more important that we resolve the issue in a timely manner. I am sorry for any inconvenience these regressions might have caused.

Besides these two regressions I also included a patch for people who are experiencing corrupted cache files under heavy load. For details please check Ticket #5729.

The whole list of closed tickets can be found in the Trac Roadmap for 1.2.4 or the Changelog file

Upgrade

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

$ pear upgrade symfony/symfony-1.2.4

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

Comments

Thanks a lot Fabian.

This also fixes a nasty bug I had been dealing FOR DAYS which prevented my application from properly updating DATE fields which were working fine before ver 1.2.3.

I would always end with "0000-00-00" in the DATE fields in my MySQL database.

I know other folks must be dealing with the same bug. It's over!

Congratulations again to the whole Symfony development community.
Nice update. Quick question (may be not the right place).

When are you planning to set up the jobeet wbesite ?

Comments are closed.

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