Problem/Motivation

A common component of a features set is a "site" feature, which collects configuration needed for the site but not specific to focused use cases. Configuration assigned to such a feature might include sitewide menus and blocks, shortcut sets, and text formats.

Proposed resolution

  • Create a new 'site' assignment plugin.
  • Add a configuration form to select the configuration types that should be assigned to it.
  • Give it a relatively high default weight, allowing other assignment plugins to run first.
  • By default, assign the following:
    • block (Block)
    • block_content_type (Custom block type)
    • contact_form (Contact form)
    • menu (Menu)
    • search_page (Search page)
    • shortcut_set (Shortcut set)
    • editor (Text editor)
    • filter_format (Text format)
    • tour (Tour)
    • view (View)

Remaining tasks

Comments

nedjo created an issue. See original summary.

nedjo’s picture

Assigned: Unassigned » nedjo
nedjo’s picture

Alternately, this configuration could go into the 'profile' assignment plugin.

  • nedjo committed 821b074 on 8.x-3.x
    Issue #2579741 by nedjo: generalize core assignment method for assigning...

  • nedjo committed 66e33e0 on 8.x-3.x
    Issue #2579741 by nedjo: New 'site' assignment plugin
    
nedjo’s picture

Status: Active » Fixed

As a start, I added a subset of the configuration types listed in the summary. Fine tuning can be done in follow-up issues.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.