![]() ![]() ![]() ![]() ![]() In any case, a ModuleHandler method should never be able to call or load any uninstalled module's code. So at this point we only need to separate out uninstalled/never installed modules (forthcoming paradigm), but may separate out disabled modules as well (current paradigm). Either the disabled status gets removed altogether and replaced by some convenient, or at least some code continues to run. We don't know yet the outcome of #1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed, but if it doesn't get postponed to D9, one thing is clear: there won't be a thing such as completely disabled modules anymore. Yes, I agree that ModuleHandler should only act on our (enabled) $moduleList, making sure that code of uninstalled modules is clearly separated and never called here. I wanted to avoid that, because I think it's a very powerful feature that ModuleHandler relies solely on the module list. I went the extra mile of splitting the 'loader' part into a dedicated interface, because not doing that would have meant tainting the ModuleHandler with a SystemListing object. Is this actually about module_load_install() or about module_install()? Support from Acquia helps fund testing for Drupal Comments PHP 7 & MySQL 5.5 Unable to generate test groupsĢ010380-9-module-handler-load-install.patchĢ010380-8-module-handler-load-install-do-not-test.patchĢ010380-1-module-handler-load-install.patch.PHP 8.0 & MySQL 5.7 Patch Failed to Apply. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |