• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue How to define Standard Skin?

Martin.B

Plesk Certified Professional
Plesk Certified Professional
Hi, is there a way to define a standard skin?

Since a few versions, everytime our Obsidian Installations do a nightly Microupdate, the branding theme gets reset to the "default" skin. We always have to check all of our systems to manually change the skin back to our company branding (plesk bin branding_theme --set -name <ourname>), which is a hassle. Is there a way to tell Plesk to use our Skin as default and reset it to this one?
 
The meta.xml file is okay.
The problem exists since upgrading to 18.0.23 I guess. Maybe it has something to do with this entry from the changelog:

"Updating a Plesk instance using a custom skin to Plesk Obsidian no longer results in a broken skin. Instead, the custom skin is replaced with the default Obsidian skin. (PPP-45324)"

?
 
Back
Top