i'm trying to migrate data from a .csv file using the modules migrate tools, migrate plus and migrate csv but i get the following 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."

CommentFileSizeAuthor
Capture du 2017-05-11 18-07-31.png113.04 KBzchokri

Comments

zchokri created an issue. See original summary.

zchokri’s picture

zchokri commented
Priority: Normal » Major
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Assigned: zchokri » Unassigned
Category: Bug report » Support request
Priority: Major » Normal

It appears you're getting that error when importing configuration, not when running migration? What does the .yml you're importing look like?

zchokri’s picture

zchokri commented

yes when importing configuration

id: user_migration
migration_tags: null
migration_group: null
label: 'User migration from CSV'
source:
  plugin: csv
  path: /home/zidane/Zidane-platform/project-migrate/export.csv
  header_row_count: 1
  keys:
    - ID
process:
  field_nom: Nom
  field_prenom: Prenom
  field_email: EMail
  field_civilite: Sexe
  field_pays_site: Pays
  field_responsable_site: ResponsableSite
  field_type_salarie_et_service: TypeSalarie
  field_agence_salarie: Agence
  filed_responsable_ingenieur: ResponsableIngenieur
  field_responsable_commercial: ResponsableCommercial
  field_poste_salarie: Poste
  field_date_naissance: DateDeNaissance
  field_telephone: Telephone
destination:
  plugin: 'entity:user'
migration_dependencies:
  required: {  }
optional: {  }
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Title: issu with migrating data from a .csv file » issue with importing YAML configuration
Project: Migrate Plus » Drupal core
Version: 8.x-4.0-beta1 » 8.3.x-dev
Component: API » configuration system

I'm not sure where to move this issue - it doesn't appear to have anything to do with migrate_plus (or, really, migration at all). I guess core configuration management is closest...

You're using the configuration UI to import some YAML and getting an error message that has nothing to do with the YAML you're trying to import. I'm perplexed, maybe some configuration management expert might hazard a guess...

TigerWhite’s picture

TigerWhite commented

I have the same issue ...
zchokri Have you resolved it?

zchokri’s picture

zchokri commented
Status: Active » Fixed

Yes
You must delete the the THEMENAME config, you can use drush to delete it with the command : " drush config-delete THEMENAME.settings "

Status: Fixed » Closed (fixed)

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

james917’s picture

james917 commented

I deleted THEMENAME config but I am still getting the same errors

giorgosk’s picture

giorgosk
Location Chios, Greece 🇬🇷
commented

You can delete config from database if have not exported yet so it does not give you trouble later

drush config-delete THEMENAME.settings

or you can delete from export directory when importing and gives you the trouble mentioned above

rm sites/default/files/config_*/sync/THEMENAME.settings.yml
# then try again
drush config-import

I believe this happens because bootstrap has the starterkits with this particular config install for example in
themes/contrib/bootstrap/starterkits/less/config/install/THEMENAME.settings.yml
but is this a bug of bootstrap or core ? what does this setting get into the database in the first place ?

Here is a discussion for it on bootstrap issue queue #2706711: Configuration THEMENAME.settings depends on the THEMENAME theme that will not be installed after import.

renus09’s picture

renus09 commented

Hi,

I am also getting error while importing a view single item from dev to stage environment drupal8-

The configuration cannot be imported because it failed validation for the following reasons:
Configuration block.block.block depends on the
Theme theme that will not be installed after import.
Configuration block.block.block103 depends on the
Theme theme that will not be installed after import.
Configuration block.block.block104 depends on the
Theme theme that will not be installed after import.
Configuration block.block.block105 depends on the
Theme theme that will not be installed after import.

Please suggest how to overcome this issue.

aquaphenix’s picture

aquaphenix
Primary language English
commented

I ran into a similar issue as described on #11,

Configuration block "block.block.views_block__featured_content_featured_content_block" depends on the theme that will not be installed after import. Looking at the block.block.views_block__featured_content_featured_content_block.yml file the theme value is set to null. For some reason the value was not set correctly, updated to the correct installed theme and running again drush cim fix the issue for me.

lukus’s picture

lukus
he/him
commented

I'm experiencing the same problem.