Ok, that makes sense. However it seems sensible for this functionality  
to be added to the autoloader. Infact, it seems as if almost all the  
code needed to implement this functionality is already there. Was it a  
deliberate decision to exclude this?? if so, what was the rationale??



On 8 Oct 2008, at 08:26, Thomas Rabaix wrote:

>
> Yep, you have a point. The actions class inside plugin are getting
> indexed because they are matched by the autoloader. It's a wrong side
> effect.
>
> But all plugins I have see so far included base* class. This should be
> more discussed in the dev mailing list.
>
> Thomas
>
> On Tue, Oct 7, 2008 at 10:12 PM, Ian Christian <[EMAIL PROTECTED]>  
> wrote:
>>
>> 2008/10/7 Thomas Rabaix <[EMAIL PROTECTED]>:
>>>
>>> Ok,
>>>
>>> BaseClass* should be include on the top of the child one.
>>>
>>> I didn't spot that the first time I read the post.
>>>
>>> include_once sfConfig::get('sf_plugins_dir').'/yourPluginPlugin/ 
>>> modules/yourPlugin/lib/baseyourPluginActions.class.php';
>>
>> If this is indeed the case, why is Jonathan seeing this in his  
>> autoloader cache?
>>
>> {{{
>> // plugins module lib
>> 'ifdsContactForm/BaseifdsContactFormActions' =>
>> '/Users/jonathan/Sites/ifds.4/plugins/ifdsContactFormPlugin/modules/ 
>> ifdsContactForm/lib/BaseifdsContactFormActions.class.php',
>> }}}
>>
>> I've not had a chance to look at this myself, but.... It seems odd
>> that you might have to manually include the file when the autoloader
>> is finding the class, and putting it into the autoload cache, albeit
>> with a prefix on the key.
>>
>>>
>>
>
>
>
> -- 
> Thomas Rabaix
> Internet Consultant
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to