Using Package Management in MODx Revolution 2.0.0-beta-2

Quote from: splittingred at Jul 24, 2009, 06:23 PM

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.

I’m sorry - but the problem are still the same in beta3. (Deleted beta2).
A long shot: Can it have anything to do with that my installation are on a real subdomain?

-> Had just tried and installed beta3 from SVN (Revision 5537) directly on the same domain, but this time on the first level: With the same result.

It’s working for me now, thanks!

Thanks for the tip on the upgrade thing.

I have a question and I apologise in advance if it’s too dumb... how do I upgrade fron beta2 to beta3? do I have to download and re-install?

Because in that case I’d much rather just manually upload the packages to the core>packages folder.

I hope there’s an easier way like a "Check for Upgrades" button and I’ve just failed to find it.

Thanks.-

Quote from: upiorz at Jul 24, 2009, 08:39 PM

I have a question and I apologise in advance if it’s too dumb... how do I upgrade fron beta2 to beta3? do I have to download and re-install?

Because in that case I’d much rather just manually upload the packages to the core>packages folder.

I hope there’s an easier way like a "Check for Upgrades" button and I’ve just failed to find it.

Though most of the installation is upgradable from a transport package, you would still need to first update the core/ directory itself somehow. One way we do this is by maintaining the core/ directory from SVN (we actually use a shared core/ that is located outside the webroot for security reasons). Then all we need to do is upload a new transport package, export the setup directory where appropriate, make sure all the files in the webroot are writable by the PHP process for the duration of the upgrade, and run setup.

We’ll be looking into ways to do upgrades on the core itself over the wire, but I’m not sure there will ever be a practical or secure way to do that. If you have ideas though, feel free to let us know...