Previously the list of modules that users could choose during UI installation was hardcoded in the install steps of social.profile. These are now managed by the Drupal\social\Installer\OptionalModuleManager class that looks for a specific file in modules. As a side-effect of this the number of steps in the installer have been reduced and the step for demo content will only show if demo content is selected.
The Open Social profile itself can define modules not controlled by the profile as optionally installable using the social.installer_options_list.yml file. The installer will use the name of the profile that is being installed in case you have a profile that extends the social profile.
Modules can provide a [modulename].installer_options.yml file with name (required), description (required), weight (optional, default: 0), default (optional, default: false) keys. The weight controls the order of the modules on the configuration form (lower first) and the default key indicates whether the module is checked to be installed by default. The name does not need to be the module name but can be something that is more descriptive to less technical users. The description is not currently used but may be used in the future.
Examples
An example for the social_search_autocomplete module that wants to be displayed at the top of the list and enabled by default can be seen below.
name: Interactive search suggestions
description: Provides real-time search results in the search overlay.
default: true
weight: -100
An example for the social_event_types module that is not enabled by default and doesn't care about it's position can be seen below.
name: Event types
description: Allows events to be organised by event types.
| Attachment | Size |
|---|---|
| The installer's optional module selection screen right before module installation begins. | 289.52 KB |
