Hi
I'm working on xswatch5
and for now, i keep the original file theme_autorun.php from xswatch4.

In this file :

Should we had a new file
XoopsFormRendererBootstrap5.php
in the /class/xoopsform/renderer directory ?

https://github.com/alain01/xswatch5

1st step :
- Add 4 news themes
- Updated bootstrap.min.css + bootstrap.bundle.min.js + bootstrap.bundle.min.js.map to Bootstrap v5.0.0.
- Removed the templates in the modules directory

Bootswatch v5 :

21 themes yet known + 4 new themes :
- Morph (neumorphism design theme)
- Quartz (glass design theme)
- Vapor (dark theme)
- Zephyr (light theme)

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?

Boostrap V5.0.0 is available now !

And bootwatch with bt5 since today ! (https://bootswatch.com/ )

So,
My first objective is to update xswatch 4 to xswatch5.

I'm starting with the heart of the theme,
After that, I will check the overloaded templates for modules.

I think I will need help for the overloaded templates for modules.

I will come back here with a link on a repository.

Beep !

Interresting,

I 've tryed but my MYSQL courses are too far in my head...

I understand what we should do it but not in SQL !

1 - find all uid with with groupid = 5 (easy : SELECT * FROM `xe07_groups_users_link` WHERE `groupid` = 5)
2 - List for each uid with groupid=5, and find their other groupid <> 5
3 - delete these lines

So you keep all uid with groupid = 5

I want to see the SQL request

"remove duplicate occurrence in SQL" but dont keep the first occurrence (keep the occurence with groupid = 5 )

Humm,
so,
there is a bug in the overloaded templates system... with admin templates,
or
a bug in your module...

That is the question.

Quote:?
Goffy,
if the overloaded files are not present, the module use the initial templates by default, admin too.
Why not here ?

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)