Tried with multiple views many times

Configuration block.block.bootstrap_mytheme_account_menu depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_branding depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_breadcrumbs depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_content depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_footer depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_help depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_local_actions depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_local_tasks depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_login depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_main_menu depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_messages depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_page_title depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_powered depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_search depends on the bootstrap_mytheme theme that will not be installed after import.
Configuration block.block.bootstrap_mytheme_tools depends on the bootstrap_mytheme theme that will not be installed after import.

Comments

F.E.M created an issue. See original summary.

AlexBorsody’s picture

Title: Unable to Import Views Configuration block.block.bootstrap_fem_account_menu depends on the bootstrap_mytheme theme that will not be installed after import. » Unable to Import Views Configuration block.block.bootstrap_mytheme_account_menu depends on the bootstrap_mytheme theme that will not be installed after import.
alexpott’s picture

Component: views.module » configuration system
Status: Needs work » Postponed (maintainer needs more info)
Issue tags: +Configuration system

Was the bootstrap_mytheme installed on the target site? If it is not then this is the expected behaviour. How was the theme uninstalled - when it was uninstalled it should have removed the blocks.

AlexBorsody’s picture

Yes the them is on both sites it is the same site no change. Was just two different time stamps a few hours later, I made some changes to a view, then wanted to import it into the same site on the test server, the site is identical except for a view. And this happens with every attempted import like this. It's hosted on Pantheon.

amedjones’s picture

Hi
My workaround for the above is to simply export to the tar.gz then extract it and copy the view.xx.yml files or any other yml config file you need. Once complete, compress them to .tar format and simply import into your server

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

freelock’s picture

Hi,

I'm running into something like this on a few different sites. In my case, I think the configurations blocking a config import are entirely extraneous, but I'm not completely sure of the cause.

What we're getting are about 20 messages along the lines of:

Configuration block.block.demo_bootstrap_user_9 depends
on the demo_bootstrap theme that will not be installed
after import.
Configuration block.block.menu depends on the class="placeholder">childrens theme that will not be installed after import.
Configuration block.block.menu_1 depends on the class="placeholder">childrens theme that will not be installed after import.

What I'm seeing with all of these messages is that the referenced themes do not exist. They might have existed at one point -- developers trying out different themes, or starting with a theme on one site and then changing it to a new name -- one thing or another, but the key issue is that the theme name is old/stale. And these configurations do seem to re-appear for some reason.

Some of the configurations have the theme name in the name of the configuration. Others have a "theme: " entry at the top level of the yaml as well as listed as a dependencies.theme value. So far deleting all these configurations and importing the config seems to clean these up -- but we have had them somehow re-appear a couple times...

One thing I notice: aside from an actual config for the missing theme, the config-import is complaining about two kinds of blocks specifically: block.block.menu*.yml, block.block.user*.yml. Neither of these are in my active theme! (Not sure if this is because we have them hidden, or because this is some legacy config that is no longer used).

Theories:

- Block configuration migrated from D6/D7 (some of the theme names I've deleted only existed on the original D6 site)
- Change to name of config that controls block placement, and config not properly deleted during a core update
- Block configs not properly removed when theme is uninstalled

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.