Could not install package with signature

Seems I misinterpreted some code that got ported recently. Sorry for the disruption guys. This should now be fixed. Please let me know if you experience otherwise.

Same results for FormItLog.
I even did a force removal and manually deleted the folder under packages and then downloaded it again and attempted an install:

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

And my abject apologies to all of the extra developers!

However, Vapor is still not correct. One way you can immediately tell that the extracted package's directory name is wrong is that there won't be the usual three documents available.

Quote from: sottwell at Jan 22, 2014, 12:47 PM

However, Vapor is still not correct. One way you can immediately tell that the extracted package's directory name is wrong is that there won't be the usual three documents available.

That's the case with FormItLog as well.

I've made some more adjustments to resolve the version/release issues. FormItLog installs fine now.

Vapor packages likely will not work, and are not intended for use in Package Management.

Yes. After I removed it completely it worked.
Also the updates that didn't exist but had the update button are now not highlighting an update.
And the updates that do exist updated fine.

Not being able to use Vapor in package management will be unfortunate. It was a much nicer method than manually moving a site to another server and changing configs, etc. [ed. note: rx2 last edited this post 12 years, 8 months ago.]

Vapor works just fine if you rename the unzipped directory to match the transport zip file.

Quote from: rx2 at Jan 22, 2014, 04:26 PM

Yes. After I removed it completely it worked.
Also the updates that didn't exist but had the update button are now not highlighting an update.
And the updates that do exist updated fine.

Not being able to use Vapor in package management will be unfortunate. It was a much nicer method than manually moving a site to another server and changing configs, etc.

Thanks for your patience as we attempt to improve the backend services that power MODX Package Management.

Also, take a look at Teleport if you liked Vapor. Vapor was a tiny functional subset of Teleport; anything Vapor could do, Teleport can do, plus a whole lot more.