9

It isn't possible to uninstall a disabled plugin; you'll need to first enable the plugin, and then the Uninstall option will be available. The correct way to remove a plugin is actually to first Uninstall it. After uninstalling, you can either run composer remove vendor/plugin-handle from the command line, or select the "Remove" option from the Control ...


6

Although I'm not in favor of the nuclear option in international politics, it works very fine and simply this case. Brad's suggestion of deleting the craft/vendor folder and composer.lock and then running composer update solved the problem immediately. Now I appreciate composer.


5

To delete craft, all you need to do is delete the craft/app folder, so you don't lose all your templates/plugins etc. That said, this won't affect your site url as siteUrl stored in the database. Here are a few options: You would need to go into the database under the table craft_info and then change siteUrl back to localhost or whatever you need it to be. ...


2

You will need to enable it to uninstall it but you can do everything via CLI. First ./craft plugin/enable plugin-handle then ./craft plugin/uninstall plugin-handle then composer remove namespace/package-name. If you really can't enable it as above, you'd need to composer remove namespace/package-name and manually remove any references in your plugins table, ...


2

Settings > Plugins There you will find a pulldown for each plugin with an uninstall option.


2

Thanks for that tip, Lindsey, but here's what happened: I changed calendar37 to calendar37_Occurrences and then all three tables wouldn't uninstall. It turns out that the issue is having a capital letter after the underscore. So it seems like an "undocumented feature" that you can make plugin tables persist after uninstall by including a capital letter ...


1

This is a little bit speculative, so let me know if it turns out to be incorrect... When you use a non-underscored Record name, you're telling Craft that this is the one-and-only, definitive Record. When you use an underscored Record name, you're telling Craft that this Record is one-of-many. I have a vague recollection of similar behavior with Variables or ...


Only top voted, non community-wiki answers of a minimum length are eligible