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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Jaya M created an issue. See original summary.

jorgediazhav’s picture

Hi 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!!!

jorgediazhav’s picture

Ahh, OK, I missed he pat where you said "not mentioned in the document"

Ok, already added this to the doc:

5. Rename the sub-theme files `./config/install/THEMENAME.settings.yml` and
   `./config/schema/THEMENAME.schema.yml` to match the folder name.
6. Open `./config/schema/THEMENAME.schema.yml` and change `- THEMENAME.settings:`
   to `- subtheme.settings:` and label: `'THEMETITLE settings'` to `'Your Theme Title settings'`

Changing the category to "Documentation".

jorgediazhav’s picture

Component: Starterkit (LESS) » Documentation
Status: Active » Needs review
Jaya M’s picture

Thanks jorgediazhav! Sorry for the delayed reply. But you already figured out the problem and fixed it.

jorgediazhav’s picture

Status: Needs review » Reviewed & tested by the community

markhalliwell’s picture

Version: 8.x-3.0-beta3 » 8.x-3.x-dev
Category: Bug report » Task
Priority: Major » Normal
Status: Reviewed & tested by the community » Fixed
Issue tags: -Documentation

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

ex DJ’s picture

I'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.

tarun8085’s picture

I 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.

jeromewiley’s picture

How was this fixed?

I'm trying to import a fairly simple view from local Dev to remote Dev, and getting this error:

The configuration cannot be imported because it failed validation for the following reasons:

    Configuration THEMENAME.settings depends on the THEMENAME extension that will not be installed after import.

Subscribe.

markhalliwell’s picture

THEMENAME 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...