• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Forwarded to devs Plesk branding_theme utility does overwrite default skin

vaelu

Basic Pleskian
Username: webdiz

TITLE

Plesk branding_theme utility does overwrite default skin

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.32, Debian 9.13

PROBLEM DESCRIPTION

We have changed our Plesk theme with a custom one like described here: Using Custom Themes

We have uploaded the skin ZIP to /tmp/ and added the skin to plesk with plesk bin branding_theme -i -vendor admin -source '/tmp/customskin.zip'. The skin was succesfully added.

Now we wanted to change the whole structure of it and want to download the default skin from Plesk again. The default skin is available, as when we type plesk bin branding_theme -l there shows up "default" and our "customskin".

But when we try to export the default skin now with plesk bin branding_theme -p -name default -destination '/tmp/default.zip', it looks like the default skin was overwritten by our custom skin - it's exactly the same like "customskin".

STEPS TO REPRODUCE

  1. Export the default skin
  2. Change something in it and install it to Plesk
  3. Try to export the default skin

ACTUAL RESULT

Instead of getting the Plesk default skin you will get your customized one

EXPECTED RESULT

Getting the default Plesk skin

ANY ADDITIONAL INFORMATION

Can you please provide us with a download link for the original default Plesk skin since we need it, thanks.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for the report!
Confirmed bug: PPPM-12588
There is the ability to corrupt default skin. You can't rollback to default skin.

Workaround:
Download package: http://autoinstall.plesk.com/PSA_18....0-v.debian.9+p18.0.32.0+t201204.1424_all.deb
Unpack it and get original skin files from: ./opt/psa/admin/cp/public/theme/
Don't forget to put meta.xml and install to plesk.

wget http://autoinstall.plesk.com/PSA_18....0-v.debian.9+p18.0.32.0+t201204.1424_all.deb
dpkg-deb -R plesk-control-panel_18.0-v.debian.9+p18.0.32.0+t201204.1424_all.deb tmp
echo '<?xml version="1.0" encoding="UTF-8"?>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
echo '<meta>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
echo ' <name>default</name>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
echo ' <description></description>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
echo ' <version>3.0.0</version>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
echo ' <vendor>Parallels Inc.</vendor>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
echo '</meta>' >> tmp/opt/psa/admin/cp/public/theme/meta.xml
cd tmp/opt/psa/admin/cp/public/theme
zip -r ~/default.zip ./*
plesk bin branding_theme -i -vendor admin -source ~/default.zip
 
Back
Top