The Elastic Social extensions have been disabled by default in the Blueprint. This means that after switching to the SQL Persistence for Projects and other editorial features (see Section 4.5.3, “Migration to SQL Persistence” in Operations Basics for details), the Blueprint by default does not connect to a MongoDB.

Following extensions have been disabled: es, lc-es. To enable them in your Blueprint, follow the instructions in Section 4.2.1.2, “Enabling the Elastic Social Extension” in Blueprint Developer Manual .

The es-controlroom extension has been removed to avoid confusion as it was no Elastic Social Extension. Its functionality has been incorporated into other Blueprint modules.

The brick-elastic-social brick in the Frontend Workspace has been left untouched and is still used in the example themes.

The Elastic Social extension contains two content types: ESDynamicList and CMMail. Instances and references in the example content outside of Elastic Social extensions have been removed. If you, for some reason, have instances of these content types without actually using Elastic Social, you can either destroy these instances, enable the extensions again or just add the content types to your Blueprint.