Installing Packages error

Hi,

I'm trying to install the modx updateing tool, or any package for that matter, but i'm getting the following errors:

Console running...
Attempting to install package with signature: upgrademodx-1.5.5-pl
Package found...now preparing to install.
Could not open file for reading: upgrademodx-1.5.5-pl.transport.zip?revolution_version=Revolution-2.3.3-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 upgrademodx-1.5.5-pl.transport.zip to /var/www/vhosts/xxxxxx/httpdocs/corepackages/.
Could not install package with signature: upgrademodx-1.5.5-pl

I have made sure that my cURL is enabled, allow_url_fopen is enabled as is fsockopen.
All the correct folders have write privileges, as does the zip file it self.

I'm not sure what else to do, any advice?

thanks

Some Info:

Modx version: MODX Revolution 2.3.3-pl
PHP version: 5.6.38

Is there anything useful in the MODX error log (under Manage -> Reports on the Top Menu)?

Quote from: BobRay at Oct 01, 2018, 12:08 PM

Is there anything useful in the MODX error log (under Manage -> Reports on the Top Menu)?

Thanks for the swift reply -

I've looked in the logs and can't see anything that is more revealing than the initial message:

[2018-10-01 16:55:03] (ERROR @ /connectors/index.php) Could not open file for reading: upgrademodx-1.5.5-pl.transport.zip?revolution_version=Revolution-2.3.3-pl
[2018-10-01 16:55:03] (ERROR @ /connectors/index.php) MODX could not download the file. You must enable allow_url_fopen, cURL or fsockopen to use remote transport packaging.
[2018-10-01 16:55:03] (ERROR @ /connectors/index.php) Could not transfer package upgrademodx-1.5.5-pl.transport.zip to /var/www/vhosts/xxxxxx/httpdocs/corepackages/.


I'm fairly clueless when it comes to MODX...

The first one suggests that there's a problem with the permissions or ownership of the core/packages directory or its files. Or that you've protected that directory with a Media Source permission setting in MODX.

BTW, you really need to upgrade MODX to 2.4.0, then 2.5.0, then 2.6.0, then the current version using the UpgradeMODX extra, which you may have to install manually by downloading the transport file and putting it in the core/packages directory, then doing "Search Locally for Packages" in Package Manager.

Start Here (click on "Previous Versions"): https://modx.com/download/other-downloads

The version you have has very serious security vulnerabilities and many MODX sites have been hacked lately, and upgrading could solve your problem (or not).




[ed. note: BobRay last edited this post 7 years, 11 months ago.]

Quote from: BobRay at Oct 01, 2018, 05:20 PM

The first one suggests that there's a problem with the permissions or ownership of the core/packages directory or its files. Or that you've protected that directory with a Media Source permission setting in MODX.

BTW, you really need to upgrade MODX to 2.4.0, then 2.5.0, then 2.6.0, then the current version using the UpgradeMODX extra, which you may have to install manually by downloading the transport file and putting it in the core/packages directory, then doing "Search Locally for Packages" in Package Manager.

Start Here (click on "Previous Versions"): https://modx.com/download/other-downloads

The version you have has very serious security vulnerabilities and many MODX sites have been hacked lately, and upgrading could solve your problem (or not).

Thanks Bob,

yeah I’m trying to get it all up-to-date. Strangely, I've followed the instructions to upgrade, run the setup and that’s completed with no errors, but it doesn't seem to upgrade the version. I've started with 2.4.0, the moved to 2.5.0 etc but nothing updates and it sticks to 2.3.3.

I thought using your upgrading package might help it work.

This is the message I get when I run the setup upgrade:

Installation Summary
Core installation was successful. Click next to complete the installation process.
(scroll to bottom)

Toggle Success Messages | Toggle Warnings

Config file successfully written.

Config file permissions successfully updated.

Error updating table for class transport.modTransportProvider
Array
(
[0] => 00000
[1] =>
[2] =>
)

Error updating table for class transport.modTransportProvider
Array
(
[0] => 00000
[1] =>
[2] =>
)

Error updating table for class transport.modTransportProvider
Array
(
[0] => 00000
[1] =>
[2] =>
)

Error updating table for class modCategory
Array
(
[0] => 00000
[1] =>
[2] =>
)

Error updating table for class modCategory
Array
(
[0] => 00000
[1] =>
[2] =>
)

Successfully created table for class modAccessNamespace

Successfully upgraded table for class modAccessResourceGroup
Dropped index `principal_class` on table ``modx15_access_resource_groups``.

Successfully upgraded table for class modAccessResourceGroup
Added new index on `principal_class` for table ``modx15_access_resource_groups``.

Error updating table for class modTemplateVarResourceGroup
Array
(
[0] => 00000
[1] =>
[2] =>
)

Error updating table for class modManagerLog
Array
(
[0] => 00000
[1] =>
[2] =>
)

Successfully converted user profile country names to ISO codes.
0 updated

I'm thinking it might be best to do a fresh install of MODX's latest version and then migrate the site over to it - would this be possible? Can you copy the content across versions of MODX ok? [ed. note: lozauk last edited this post 7 years, 11 months ago.]