Package Management has stopped working.

I’m encountering something similair with a fresh install of 2.0.8-pl,
but only with some packages.

I’ve made sure the service URLs are correct, and I’ve cleared the cache.
However, when I try and install some packages, I get the same error message.

Other packages, however, seem fine to install.

Quote from: robrob at Mar 25, 2011, 12:46 AM

I’m encountering something similair with a fresh install of 2.0.8-pl,
but only with some packages.

I’ve made sure the service URLs are correct, and I’ve cleared the cache.
However, when I try and install some packages, I get the same error message.

Other packages, however, seem fine to install.

Any chance you could specify which packages you are having problems with? Sounds very, transient...

Any chance you could specify which packages you are having problems with? Sounds very, transient...

I can’t install tagLister, wayfinder, tinyMCE, formit.

Additionally, in the modal window "package retriever", in the package browser, underneath the search input, I also see the message "an error occured while connecting to the Provider. Modx recieved a blank response from the provider.."

I recently did a fresh install of 2.0.8pl and didn’t changed the provider URL. This setup works without any issues. When editing to modx.com URL errors occur "provider not found", etc etc.

Quote from: robrob at Mar 27, 2011, 03:16 AM

Any chance you could specify which packages you are having problems with? Sounds very, transient...

I can’t install tagLister, wayfinder, tinyMCE, formit.

Additionally, in the modal window "package retriever", in the package browser, underneath the search input, I also see the message "an error occured while connecting to the Provider. Modx recieved a blank response from the provider.."

I have exactly the same problem, but for all packages. At first when I click on ’Download Extras’ I see three folders (Extras, Frontend Templates and Backend Templates) but when I expand one of them I get the "an error occured while connecting to the Provider. Modx recieved a blank response from the provider.." error.

I have this problem with a fresh MODx Revolution 2.0.8-pl install, and also with a MODx Revolution 2.0.7-pl installation. It doesn’t matter if I change the provider url from modxcms.com to modx.com, the connection problem stays...

My error log says:
[2011-03-28 11:26:59] (ERROR @ /connectors/workspace/packages-rest.php) Could not connect to provider at: http://rest.modx.com/extras/

Do you have cURL enabled?

Quote from: splittingred at Mar 28, 2011, 07:34 AM

Do you have cURL enabled?

In my case, I definately have cURL installed on the server.
I’m running a test server with a few installations of modx. Some instances are older versions.

The other, older instances (I’m playing with 2.04 now) have no such problems finding the same packages or servers.

Hello,

we have the same problems and yes - cURL is missing on server. The problem is we can't install cURL as we are using a Debian machine with the latest Lenny stable and because of the MySQL 5.0.51a "problem" we are now using the dot deb MySQL and php packages.

But using the dot deb packages prevents installation of cURL!

What now?

Greetings,
Martin

Quote from: gadgetto at Sep 08, 2011, 02:12 PM

Hello,
we have the same problems and yes - cURL is missing on server. The problem is we can't install cURL as we are using a Debian machine with the latest Lenny stable and because of the MySQL 5.0.51a "problem" we are now using the dot deb MySQL and php packages.

But using the dot deb packages prevents installation of cURL!

What now?

You'll have to find a way to get cURL installed OR you can download packages from the website and upload them to your packages directory manually.

To install package manually, put the transport.zip file in the core/packages directory. You can transfer as many packages as you like before doing the next step.

In Package Manager, select "Add Package" and then "Search Locally for Packages."

The package(s) should then appear in the PM grid where you can install them normally. When you do it this way, there's no automatic notification of updates -- you have to check periodically to see if an update has been released.