Could not install package with signature

I continue to get this error message when installing packages. "Could not install package with signature"

v2.2.10

I have cleared cash, ran setup, and removed package and redownloaded with no luck. Any ideas would be helpful.

Are you sure that PHP has zip enabled?

I just started getting this error on MODX Cloud, both for packages that are already installed where the update button is active even though the version you're updating to is the same version you already have. I have it happen for:

Canonical
getURLParam
Switch

And I was unable to install Vapor 1.1.0. At all, though I was able to download it from the repository.

I have 5 pages of packages, all of which installed on the same server before.
I'm getting this happening on a non MODX Cloud server as well.

Vapor is not an installable package. In fact, while it can be invoked from the browser, it is best run from a command line via SSH on a remote server.

Ah, begging your pardon. I see that it is (supposedly). Its problem being that it is vapor.1.1.0-beta, while the Package Manager is looking for vapor-1.1.0-pl. Rename the unzipped directory in your core/components directory and it installs fine. [ed. note: sottwell last edited this post 10 years, 3 months ago.]

Attempting to install package with signature: redirectusergroups-1.0.0-pl1
Package found...now preparing to install.
Could not find package manifest at /home2/mistaway/public_html/mistawaydealerolc.com/core/packages/redirectusergroups-1.0.0-pl1/manifest.php
Could not unpack package /home2/mistaway/public_html/mistawaydealerolc.com/core/packages/redirectusergroups-1.0.0-pl1.transport.zip to /home2/mistaway/public_html/mistawaydealerolc.com/core/packages/. SIG: redirectusergroups-1.0.0-pl1
Could not install package with signature: redirectusergroups-1.0.0-pl1

This may be related. I downloaded this tonight and got this message. I installed a lot of packages just fine last week. I am running Rev 2.2.10-pl

Did you check the unzipped package directory's name? It sounds like the same problem - the zip file's name is redirectusergroups-1.0.0-pl1, but it unzips a directory with a different name. Just renaming the unzipped directory to be redirectusergroups-1.0.0-pl1 may solve the problem.

Yes, that's the problem. When installing, it unzips into a directory named redirectusergroups-1.0.0-pl. Rename the directory to redirectusergroups-1.0.0-pl1 and it installs fine.

Come on, developers, aren't you testing your packages before you submit them for distribution? [ed. note: sottwell last edited this post 10 years, 3 months ago.]

Ive got the same issue as rx2

im trying to install getReqParam and getUrlParam but everytime i try to install them i get the following:

Attempting to install package with signature: getreqparam-1.0.0-rc1
Package found...now preparing to install.
Could not open file for reading: getreqparam-1.0.0-rc1.transport.zip?revolution_version=Revolution-2.2.10-pl
MODX could not download the file. You must enable allow_url_fopen, cURL or fsockopen to use remote transport packaging.
Could not transfer package getreqparam-1.0.0-rc1.transport.zip to /var/www/vhosts/site.com/httpdocs/core/packages/.
Could not install package with signature: getreqparam-1.0.0-rc1

Now all of the other packages have installed without issue its just these two.

I've tried renaming the folder to the same name as the zip(minus the .transport bit) but still having the same issue.

Edit: renaming the getUrlParam folder worked and installed - just getReqParam now

It starts to happen to all the packages as well.
Something has changed on the repository system.
I also got problem for UltimateParent.
This might shed a light: http://forums.modx.com/thread/88704/transport-039-s-builder-awkward-pkg-name-vs-pkg-name-lower#dis-post-487930

Ive just tried UltimateParent and I too have the issue.

Anyone know where I can get getReqParam to install that works as I really really need it LOL

Quote from: sottwell at Jan 22, 2014, 04:39 AM

Did you check the unzipped package directory's name? It sounds like the same problem - the zip file's name is redirectusergroups-1.0.0-pl1, but it unzips a directory with a different name. Just renaming the unzipped directory to be redirectusergroups-1.0.0-pl1 may solve the problem.

Yes, that's the problem. When installing, it unzips into a directory named redirectusergroups-1.0.0-pl. Rename the directory to redirectusergroups-1.0.0-pl1 and it installs fine.

Come on, developers, aren't you testing your packages before you submit them for distribution?

Did this for Canonical. I renamed the folder from:

canonical-1.0-beta1

to

canonical-1.0.0-beta1

I have to Canonical transport packages:

canonical-1.0-beta1.transport.zip

and

canonical-1.0.0-beta1.transport.zip

Renaming the folder did not work.

For FormItLog

Now FormItLog is giving me this error and transport package and the folder have the same name. This time it completely uninstalled the package when I clicked the Update button.

Transport Package Name: formitlog-0.0.4-beta.transport.zip
Folder Name: formitlog-0.0.4-beta

So now I can't even install it after Update uninstalled it. Get this error during attempted installation:

Attempting to install package with signature: formitlog-0.0.4-beta1
Package found...now preparing to install.
Could not find package manifest at /home/gyrosgym/public_html/core/packages/formitlog-0.0.4-beta1/manifest.php
Could not unpack package /home/gyrosgym/public_html/core/packages/formitlog-0.0.4-beta1.transport.zip to /home/gyrosgym/public_html/core/packages/. SIG: formitlog-0.0.4-beta1
Could not install package with signature: formitlog-0.0.4-beta1

For getUrlParam

Transport Package Name: geturlparam-1.0-beta1.transport.zip
Folder Name: geturlparam-1.0-beta1

I won't bother trying to update it just in case I lose it. The thing is there really isn't an update. The last release was Oct 29, 2010.

For MIGX

I've never seen MIGX's update button show so I'm not going to touch this. But there was a new version released (2.6). I will try it on a MODX cloud and report back (I will back up the site of course).

For Switch

Transport Package Name: switch-1.0-beta1.transport.zip
Folder Name: switch-1.0-beta1

Showing the Update button. Last actual release was Mar 31, 2011.

For SimpleSearch

Showing the update button and an update does exist but I'm not going to try it on a live server.