Page 1 of 1

using the module_custom directory

Posted: Thu Dec 07, 2006 3:17 am
by jmcgin51
Is there any secret to using this functionality?

In another thread, someone posted that:
"This functionality was added in the 0.12 series to allow overriding any string in any module without having to worry about re-changing that file when you upgrade the module."

If you include a customized version of a file in the module_custom, do you have to remove it from the "normal" module directory?  For example, if I customize FrontEndUsers.api.php and put the customized version in module_custom/FrontEndUsers, should I remove FrontEndUsers.api.php from the modules/FrontEndUsers directory?

Re: using the module_custom directory

Posted: Thu Dec 07, 2006 4:14 am
by calguy1000
The module_custom stuff is only for language strings, not for the code php files.

The system only looks in the module_custom directory when doing a language lookup.

Re: using the module_custom directory

Posted: Thu Dec 07, 2006 12:40 pm
by jmcgin51
ok, that makes sense - thanks...