Manually Removing Packages

Can someone explain the full process for manually removing packages? Often the manager hangs when I try to do this the nice way -- methinks there needs to be more permissions checks at this phase. I can remove the package from core/packages/ but the thing still shows up in the list of packages (in 2.2.5-pl). The modal windows have buttons with no labels. It's kinda a mess in there. How do I nuke my package?

Seems that nuking malformed packages has problems... but if they're created correctly, they delete much more easily...

I've been seeing this on a couple sites, but I thought it was due to moving the site, or in the other site, dependent on the fact that I had re-installed from scratch and then loaded all the old transport.zip files into packages from the db.

What seemed to happen is the package path isn't valid and thus, it can't install, reinstall or remove any package depending on the incorrect path. I got this idea from viewing the log, as it clearly stated it couldn't find the package in the path. I was also getting a cURL error in the log any time I tried to install/uninstall packages, when I know cURL was enabled.

Once the package is removed entirely, a new copy from package management works. Also, transport.zip files work fine but only if all traces of the package are removed from the packages folder prior to upload.

It's been going on long enough that if I find a package that shows no setup information in the first window, it probably won't install. I chalk it up to a bad one and go through the manual removal and reinstall process.

All the packages that I moved from one server to new were like this. Only the ones that I'd previously downloaded or installed were problematic on the rebuilt site, new downloads function properly. I used a copy of the db to rebuild that site.
[ed. note: frogabog last edited this post 13 years, 11 months ago.]