Dustin, would the attached patch work for you? On Mon, Sep 29, 2008 at 12:49 PM, Kiril Angov <[EMAIL PROTECTED]> wrote: > Yes, let's do the special case for the __toString() because Symfony > 1.2 may fix the i18n issues with the admin generator but for 1.1 the > above method seems to be the only reasonable way to deal with i18n > tables. > > Thank you, Dustin. > > On Mon, Sep 29, 2008 at 12:32 PM, Dustin Whittle > <[EMAIL PROTECTED]> wrote: >> >> Kiril, >> >> The issue is when you have a __call() defined in a model, then this was >> always being returned true when looking for __toString. Maybe is_callable is >> better, and have method_exists check only for __toString checks? >> >> Cheers, >> >> Dustin >> >> >> On 9/28/08 9:32 AM, "Kiril Angov" <[EMAIL PROTECTED]> wrote: >> >>> >>> Hello, >>> >>> I was using for quite some time and on an ongoing project (symfony >>> 1.1) the method described here >>> http://trac.symfony-project.org/wiki/HowToHandlei18nDbFieldsWithAdminGenerator >>> Method2 >>> which works solely because of is_callable() in the ObjectHelper. With >>> the http://trac.symfony-project.org/changeset/10977 revision, this no >>> longer works and I was wondering exactly what Propel 1.3 compatibility >>> it fixes? Can we find a middle ground so that we can at least work >>> with i18n fields in the admin generator? >>> >>> Thanks, >>> Kiril >>> >>> > >> >> >> >> >> >> >> >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
ObjectHelper.patch
Description: Binary data
