site configs are out of sync: original site has 'standard' enabled; deployed does not

Created on 2 May 2016, almost 9 years ago
Updated 11 December 2023, over 1 year ago

Possibly a consequence of #2715993: installer crashes during import ...

My initial local build site was built on the 'standard' profile. Accordingly, my core.extension.yml file has this in it:

  standard: 1000

But the site I deployed using Config installer doesn't have 'standard'. If I try to do a 'drush cim', I get this error:

The import failed due for the following reasons:                     [error]
Unable to install the <em class="placeholder">standard</em> module
since it does not exist.

If I try to disabled standard from the initial site, I get this error:

The import failed due for the following reasons:                     [error]
Unable to uninstall the <em class="placeholder">Standard</em> profile
since it is the install profile.

Currently, the only workaround seems to me to keep one of the sites in a perpetual state of its config files being overridden from git:

- remove standard from the config locally, keep local files out of sync with git
- keep the deployed site's config with standard removed

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇬🇧United Kingdom joachim

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024