I did the same thing in sfFormtasticPlugin, but have since noticed
allowances in sfRootConfigHandler for this issue. It appears you can
provide a "file" key along side your "class" key, which would read
something like "%SF_PLUGINS_DIR%/sfFormtasticPlugin/lib/config/
sfFormtasticYamlConfigHandler.class.php" ... This adds a
"require_once" call to the cache file.
Kris
On Aug 24, 2008, at 3:50 AM, chrisk <[EMAIL PROTECTED]> wrote:
>
> Hello Kris,
>
> I experienced the same problem, when the config handler was registered
> through application's config_handler.yml.
>
> When I registered the config handler in the plugins config.php it
> disappeared....
>
> register the config handler in config.php with:
>
> $this->getConfigCache()->registerConfigHandler('config/
> my_custom_config.yml', 'sfMyCustomConfigHandler', array());
>
> Regards,
> Christian
>
> On 6 Aug., 18:08, Kris Wallsmith <[EMAIL PROTECTED]> wrote:
>> Has anyone experienced fatal errors when using plugins that provide
>> config handlers? I'm working on sfFormtasticPlugin, which includes a
>> config handler, and it works fine when the application is in the dev
>> environment. The strange this is that is stops working when I switch
>> to prod (or any non-dev environment).
>>
>> It appears sfRootConfigHandler is executed before sfAutoload is
>> registered so symfony doesn't know to look in the plugin lib dirs (in
>> my case for sfFormtasticConfigHandler). I have no idea why this works
>> in dev...
>>
>> Any ideas?
>>
>> Kris
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
