Current process after one for example has enabled say devel and devel_generate:
- Go to
/admin/modules - Uncheck "Devel Generate" ("Devel" is locked)
- Hit "Save configuration" -> page refreshes, now "Devel" is unlocked
- Uncheck "Devel"
- Hit "Save configuration" -> page refreshes, both "Devel Generate" and "Devel" are disabled
- Go to
/admin/modules/uninstall - Check "Devel Generate" ("Devel" is locked)
- Hit "Uninstall" -> you get redirected to the confirmation page
- Hit "Uninstall" again -> you get redirected back to
/admin/modules/uninstall, now "Devel" is unlocked - Check "Devel"
- Hit "Uninstall" -> you get redirected to the confirmation page
- Hit "Uninstall" again -> you get redirected back to
/admin/modules/uninstall
OMG, finally!!! ...and this is only with one level of dependency. Imagine if you had a devel_generate_extras module installed that depended on devel_generate and you wanted to disable devel. That would make devel_generate be locked until devel_generate_extras was disabled/uninstalled and then devel would still be locked until devel_generate was disabled/uninstalled. O-M-G!!!
How I envision this to work ideally:
- Go to
/admin/modules-> "Devel" is not locked - Uncheck "Devel" -> dialog pops up explaining that this module is required by "Devel Generate" (and any other modules down the chain) and that means that these will need to be disabled too.
- The dialog also offers a "Also uninstall these modules after disabling them" checkbox that is unchecked by default
- Confirm -> dialog closes and there are indicators (red status text, asterisks, what-have-you) next to all modules queued for disabling.
- Hit "Save configuration" -> progress bar shows the progress of disabling and uninstalling all queued modules. -> you get redirected to
/admin/modules/uninstallthat has a report of which modules were disabled and which were uninstalled, giving you the option to uninstall any that are just disabled.
Compare 5 steps (no matter the complexity of dependencies) vs. at least 12 steps with one level of dependencies. Now, that's something I'd like so see fixed in the next minor release.
Recent comments
Sorry - it is the field_group module. However, last night I switched off proxying to the site and proved to Cloudflare Support that it was NOT a Backdrop issue. After a thorough...
Cloudflare specific advice needed [SOLVED]
@ian I am getting lost what module are you using that is version 1.x-1.6.0 and 1.x-1.7.0 ?
Cloudflare specific advice needed [SOLVED]
I'm also now getting a 403 when trying to access admin/reports/updates - it seems to be Backdrop generated but there is nothing in the Recent Log messages other than my login as admin...
Cloudflare specific advice needed [SOLVED]