Problem with Package Management after Upgrade 2.2

Ah yes, there are multiple config files. Didn't think of that. Wouldn't running the setup in upgrade mode have updated those. Should I delete them then re-run the setup in upgrade mode?

I did delete the cache files, cookies and browser cache.

Would any of this cause the package installation to misbehave?

No, upgrade mode doesn't re-write the paths and URL in any of the config files.

I think that the main MODX config files are supposed to be updated when you run Setup, but it doesn't always work and I don't think it will reset things like the filemanager path (which may be used by addons).

If the Manager is not working in general, you may need to edit the config files manually. Some folks have had to go into the System Settings table in PhpMyAdmin and set the compress_js and compress_css settings to 0.

In addition, the packages you install may set paths or store the IDs of specific resources and those would not be updated during Setup. The best bet would be to uninstall and reinstall the extras that are not working.


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/MODx.html [ed. note: BobRay last edited this post 14 years, 8 months ago.]

OK, I checked the path in the config files in both the manager and the connectors folder. Both are correct.

The manager, and all other functions on the site are working correctly except adding new packages. Existing packages that were in the original installation are working just fine.

The only problem I have is that I'm unable to add new packages.

What version did you upgrade from? You may have to edit the modx_workspaces table in PhpMyAdmin . There also might be some leftover System Settings from the older version (if it's old enough).



---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/MODx.html

I ran the upgrade on the install i just set up. So I ran it on the newly set up ver 2.2. Since I had copied this install from another site, I ran the upgrade to reset the config, path , etc. (see my first post)

Hmm . . . I'm about out of ideas. You could try turning off the compress_js and compress_css Settings, but I doubt if it will help.

Since we're grasping at straws here, you might try deleting *all* cookies in the browser in case you missed one and delete all files in the core/cache directory again.

I can't remember if you've checked the path in the modx_workspaces table, but if not, it's worth a try and I'd triple-check core/config/config.inc.php and all the paths in all four config files.

If there is a timezone set in php.ini, you need to set the MODX timezone setting to match (put timezone in the search box in System Settings).

Since you can download the packages, it's unlikely to be a problem with cURL, mod_security, or file/directory permissions.

Is there anything in the error log?

The only other thing I can think of is a file missing or corrupted in the transfer, or an old file that somehow didn't get overwritten when you unzipped things.


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/MODx.html

I know this is an old thread, but it was never resolved and I wanted to let you know that I just had this exact problem, but BobRay resolved it for me. I created a test directory and upgraded from 2.2.16 to 2.3.3. In the meantime, I hardened the installation by changing the core, connectors and manager folder names, and updated the core config files to compensate. The installation went smooth, and everything was working until I tried to update a couple packages. They kept trying to download and install into the original, live directory, and failed in the attempt. I reviewed my paths and they were all correct, until Bob reminded me that there is a "workspaces" table in the database, and sure enough, updating that with the correct path fixed the problem. Why is that even used?

WOW, I hope they find a way in MODx3 to do away with terrible system of updating and multiple connector files. Fortunately, after years of frustrating updates, I've finally got a system down for it - except I still have "gotchas" every now and then.

As of a certain 2.2 version (I'm not sure which one), the workspaces table has a relative path set as {core_path}packages/ - older versions might still have it hardcoded, but for newer installs that should no longer be a problem. The historic reason for that was the potential feature of having multiple workspaces, but I'm not entirely sure what that would be or why that was never implemented.

In 2.3 the number of connectors has been brought back to only the handful that are absolutely necessary: https://github.com/modxcms/revolution/tree/master/connectors (compared to the 200+ that existed previously).