Changes between Version 110 and Version 111 of ConfigurationGuidelines


Ignore:
Timestamp:
05/01/14 07:41:03 (8 years ago)
Author:
MattS
Comment:

Trying to explain better the way that modules are deactivated

Legend:

Unmodified
Added
Removed
Modified
  • ConfigurationGuidelines

    v110 v111  
    9696We would like to expose these to a [wiki:BluePrintWebSetup Web Setup], although it's low priority as these are mostly installation-time decisions.
    9797
    98 Disable unnecessary modules, which is currently done in {{{models/000_config.py}}}
     98Disable unnecessary modules, which is currently either done in {{{models/000_config.py}}} or in the template's {{{config.py}}} file. Active modules are stored in settings.modules, which is an instance of !OrderedDict. The key of each item in this !OrderedDict is the name of the module (a string), and each value is an instance of Storage. To disable a module, either comment out the relevant lines of {{{config.py}}} in the template, where the list is populated, or else use the pop method in {{{models/000_config.py}}} to remove the relevant item from settings.modules.
    9999
    100100Can also reorganise the Applications menu completely to better display those relevant to the instance: