Config imports are failing on site install because of a config entity being created in lightning_preview_install. Can this be moved to a sub-module of lightning_preview (perhaps lightning_preview_demo) so sites can be created without this configuration?

Causing this error:

Drupal\Core\Config\ConfigImporterException: There were errors validating the config synchronization. in Drupal\Core\Config\ConfigImporter->validate() (line 728 of            [error]
/var/www/canary/docroot/core/lib/Drupal/Core/Config/ConfigImporter.php).
The import failed due for the following reasons:                                                                                                                              [error]
Entities exist of type <em class="placeholder">Workspace</em> and <em class="placeholder">Workspace type</em> <em class="placeholder">Basic workspace</em>. These entities
need to be deleted before importing.

Comments

arknoll created an issue. See original summary.

arknoll’s picture

arknoll CreditAttribution: arknoll commented
Related issues: +#2834874: Remove default Shortcuts configured in lightning.install
balsama’s picture

balsama
he/him
Primary language English
Location boston
CreditAttribution: balsama at Acquia commented
Assigned: Unassigned » phenaproxima
phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Status: Active » Postponed (maintainer needs more info)

Config imports are failing on site install because of a config entity being created in lightning_preview_install

lightning_preview_install() creates no entities at all. It does attempt to modify existing ones, but it doesn't create any. A backtrace might be helpful here?

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima at Acquia commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

So yeah...Preview's install hook creates no entities at all, and it never has...although it does modify the existing Basic workspace type. I think you need at one workspace type in order to use Preview, so I'd say this works as designed. Closing.