How to suppress the "Virtualmin 5 comes with a brand new HTML 5 theme! Would you like to try it now?" message

This message only appears for the root user though - so domain owners won't even see it. And if they don't want to switch, they can just click the "Don't Ask Me Again" button.

We provide root access to the end users, so this has already started to be a problem for us. "Gentle" for individual users, but not hosting vendors which manage hundreds of customized Virtualmin servers. Expecting all end users to click on "Don't Ask Me Again" is simply not realistic, because people already started to click on that very much inviting theme and then send us lot's of confused messages about terminology on the interface. We would like to suppress that notification and I do hope you can give us such an option. I don't believe it should be a big problem for you to give us a possibility to suppress it.

I do strongly believe Webmin/Virtualmin should have an option to either display or not that kind of messages (regardless of their importance) and if negative option is selected then all future modifications to the system should respect it. It would just make lives of hosting vendors much easier. You simply can not understand how it is frustrating to deal with this kind of imposed options on hundreds of servers.

Also, note that it's possible to switch back to the Virtualmin Framed Theme using the instructions here:

We know that, but again it is not an option. We would like to SUPPRESS this notice until all the issues for the new theme are polished, so that end-users never see any ambiguity.

I ask *min developers to please respect the fact lot's of hosting vendors use your products.

There are few hardcoded lines and I will fit it in the next release. (those lines are not VM related)

Дорогой Илья,

Вот пока все эти проблемы не будут решены навязывать новый интерфейс конечным пользователям неприемлемо.

From my point of view it's important to move forward and change sometime can be a bit painful. I am opened to any rational suggestions. Anything is doable and possible for conversion/transmission.

Right, but those kind of changes should always be done on dev branches between developers and tested very well before imposing them to the end-users. And then when you or *-min devs elaborate on this kind of changes for some reason they never put themselves in shoes of hosting vendors, which always try to avoid unnecessary spike of surprised end-user requests. Using cutting-edge technologies is cool for individual users, but definitely not for hosting vendors.

:) I am not imposing anything on anybody. There are no hardcoded strings that are Virtualmin related. The rest will be fixed in days.

It was not your fault personally, but *-min developers as a team. It was really not wise decision to roll this out to the end-users in such an imposing way.

The theme was test thoroughly. Few many hundred bugs were fixed and dozens of releases made before the team decided to make it default in Virtualmin. It's all about we look at the things. The more people use it the better the whole project goes (better for Virtualmin, better for the theme and in the end better for all of us).

In case we're talking about system administrators, from my point of view, quite advanced people in technology, I would expect them to be able easily change back to the previous theme, if they tried and didn't like Authentic Theme. What's more, they can always comment to GitHub or issue tracker with their ideas and what is missing for them. I would like to hear what they say on your behalf and most importantly why they don't like trying new theme and switching back, which only takes less than 30 seconds?

You can not imagine how much I agree with everything said, however please try to understand that end-users are not necessarily system administrators or tech-savvy developers. As a hosting vendor we have to provide root access to our customers, very often just regular account owners without any technical background. And it turns to absolute disaster to us, hosting vendors, when there lot's of such customers who just accept that imposing new theme button and then start complaining about all the confusion they find themselves in.

Believe me - we love the new theme, but as a hosting vendor we need more time to polish all the interface nuances and then preliminarily inform our customer base, write documentation and then only switch everybody to the new theme.

Once again - put yourself in shoes of a hosting vendor and you will understand you never want to put your customers to unexpected situations like this.

Again we are still waiting till Jamie gives us clear instruction on how to suppress that notification on all our Virtualmin servers. Jamie, time is precious in this kind of situations, you have to understand as a creator of Virtualmin. Please do not make us wait any longer or we will have to seriously consider to switching to alternative control panels.

Yeah, adding that theme_switch_authentic-theme=1 line to /etc/webmin/virtual-server/config will prevent this message from appearing.

Thank you very much, guys!

We do love the new theme and will switch to it very soon. We just need to address some minor issues that are being discussed here in the issue queue.

Another related question is can we explicitly set the theme in /etc/webmin/virtual-server/config file?

I understand you'd like to give freedom of choice to the end-users, however for us as a hosting vendors managing hundred of Virtualmin servers it is best to standardize our workflow and procedures, so hard-setting a specific theme would save us from lot's of troubles. For example, when we figure out how to deal with currently discussed Authentic Theme issues, we would like to set it by default on all our servers seamlessly to our end-users.

I see the webmin_theme=* setting in that file and wonder how it works as changing it to webmin_theme=authentic-theme doesn't have any effect.

Further troubleshooting my last question I've figured out I needed to set theme=authentic-theme, however unfortunately despite new theme loads all the css are gone as shown in the attached screenshot. Restarting webmin doesn't help.