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-modelAs for every 1.0.X release, after upgrading to 1.0.2, don't forget to clear the cache of your projects.
Published in
#Releases
Does pear upgrade work?
#shell$ pear upgrade symfony/symfony Nothing to upgrade #shell$ symfony -V symfony version 1.0.1
And pear upgrade-all ? It works fine for me
very nice Thank you Fabien POTENCIER for such a great growth of symfony
Just upgraded on a fairly large project and all looks fine here.
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.
Antonio, I had the same problem. Upgrade-all didn't work either. Using "pear upgrade -f symfony/symfony" did the trick.
I must be missing something too...
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?
@Visa @ccors
In my experience the only thing to do is to wait.
Maybe a transparent caching proxy is the problem? Because pear remote-list displays 1.0.2.
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
:)
The Changelog for PEAR 1.5.3 tells Fix Bug #10771: upgrade-all/upgrade will not upgrade non-PEAR channels [cellog]