These functions after #1608842: Replace list of bootstrap modules, enabled modules, enabled themes, and default theme with config rebuild nothing, they need to renamed all_data , the system_list_reset be removed and called separately when needed. When needed and not all the time when all you want is read data.

Comments

chx’s picture

chx CreditAttribution: chx commented

The container has the module list so as a first step, remove the module parts from system_list. Both the module_enabled and the file names can be removed. Two, pivot ModuleInfo or add a new similar class so that it returns the info for a single module and then make sure all access to ->info goes through that functionality -- run hook_system_info_alter on cache miss. Now you do not need the system_rebuild_module_data function any more.

For theme, #1833590: Move the module provided theme to something not-hook and fast to detect needs to be resolved first and then in a very similar fashion, have something that caches the parsed and altered info file. I readily presume that the same caching facility as above would be usable.

dlu’s picture

dlu CreditAttribution: dlu commented
Component: base system » system.module

Moved to system.module per #2050763-16: Refine "base system" component (notes on refactoring of "base system" category here: https://docs.google.com/a/acquia.com/spreadsheet/ccc?key=0AusehVccVSq2dF...).

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett commented
Component: system.module » extension system
Priority: Major » Normal
Issue summary: View changes

Enough work has been done on these that I don't think it's major.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner as a volunteer and at Chapter Three commented
Status: Active » Closed (duplicate)

#2208429: Extension System, Part III: ExtensionList, ModuleExtensionList and ProfileExtensionList will resolve that.