symfony 1.0.2 is released
April 17, 2007
·
Published by
Fabien Potencier
I released symfony 1.0.2 yesterday. As for every 1.0.X release, there is no new feature, just some bug fixes.
Here are all bugs fixed in this release:
- r3785: fixed getCookies() call in sfDebug when using sfConsoleResponse (#1666)
- r3775: fixed _compute_public_path() when using a query string
- r3754: updated Propel to 1.2.1 (http://propel.phpdb.org/trac/query?status=closed&milestone=1.2.1&resolution=fixed&order=priority)
- r3746: fixed output escaping and _get_object_list() (#1593)
- r3699: fixed highlight_text() doesn't work with / (#1621)
- r3692: fixed i18n support for errors in sfRequest
Propel has been upgraded to 1.2.1. It fixes some small bugs in the Propel templates, so you have to rebuild your model:
symfony propel-build-model
As for every 1.0.X release, after upgrading to 1.0.2, don't forget to clear the cache of your projects.
Log in to add a reaction to this post
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
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
#shell$ pear upgrade symfony/symfony
Nothing to upgrade
#shell$ symfony -V
symfony version 1.0.1
It works fine for me
Thank you Fabien POTENCIER for such a great growth of symfony
antonio, I upgraded using "pear upgrade ..." without issue. In the past though I have had some issues with something like that - I did a "pear uninstall ..." first, then installed Symfony again.
pear upgrade - nothing to update
pear upgrade-all - nothing to update
pear channel-update - up to date
If I use -f it starts downloading 1.0.1.
Used pear clear-cache and tried again - the same thing.
Any ideas?
@ccors
In my experience the only thing to do is to wait.
Well, I connected via another gateway trough which I haven't used pear. It still didn't want to upgrade via pear upgrade symfony/symfony, but -f did the job. This time 1.0.2 was downloaded.
So, I think all these problems could be because of a transparent cache of some small response/file from pear's system.
@Akinas
:)
Fix Bug #10771: upgrade-all/upgrade will not upgrade non-PEAR channels [cellog]