Hi David, this bug was introduced in Rev1092 and is fixed in 1093.
Fabian (not fabien) is already aware of this bug as it is reported in http://trac.symfony-project.org/ticket/5768 The issue is only relevant for users who use the svn version of symfony and have updated their svn between Friday and yesterday. It can be solved by updating symfony again. Those who use the releases are not affected. Carsten On Tue, Feb 3, 2009 at 11:09 AM, David Herrmann <[email protected]> wrote: > > A really nasty Propel bug slipped into Symfony 1.2.3: > http://propel.phpdb.org/trac/ticket/715 > > It was fixed yesterday: > http://propel.phpdb.org/trac/changeset/1093 > > I stumbled upon it today > (http://forum.symfony-project.org/index.php/m/71311/) and found the > reason after 2 hours of searching. > > I recommend an immediate release 1.2.4 to fix this because it may break > many applications. > > Best regards, > > David > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
