• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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