Hi all.

I’ve noticed something very peculiar. When editing a template file with the “Update module template .html” option set to Yes in System -> Preferences, Smarty recompiles the template file on any change. As soon as I change my theme from the supplied default theme the update no longer works.

The theme I am changing to is a copy of the default theme with only the logo changed, so nothing drastic there.

It seems that Smarty is only taking the “Update module template .html” into account when XOOPS is set to the default theme. Is this by design or am I missing something? I’m currently debugging through the Smarty code but have only managed to scratch the surface.

Templates can still be recompiled via System -> Modules -> Update but this is a slight pain during template development.

Any help would be greatly appreciated.


Cheers.

Well, theres a few things goinf on here.

The admin | preferences setting for “Update module template .html” only applies to the main XOOPS theme in use.

If you want to edit the module templates,
You still have to do the System -> Modules -> Update to update the modules template changes.


Thats how it works, and its rather intuitive to me. But I can see the possible confusion.


After a while, it will be easier to understand why i think.


Hope that helps,

Quote:
It is by design, since other themes than the default can override templates by placing templates in themes/yourtheme/templates/modulename/ folder.

A side-effect of this setting is that the theme.html is recompiled, but the main objective of this setting is that themes can override module templates like I just outlined.

@Mith: Thanks for that. I'll stick to the default theme while developing templates.

@hyperpod:

Thanks for the answer.

Quote:

I can confirm that with this setting on, not only does the theme.html file get recompiled if modified, but also any module template files as well (when modified)... but only if the default theme is selected.

I am finding this rather handy as I am developing my templates in a module because the change comes through immediately and without the need of a System -> Modules -< Update Module.

Thanks for the answers.

Cheers.