Views & Blocks
- Version: 1.0
- Created: 08/29/2018
- Last Updated: 08/29/2018
- Intended Audience: UCOM/DoIT
Summary
Configuration management procedures for creating and modifying views and blocks in D8
Procedure
UCOM
- Create/modify view or block.
- Determine if it should be available on a single site, or should be made available to all sites on the D8 platform.
- Coordinate with web developers. They will need to know the name of the view or block, and whether it should be made available on all sites, or should only be available on a single site.
DoIT
If the block/view should only be available to a single site
- Go to Configuration > Development > Configuration Synchronization.
- Go to the Ignore tab.
- If config_ignore.settings is not already in the list of ignored configuration files, add it.
- Add the view/block configuration file to the list of ignored configuration files.
- Save.
If the block/view should be available to all sites on the D8 platform
- Run
drush @[siteName].[env] config:status
to ensure that the config export won’t be exporting file changes we don’t want to apply to the entire platform. - Keep any unwanted files listed in the config status from being exported by putting the file names on the Ignore tab under Configuration > Development > Configuration Synchronization.
- Run
drush @[siteName].[env] cex
. - Pull the changes to your local environment using
drush cpull @[siteName].[env] @self
. - Commit the changes to version control.
Keywords
- view
- block
- configuration