> Doctrine has config handlers defined as follows:

> # cat plugins/sfDoctrinePlugin/config/config_handlers.yml
> config/doctrine.yml:
>    class:    sfDoctrineConfigHandler

> config/schemas.yml:
>    class:    sfDoctrineSchemasConfigHandler

> When a sf1.1 project starts up, the lib/projectConfiguration file
> registers sfCoreAutoload, which handles the base autoloading required
> for bootstrapping.  However...

> in ./lib/vendor/symfony/lib/config/sfApplicationConfiguration.class.php,
>   we have this:

>   97   public function initConfiguration()
>   98   {
> ..
> 107     // required core classes for the framework
> 108     if (!sfConfig::get('sf_debug') && !sfConfig::get('sf_test'))
> 109     {
> 110       $configCache->import('config/core_compile.yml', false);
> 111     }
> 112
> 113     sfAutoload::getInstance()->register();

> This causes this:

>   Fatal error: Class 'sfDoctrineConfigHandler' not found in
> /var/www/localhost/cache/frontend/prod/config/config_config_handlers.yml.ph p
> on line 29

> This file contains:

> 29 $this->handlers['config/doctrine.yml'] = new sfDoctrineConfigHandler();
> 30 $this->handlers['config/schemas.yml'] = new
> sfDoctrineSchemasConfigHandler();

> Now, the problem this is failing, is because the real autoloader isn't
> started till line 113 in the aplicationConfiguration  class show above,
> but the file is being imported at line 110.

> For now, I've  got around this issue by manually including these classes
> in my project config class, but that's no real fix :)

> Any ideas?

> Ian P. Christian wrote:
>> Hi all!

>> Doctrine has config handlers defined as follows:

>> # cat plugins/sfDoctrinePlugin/config/config_handlers.yml
>> config/doctrine.yml:
>>    class:    sfDoctrineConfigHandler

>> config/schemas.yml:
>>    class:    sfDoctrineSchemasConfigHandler

> You can specify a file in config_handlers.yml like this:

> config/schemas.yml:
>    file:
> %SF_LIB_DIR%/doctrine/.../sfDoctrineSchemasConfigHandler.class.php
>    class:  sfDoctrineSchemasConfigHandler

> Fabien

>> When a sf1.1 project starts up, the lib/projectConfiguration file
>> registers sfCoreAutoload, which handles the base autoloading required
>> for bootstrapping.  However...

>> in ./lib/vendor/symfony/lib/config/sfApplicationConfiguration.class.php,
>>   we have this:

>>   97   public function initConfiguration()
>>   98   {
>> ..
>> 107     // required core classes for the framework
>> 108     if (!sfConfig::get('sf_debug') && !sfConfig::get('sf_test'))
>> 109     {
>> 110       $configCache->import('config/core_compile.yml', false);
>> 111     }
>> 112
>> 113     sfAutoload::getInstance()->register();

>> This causes this:

>>   Fatal error: Class 'sfDoctrineConfigHandler' not found in
>> /var/www/localhost/cache/frontend/prod/config/config_config_handlers.yml.ph p
>> on line 29

>> This file contains:

>> 29 $this->handlers['config/doctrine.yml'] = new sfDoctrineConfigHandler();
>> 30 $this->handlers['config/schemas.yml'] = new
>> sfDoctrineSchemasConfigHandler();

>> Now, the problem this is failing, is because the real autoloader isn't
>> started till line 113 in the aplicationConfiguration  class show above,
>> but the file is being imported at line 110.

>> For now, I've  got around this issue by manually including these classes
>> in my project config class, but that's no real fix :)

>> Any ideas?

> config/schemas.yml:
>     file:
> %SF_CURRENT_DIR%/../lib/sfDoctrineSchemasConfigHandler.class.php
>     class:  sfDoctrineSchemasConfigHandler

> I'm not sure about the name...

> What do you think?

>> Or, if you don't want to hardcode the path, perhaps we can add a new
>> shortcut to able to do something like this:

>> config/schemas.yml:
>>     file:
>> %SF_CURRENT_DIR%/../lib/sfDoctrineSchemasConfigHandler.class.php
>>     class:  sfDoctrineSchemasConfigHandler

>> I'm not sure about the name...

>> What do you think?

> That's certainly a good idea... but yes, not sure about the name.

> This will of course allow plugins to be renamed locally without any
> changes, for whatever odd reason someone might want to do it.... ;)

> 'current' dir does seem wrong...  'this' dir doesn't seem much better
> though.  Maybe 'relative' makes some sense.

> Adding file: to my config_hamders.yml causes a really really odd error:

> sfParseException: Configuration file
> "/var/www/localhost/lib/vendor/symfony/lib/config/config/config_handlers.ym l"
> specifies category "category" with missing class key. in
> /var/www/localhost/lib/vendor/symfony/lib/config/sfRootConfigHandler.class. php
> on line 63

> I'm busy trying to figure that out at the moment, but if you have any
> bright ideas, I'm all ears :)