The drush command 'pm-unistall nodeaccess' could not be found. Nodeaccess 8.x-1.0-beta2 2018-Mar-05 Supported, Recommended, InstalledĬHANGELOG.txt LICENSE.txt nodeaccess.install README.txt srcĬonfig nodeaccess.module services.yml trying to get rid of 'Nodeaccess' module, version: 8.x-1.0-beta2. Sorry, but I still do not understand how this is supposed to work.Į.g. Right now it behaves like a broken UI, a buggy form that was accidentally crippled - because giving a user a checkbox and then telling them "this isn't really something you can change" is obnoxious. I suggest we really need to replace the "disabled" checkbox UI with (at least) an explanation of why you can't disable modules, and how you can uninstall them (and what those implications are). Can we make this developer experience less horrible? The big discussion hints that we are expected to edit config files by hand now. This change was made possible because the method for upgrading is now shifted into 'migration' (rather than internal upgrading) and configuration management (rather than module configs in database schema) But things are broken - how can I remove this broken contrib module that now makes the site unusable? that issue is several hundred arguments long, so It's unfair to over-summarize.
* Some upgrades left behind data loss due to things like unexpected dependencies, plugins or hooks being unavailable at key times - when things were disabled. * Because data left behind by a disabled module that is later re-enabled causes integrity issues and cruft. * Because upgrades of some contrib module don't actually work (and can't be made to work) if upgrading when they are disabled. The longer answer is because reasonsĪ huge debate and amount of thought went into this, with strong talk on both sides. Uninstalling a module means removing all traces of it. There is no longer any grey area between a module being on and active vs off and "purged". It turns out this is by design The short answer is - you probably are looking for the "Uninstall" tab found on the "Extend" (Modules) page /admin/modules/uninstall You want to turn off "Comment" because you are not going to use it? Too bad sucker! The checkbox is still there, taunting you with its permanently on status. It's not due to it being required by a dependency or anything, the checkbox is simply locked on, with no explanation of why you can't use it. If you use the Drupal 8 'Extend' page to manage modules, and enable anything, or even just allow the default profile to turn things on for you (the usual case) the module checkboxes are disabled.
0 kommentar(er)
