Hi I’m using MODx Revolution 2.0.0-beta-2 on FireFox 3.0.12
Installation ran smoothly and I log in to the back-end perfectly, the database is all set and I’ve cleared all the configuration details that didn’t check out on the home page in the manager.
I have a small problem when I try to download and install packages.
Here’s the summary of what I do and get:
I go to : System> Package Management> Add New Package> Select Provider (modxcms.com)> (I make a single selection from the tree and press finish).
After that I get a download loading bar but once it’s finished nothing happens, the Package Retriever window remains open so I close it and refresh the list to see if it appears (I hold my breath)... and nothing.
Same thing happens if I try: System> Package Management> Download Extras
Am I doing something wrong? I’m sure the installation went perfect and also sure that I uploaded everything to the server since I was very meticulous and uploaded almost every file manually.
Here’s my server info:
Apache version---> 2.2.9 (Unix)
PHP version---> 5.2.6
MySQL version---> 5.0.81-community
Architecture---> i686
Operating system---> Linux
Kernel version---> 2.6.18-028stab060.8-ent
And again I’m using MODx Revolution 2.0.0-beta-2 on FireFox 3.0.12
Any help will be greatly appreciated.
Thanks.
PS: please forgive this humble new user if I’ve posted in the wrong place.
-
☆ A M B ☆
- 872 Posts
I’ve got the exact same issue. I downloaded the package manually and put them in the install directory.
I have a - almost - similar problem - in beta2 and beta3:
I can see the packages, and can "check" them - and after I hit "Finish" it retur the error: "Please select at least one package version to download".
The error(s) are the same in FireFox 3.5.1 and Google Chrome 2.0.172.37 (Can’t test it in IE8 because of a JS error (in IE’s opinion) which stops the login process).
There are no problems with the add locally packages function.
The error log in beta3:
[2009-07-24 21:12:41] (ERROR @ /home/www/subdomain.domain.tld/core/model/modx/processors/workspace/providers/download.php : 53) PHP warning: Invalid argument supplied for foreach()
Server info:
Mysql version: 5.0.32-Debian_7etch8-log
PDO Driver for MySQL, client library version: 5.0.81
PHP Version: 5.2.9-0.dotdeb.1
Memory size: 128 mb.
Apache: 2.2.3
Suhosin Patch 0.9.7 and Zend Scripting Language Engine installed.
- A small step for mankind, so why not take two...
Working with web production, graphic design/workflow, photo and education - but are trying to get a life in between!
Hi, I’ve completly removed the setup folder from my server, could that be my problem?
I know this may be a bit obvious but is your /core/packages directory writeable by your webserver?
Use MODx, or the cat gets it!
Quote from: shamblett at Jul 24, 2009, 03:49 PM
I know this may be a bit obvious but is your /core/packages directory writeable by your webserver?
Just tested it:
/core = 755
/core/packages = 755
- A small step for mankind, so why not take two...
Working with web production, graphic design/workflow, photo and education - but are trying to get a life in between!
Quote from: betoranaldi at Jul 24, 2009, 03:48 PM
Quote from: Henrik at Jul 24, 2009, 02:20 PM
I have a - almost - similar problem - in beta2 and beta3:
I can see the packages, and can "check" them - and after I hit "Finish" it retur the error: "Please select at least one package version to download".
The error(s) are the same in FireFox 3.5.1 and Google Chrome 2.0.172.37 (Can’t test it in IE8 because of a JS error (in IE’s opinion) which stops the login process).
There are no problems with the add locally packages function.
I’m having this same problem. also when I try to update an existing package, I get a package_download_err error
Where can I manually download packages? and is there anything I can do to troubleshoot these error?
You can get the packages here:
http://modxcms.com/extras/?versionFilter=revolution
- A small step for mankind, so why not take two...
Working with web production, graphic design/workflow, photo and education - but are trying to get a life in between!
This was due to a bug in our Provider, related to the beta-3 security fix. Apologies for not catching this sooner; thanks to all for notifying us of it.
It should be working as expected now; please let us know if it’s not.
Also, we strongly recommend all beta-2 and beta-1 users upgrade immediately to beta-3 because of a Security Vulnerability in the prior betas.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com