• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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