Hi, We know that symfony's autoload mechanism separates classes into two levels or scopes, global and module. Module classes lie under apps/ [appname]/modules/[module_name]/lib, and access is limited to the same module scope.
Consider this situation: I want to write a class which is "sfBaseUserAction extends sfAction". It provides additional methods for the user module. As it is solely used by the user module it should be placed under "modules/user/lib/sfBaseUserAction.class.php", and user module actions should extend from it. Sounds good, but since module name is not set when the module action is being loaded, symfony fails detecting the existence of "user/sfBaseUserAction" and autoloading fails. Moving it to application lib/ directory is ok, but as it is somewhat dedicated I prefer not to mess with app or porject lib. Is it possible to add one more fallback in autoloading for this case? Tamcy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
