Ok, it seems this is only a problem with cli.  It's has to do with the
simpleAutoloader class in /symfony/data/bin/symfony.php.  It's
completely different than that of sfAutoloadConfigHandler.class.php

On May 31, 9:44 pm, isleshocky77 <[EMAIL PROTECTED]> wrote:
> I will use sfDoctrinePlugin as my example because this is where I ran
> across the bug.  sfDoctrine throws the entire Doctrine library into
> obviously the lib directory of the plugin.  Doctrine adheres to Zend
> and Pear naming standards.
>
> When symfony loads up Doctrine it so happens it loads it after the lib/
> model files which in turn overwrites and classes which might already
> exist.
>
> First
> model/lib/doctrine/Country.class.php which has my Country class in it
> is loaded as Country for symfony.
>
> Then
> /plugins/sfDoctrine/lib/Doctrine/validators/Country.php containig
> Doctrine_Validator_Country is loaded as Country for symfony.
>
> When symfony tries to access Country it now throws an exception saying
> that the Class does not exist.
>
> This will cause havoc if I have any table/class named anything which
> has a corresponding misnamed (named by zend standards) file.
>
> My ticket is:http://trac.symfony-project.com/trac/ticket/1807


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to