Check the permissions and ownership of your core/packages directory.
I imagine that you tried logging out, deleting all files in the core/cache directory, and clearing your browser cache and cookies. I've had a similar problems resulting from an old cookie.
If that doesn't do it, you could try downloading the transport.zip file, putting it in the core/packages directory and selecting Add Package and Search Locally for Packages in Package Manager.
You might also have to remove the old package (by right-clicking on it in PM and selecting Remove Package) first.
[ed. note: BobRay last edited this post 14 years, 8 months ago.]
Bob
Tried all of the above, no change.
So I tried to remove one of the packages, Wayfinder, completely. The Remove button didn't work, so I removed it from the core/packages directory and the core/cache. I also removed any cookies from the site from my computer, cleared the cache on the site and in my browser, logged off and back on.
Wayfinder is still displayed in the package manager and still is functioning on the site.
Since this is a test site just so I can see how all this works, I'm not sure this is worth troubleshooting any further. I think I'm going to start with new site and see how it goes.
I appreciate the help. Definitely learned more about this. Thank you!
Sorry that didn't work. Since you're starting over, it doesn't matter, but for future reference you should should avoid physically removing files for installed packages if possible.
The references for the package will still be in the DB (which is why they show in PM) but will no longer be synchronized with what's in core/packages. If you tried to install the same package later, MODX could be very confused.
Usually, if you right-click on the package and select "Remove Package" and check "Force Package Removal" it will work.
Bob
Yep, I agree, removing those files is probably not a good idea. I only tried that because the force remove seemed to have no effect. It just didn't remove them.
I imagine there was some other problem with my setup somewhere.
I appreciate the help. Thank you!
I'm still struggling with these package installations.
A little background. I've completed a fresh install of modx 2.2 in a folder on my shared hosted environment. I've installed some of the basic packages such as Wayfinder, Getresources etc. All indications are the site is working normally. The installation proceeded with out any errors or warning. The package installations worked just fine.
Now I'd like to use this installation as a the basis for a new site.
Zipped up the folders and files from the install above including the setup folder, but excluding the config.core.php in the root folder.
Exported the DB
In a new folder on the same server
Unzipped the folders
Run Setup as a new installation
Import the DB from the other site
Run Setup as an upgrade
Deleted the files in the core.cache directory
Deleted any cookies related to modx or the host server
Cleared the browser cache
Now, when I login to modx, the new site is working normally, the previously installed packages are there and working correctly.
Here's the problem. If I try to install another new package, I can find and download a package, the zip file appears in the folder with all the other packages and it is listed along with the other packages in the manager ready for install. When I attempt to install the new package it takes to an empty page where the license and other information would normally appear, but there is no data (see attachment). If I continue with the install I get the error messages show in the post previous to this.
Since I was able to install packages on the original installation and I'm using the same server, just a different folder, I assume the server settings (You must enable allow_url_fopen, etc.) are not an issue. Permissions on core/packages is set at 755.
I'd appreciate any help with this. I'm happy to provide a login to the site and/or my server if someone is willing to look around.
Thank you!
Maybe your config file is 'confused'
It is here: core/config/config.inc.php
take a look at it, there are a bunch of paths defined there maybe one didn't make the transition
-
☆ A M B ☆
- 24,524 Posts
Especially tricky are the absolute URL paths, such as /assets/ which have to be changed to /subdir/assets/
There are also three config.core.php files that have to be edited. One in the site's root, one in /manager, one in /connectors.
And don't forget to delete all the folders in core/cache to force a rebuild of the cache.
I've also had problems with stale cookies; clear your browser cache and all cookies for the domain.