Terence J. Grant schrieb:
Good suggestion, but the css.php does not read that either. It is not about how to save the currently used template for the visitor (more clear a user that can not login into the wiki) it is about the css.php to notify that the template has just changed and therefore another style, means layout.css and design.css, is needed to be send. This changing of templates can take place at any time the visitor wants it to and there is no information left of the template that has been used when the visitor leaves. It is only for the current Session.Basically you are right, but the meaning of "change the template on a per user " can be mistaken on this topic. I don't want a special user to change the template. It is for everybody, having no special group, not being loged in or something, so I think the multitemplate does not really apply.
Fix: Use cookies, and determine the template based on the cookie.
I know. For me it might be OK, but consider someone else who wants to use this plugin and has about 3 templates installed that he just copied from somewhere else. This person will have to change the templates in the same way even though he does not care about the html code. That is not very userfriendly. Mostly one wants to install sth. and then just let it work without doing anything else.
> The big con is that you lose style.ini support, but that shouldn't > stop you from using it. I would not want to loose that.
Keep in mind you can turn a style.ini template into one not requiring it fairly easily.
Also, consider the contradiction-- your guests or logged in users can choose which template they want, but they're still locked into whatever default color scheme you've set up for each template... and whatever benefit style.ini had is almost all but lost.