Theme config install settings.yml file breaks Bootstrap sub-theme

I was having the very same issue @steve and then found that I had not changed the libraries definition in the {subtheme}.info.ym file

libraries:
- 'THEMENAME/global-styling'
- 'THEMENAME/bootstrap-scripts'

Changing that and now my sub theme is picking up the compiled style.css file in the subtheme/css directory.

No patch.

A project I'm working with got bit by this issue as well. Our lack of updating these filenames (using the LESS starter kit) resulted in (as crazy as it sounds) dropdown menus not working.

Once we renamed the two ./subtheme/config/... files, we uninstalled and reinstalled the subtheme, cleared all caches, and the dropdown menus worked fine.

This really, really needs to be added to the documentation. In addition, the renaming of the THEMENAME.libraries.yml and THEMENAME.theme files aren't mentioned. I suggest inserting some new steps on http://drupal-bootstrap.org/api/bootstrap/docs%21subtheme%21README.md/gr... - perhaps they could read like this:

Once you've selected one of the above starterkits, here's how to install it:

1. Copy over one of the starterkits you have chosen from the ./bootstrap/starterkits directory into the themes directory.
2. Rename the folder to a unique machine readable name. This will be your sub-theme's "name". For this example and future examples we'll use subtheme.
3. Rename ./subtheme/THEMENAME.starterkit.yml to match the folder name and append .info.yml (e.g. ./subtheme/subtheme.info.yml).
4. Rename ./subtheme/THEMENAME.libraries.yml to match the folder name (e.g. ./subtheme/subtheme.libraries.yml).
5. Rename ./subtheme/THEMENAME.theme to match the folder name (e.g. ./subtheme/subtheme.theme).
6. Rename ./subtheme/config/install/THEMENAME.settings.yml to match the folder name (e.g. ./subtheme/config/install/subtheme.settings.yml).
7. Rename ./subtheme/config/schema/THEMENAME.schema.yml to match the folder name (e.g. ./subtheme/config/schema/subtheme.schema.yml).
8. Open ./subtheme/subtheme.info.yml and change the name, description and any other properties to suite your needs. Be sure to also change - THEMENAME/globalstyling to - subtheme/globalstyling.

thanks,
-mike

Thank you @ultimike. Was having a different issue with my LESS sub theme. Forms would not display. Followed your steps, renamed the two config files, uninstalled and reinstalled the theme and cleared the cache and all fixed.

Updating the documentation is a great idea.

Rename ./subtheme/THEMENAME.libraries.yml to match the folder name and append .info.yml (e.g. ./subtheme/subtheme.libraries.yml).

Shouldn't that be "(e.g. ./subtheme/subtheme.info.yml) ?

oh.. no,, you just need to remove "and append .info.yml" from step 4.. maybe.

@thursday_bw - good catch - I've just updated the suggested help text in comment 7 above.

thanks,
-mike

This was already fixed on this issue: https://www.drupal.org/node/2689693

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.

#13 worked for me. In case anyone doesn't know SQL, after you get a response from the Select statement above, run the following query:

DELETE FROM `config` WHERE `name` LIKE '%THEMENAME.settings%';

To be precise, that should work in most cases:

DELETE FROM `config` WHERE `name` LIKE '%THEME_NAME%';

where THEME_NAME is the old theme that's is causing issues.

#13 worked for me.

#13 worked for me too. Thanks

#13 & #14 worked for me. Thanks.