• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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