Hi,
I noticed that some modules offer in addition to basic templates, templates in Bootstrap3, bootstrap4 and soon in Bootstrap5.

Sometimes, it's on the extra directory (extra/Templates for bootstrap 4)
or
/templates_bootstrap/bootstrap4/ (+ /templates_bootstrap/bootstrap3)
or
/EXTRA/themes/xbootstrap/ (+ /EXTRA/themes/templates_fulldiv_opacity/)

I have no preference but 2 points :
1 - for a serious structure, is it possible to normalize the path for the overloaded templates in new adn updateted modules ?

The point 1 is not very important. It's ok for me, whaterver the path

2 - Automatically push overloaded in the theme during installation :

I notice that sometimes the default templates (neither bt3 nor bt4, so not responsive) make the module look really old.
I'm afraid that many webmasters install the modules as is, without knowing that you have to copy the bt3 / bt4 overloads in the theme folder used and therefore see a rather "old" module interface (default templates)

Could we not add a process in the installation of the module which would ask the following question:
(If overload available in the extra folder (other folder)
Do you want to use the overload in your main theme?
----(if yes)
-------- Be careful, if your theme is using bt3, use bt3 overloaded, if it's bt4, use bt4
-------- (if bt3 available) : copy "bt3 templates" ? (end if)
---------(if bt4 available) : copy "bt4 templates" ? (end if)
----(end if)
(end if)


I dont know if my idea is clear,
but remember,
lot of webmasters download modules, install them, then use them as is (default templates)

good idea alain,

will be great if this can be implemented since the bootstrap will be continue to be updated from time to time

Beep !

I see a potential issues with it - the module doesn't know which version of Bootstrap the currently selected theme is using.

And what happens when the user/admin changes the theme to a different one? Should the Core go through all installed modules and check if there are the templates for this theme? But the Core should be first aware of the Bootstrap version used by the theme.

This would probably require a major rewrite of the Core...

I agree with Mamba.

There is no way to know for sure what a theme is using. Even if the bootstrap js files are present in some directory, that doesn't mean that is what it is loading. Best we could ever do is guess, and that sort of decision needs to be made by the site owner, not some buggy algorithm.

Two other points, the module install and updates are NOT interactive. Both are a single function call that either works or fails. Many things depend on this behavior, and it won't be changing. Also, the themes directory is NOT required to be writable by the web server. This is a very good thing for security. On a well secured XOOPS, you won't be able to copy the files without some extra effort.

This sounds more like education and standardization needs, not a code change.

Ok thank you, Mamba and Richard for your answer !

Quote:
ok, can we standardize the structure of the available themes that accompany the package of a module?