Closed stephsem23 closed 7 years ago
bobbygryzynger
commented
7 years ago The issue here ended up being that cm.core.dirs.sync.path is always set to: ${cm.core.path}/default, setting this to ${cm.core.path}/${multisite.name} in project.yml resolved this problem for us as this was an attempt to run setup:drupal:install on a non-default site with its own configuration. This issue can be closed.
leonk
commented
7 years ago We're having the same issue, but we're not using multisite, so I don't see how to resolve it (everything has to use the default directory).
We're using the standard profile, I just set this up on a fresh site. Exported my configuration to the default folder. My shortcut.set.default.yml file contains a uuid.
Now if I run blt setup again, I get the error from the post above (Entities exist of type <em class="placeholder">Shortcut link</em> and <em class="placeholder"></em> <em class="placeholder">Default</em>. These entities need to be deleted before importing.)
If I then set it to uuid: null and re-run blt setup it gets passed the point of doing the drupal install, but fails when it tries to import the configuration again (due to mismatching uuid's). (I get Unexpected error during import with operation update for shortcut.set.default: Attempt to save a configuration entity 'default' with UUID '' when this entity already exists with UUID)
Basically, I think running the standard profile with BLT is currently broken.
arisaves
commented
6 years ago Wondering if this is ever going to be addressed; I don't feel like we should be forced to use the lightning profile to avoid this. Really struggling with this, results for fixes are inconsistent, constant re-work, any help would be appreciated.
danepowell
commented
6 years ago I don't know that there's much BLT can do to address this, it's a Drupal core problem and can be easily reproduced by just using Drush to install the Standard profile and import configuration. For a good summary of the problem and quick fixes, see https://github.com/acquia/reservoir/issues/47
For a somewhat more in-depth explanation and fixes see https://danepowell.com/blog/installing-sites-existing-config-drupal-8
My system information:
Output of
blt doctor:While setting up a new multisite with the following setup command:
At this step:
I get the following output:
And I expected this to happen: I expected the config import to complete without any build failed messages.
Based on this issue i found: https://www.drupal.org/node/2638392#comment-11816155 , I attempted to edit
/config/niche/shortcut.set.default.ymland set the UUID to null. After doing so and re-importing config manually withdrush @site-alias cim, that seemed to work. However, when i try to run the setup command again, it seems like Drupal installs the shortcut module once more and attempts to import the incorrect shortcut module's config from the Drupal install config files.