• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Error: The uploaded file is not a valid Plesk skin package.

S

sem101

Guest
To test -- I download a default Skin, I open the XML and edit 1 node of text (ex: Date), I repackage and Archive it as a Zip or Tar or Tar.gz, I try to upload Skin archive to test...

Error: The uploaded file is not a valid Plesk skin package.
 
I have make a couple of tests and it seems this feature works perfectly. Here are results of my investigation.

First of all, I downloaded 'Aqua' skin from Plesk CP. After that un-packed it on the server and corrected couple of fields:

<VERSION>1.0.1</VERSION> - changed
<DATE>2007-03-22</DATE> - changed

After that packed this info .tgz archive and tried to upload but failed with the same error. As I figured out further I just forgot to use '-z' option during packaging. So correct command was:

# tar -czf Aqua1.tgz *

Here I got package Aqua1.tgz. When I tried to upload it I got next message:

Error: The skin 'Aqua' already exists

So I had to change also following fields in info.xml file:

<NAME>
<LOCALESTRING language="en">Aqua1</LOCALESTRING>
</NAME>
<DESCRIPTION>
<LOCALESTRING language="en">Aqua1</LOCALESTRING>
</DESCRIPTION>
<KEYWORDS>
<LOCALESTRING language="en">Aqua1</LOCALESTRING>

Then I re-packed the package and was upload to upload it successfully.

Checked me changes and can see that all information have been saved correctly.

Hope this information helps.
 
Thank you, I will continue to try again. But I did exactly what you did and still received the error. I'll post back here if it persists.
 
Back
Top