swilhelm wrote:
>
> Did you getting any direct responses? Did you resolve this problem?
>
> Would be interested in hearing the solution.
>
> - Steve W.
>
Hello,
The only solution i found for now is adding it into include_paths, although
i tried to avoid it using autoloader. Anyway it does
Mark Wright-3 wrote:
>
> I imagine you just need to have it in your include path. You should be
> able to add it when you figure out which module is being used, maybe
> in a controller plugin. If the namespaces are different for each
> module you might want the autoloader set to load all namesp
I imagine you just need to have it in your include path. You should be
able to add it when you figure out which module is being used, maybe
in a controller plugin. If the namespaces are different for each
module you might want the autoloader set to load all namespaces,
unless you can set this after
Did you getting any direct responses? Did you resolve this problem?
Would be interested in hearing the solution.
- Steve W.
dmitrybelyakov wrote:
>
> I've been fighting it for the whole day now, and it doesn't get any more
> clear for me.
>
> The idea is simple, i want to have my library c
I've been fighting it for the whole day now, and it doesn't get any more
clear for me.
The idea is simple, i want to have my library code under one of my module
directories. Like this:
/application/modules/somemodule/
/application/modules/somemodule/controllers
/application/modules/somemodule/mo
