Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Move que system.theme.yml from install to optional, from the core theme, to avoid "[ERROR] Configuration objects (system.theme) provided by system already exist in active configuration" and to use a custom theme in the install step
Comment | File | Size | Author |
---|---|---|---|
#4 | system-theme-already-exist-issue-3014329-4.patch | 269 bytes | ccarrascal |
#2 | 3014329-system-theme-already-exist-issue.patch | 687 bytes | rzanetti |
Comments
Comment #2
rzanetti CreditAttribution: rzanetti at CI&T for Johnson & Johnson commentedComment #3
ccarrascal CreditAttribution: ccarrascal at Johnson & Johnson commentedHi, I have the same error while installing. I have tried the patch in #2, but it doesn't work for me.
What worked is moving the system.theme.yml file from:
./web/core/modules/system/config/install/system.theme.yml
To:
./web/core/modules/system/config/optional/system.theme.yml
Honestly, I don't know the repercussions that this change may have during a standard install, as I am using a custom profile.
Any ideas about how to fix this?
PS: I have the same problem in 8.6.4
Comment #4
ccarrascal CreditAttribution: ccarrascal at Johnson & Johnson commentedHi again,
I have created a patch to move system.theme.yml file from:
./web/core/modules/system/config/install/system.theme.yml
To:
./web/core/modules/system/config/optional/system.theme.yml
This solution is working for me in 8.6.4 when installing with a custom profile.
It needs to be tested in a clean Drupal installation.
EDIT:
I just found that my problem was that after running a composer update or composer install,
I was ending up with two copies of system.theme.yml file, in different locations:
So i just added a line in my composer file to remove that file manually. I still don't know the root cause,
because I don't see that extra file in web/core/config/install/system.theme.yml on a clean Drupal installation,
so it may be coming in one of the core patches that I am already using.
So this patch that I just uploaded should be useless for most of the people.
EDIT 2:
I just found out that my issue was due to this patch:
https://www.drupal.org/files/issues/2018-07-12/1356276-473.patch
This is part of this ticket:
https://www.drupal.org/project/drupal/issues/1356276
I have updated to the last patch in that issue and it solved my problem.
So there is no need to use my patch.
Comment #5
BerdirNon-config entity configuration can't be in optional, that doesn't make sense, it doesn't have dependencies.
You can't provide simple configuration of a different module, that's just not supported. only install profiles can do that.
Comment #7
svrl CreditAttribution: svrl as a volunteer commentedI have solved this issue using Configuration synchronization delete in Development tab in Drupal 8 settings "/admin/config/development/configuration".
1. access this URL
2. Config. type set as "Simple configuration"
3. Config. name set as "nameofyourtheme.settings"
4. Press "delete"
5. You can now reinstall/install your module which had active configuration issue