When two subthemes are created from the same boostrap base theme, the second does not work, instead throws exception.
Uncaught PHP Exception Drupal\\Core\\Config\\PreExistingConfigException: "Configuration objects (THEMENAME.settings) provided by {THEMENAME} already exist in active configuration" at /var/www/html/drupal-8.0.2/core/lib/Drupal/Core/Config/PreExistingConfigException.php line 70
The issue seems to be that config/schema/THEMENAME.schema.yml was not updated for the subthemes. This creates duplicates for subsequent subthemes. This value is not cleared even after unistalling the themes, but had to be manually removed from the database tables.
Comment | File | Size | Author |
---|---|---|---|
#3 | subtheme_schema_themename_documntation-2689693-3.patch | 999 bytes | jorgediazhav |
Comments
Comment #2
jorgediazhav CreditAttribution: jorgediazhav at Evolving Web commentedHi Jaya M:
So, just to confirm (It may sound weird what I will ask):
Did you renamed THEMENAME with the name of your respective sub-themes?
If so, we will appreciate you rewrite the issue description following this template:
Issue Summary Template standards
Thanks!!!
Comment #3
jorgediazhav CreditAttribution: jorgediazhav at Evolving Web commentedAhh, OK, I missed he pat where you said "not mentioned in the document"
Ok, already added this to the doc:
Changing the category to "Documentation".
Comment #4
jorgediazhav CreditAttribution: jorgediazhav at Evolving Web commentedComment #5
Jaya M CreditAttribution: Jaya M as a volunteer commentedThanks jorgediazhav! Sorry for the delayed reply. But you already figured out the problem and fixed it.
Comment #6
jorgediazhav CreditAttribution: jorgediazhav at Evolving Web commentedComment #8
markhalliwellComment #10
ex DJ CreditAttribution: ex DJ commentedI'm getting this also, using a Bootstrap subtheme. The file mentioned doesn't exist anywhere on my site; I've checked multiple times. All references to THEMENAME.anything have been removed. I am completely frustrated at this point, and not going to meet a migration deadline.
Comment #11
tarun8085 CreditAttribution: tarun8085 commentedI have tried the below solution and it worked out for me for single item import.
Try to run this query in your database :
SELECT * FROM `config` WHERE `name` LIKE '%THEMENAME.settings%';
If there is a row found, delete that row from config table.
Clear cache once and it should not give you the THEMENAME.settings error any more during single item import.
Comment #12
jeromewiley CreditAttribution: jeromewiley commentedHow was this fixed?
I'm trying to import a fairly simple view from local Dev to remote Dev, and getting this error:
Subscribe.
Comment #13
markhalliwellTHEMENAME
is simply a placeholder for the starterkits. You should have renamed these per the instructions at https://drupal-bootstrap.org/api/bootstrap/docs%21Sub-Theming.md/group/s...