Fabian Lange
I know, symfony 1.2 is not in the focus right now. And its true, there is much more exciting stuff around, but we do not forget about our obligations on older releases. The symfony 1.2 release is pretty stable, and we intended to end its support with this release. However we were convinced by the community that a bit more time on a supported release could help a lot. So we have listened and decided to extend support of symfony 1.2 till the end of February 2010.
Reaching for symfony 1.3
symfony 1.2.10 would not be as packed as it is without our new releases. They were the main driver for many fixed which have been backported to 1.2. Parts of those efforts have emerged out of the fantastic BugHuntDay activities.
Because people showed a lot of interest in the new project:validate task, which will outline all usage of deprecated code, we decided to backport it to 1.2 to allow graceful migration towards 1.4. But please note that fixing all the deprecations reported by project:validate will be only one part of the process. You still need to do the regular 1.3 upgrade.
Amount of changes for 1.2
We normally are very strict on what gets into a stable release. The slightly larger amount of fixes contained in 1.2.10 is mainly because of the 1.3 activity, but also because of increased feedback and number of good quality tickets. I took extra care to make sure that this release is a fully compatible drop in for everybody. So in case there is anything fishy going on with it, please let me know asap.
Noteworty changes
Some 1.2.10 development highlights:
- 304 Not Modified now finally works correctly. We do not know why this was broken since 1.0 r24619
- MemcacheCache metadata no longer grows r24607r23925
- Fixed incorrect headers for Servers running in cgi-sapi mode r23984
- Doctrine is now upgraded to version 1.0.14. Changes from Doctrine Jira
of course the full changelog is also available, listing all the details.
How to install
Please upgrade your existing projects by updating the reference to the 1.2.10 subversion tag or by running the PEAR upgrade command:
$ pear channel-update pear.symfony-project.com
$ pear upgrade symfony/symfony-1.2.10
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
I'm getting
Error getting channel info from pear.symfony-project.com: File http://pear.symfony-project.com:80/Chiara_PEAR_Server_REST/p/packages.xml not valid (received: HTTP/1.1 404 Not Found ) Nothing to upgrade
Hi Zuzanna, I forgot to mention that you need to update the pear channel:
pear channel-update pear.Symfony-project.com
Fabien could You add something to file lib/request/sfWebRequest.class.php in new version of Symfony ? On many FREE hostings we are INSIDE catalog 'public_html' - and we can't go ABOVE, we must publish ALL symfony files INSIDE catalog 'public_html' - then there was a problem in symfony 1.2. Here is a solution: http://trac.symfony-project.org/ticket/7543 Could you add this code to new version of symfony ? If You don't understand something I can say explain. This solution it isn't my idea, I have found it on some polish site about the biggest hosting in Poland and about Symfony. It would be a good idea to add this solution to new version of symfony.