(Note from the author ;-) this feat isn't implemented in any released version. I'll remove this comment when it is)
[edit]
1)You can get some info about the current module using
<{$xoops_module.name}>
<{$xoops_module.dirname}>
<{$xoops_module.version}>
in your templates.
If the variable isn't set, that means we're within the "system" module.
[edit]
2)There also is another new template variable called $xoops_modulecss. This one may be, in order of preference:
A) /themes/curtheme/mod_dirname.css (or mod_system.css for system pages) B) /modules/dirname/theme.css C) Undefined (if none of the above files exists)
So, module writers may want to add a theme.css file in their mod dir to define custom CSS classes, etc...
And theme writers can create mod_xxxxx.css files that will override the default one. As the variable may be undefined, add something like this to your main theme file:
<{if isset($xoops_modulecss)}>
<link rel="stylesheet" type="text/css" href="<{$xoops_modulecss}>" />
<{/if}>
Back to the dev:Main Page



![[Main Page]](/modules/mediawiki/images/mediawiki.png)





