Import-export impossible due to some weird depencencies

Created on 23 June 2023, over 1 year ago
Updated 11 July 2023, over 1 year ago

The bpmn_io...gz files prepared on the test site cannot be opened on the live site (which is currently an exact copy of the test site), an error message appears:

The import failed due to the following reason: There were errors validating the config synchronization. Configuration <em class="placeholder">block.block.bartik_system_main</em> depends on the <em class="placeholder">Bartik</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.bartik_system_powered_by</em> depends on the <em class="placeholder">Bartik</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.bartik_user_login</em> depends on the <em class="placeholder">Bartik</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.cti_flex_menu_menu_labori_menyy</em> depends on the <em class="placeholder">cti_flex</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.cti_flex_system_main</em> depends on the <em class="placeholder">cti_flex</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.garland_system_main</em> depends on the <em class="placeholder">garland</em> theme that will not be installed after import. Configuration <em class="placeholder">cti.settings</em> depends on the <em class="placeholder">cti</em> extension that will not be installed after import. Configuration <em class="placeholder">garland.settings</em> depends on the <em class="placeholder">garland</em> extension that will not be installed after import. Configuration <em class="placeholder">block.block.bartik_system_main</em> depends on the <em class="placeholder">Bartik</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.bartik_system_powered_by</em> depends on the <em class="placeholder">Bartik</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.bartik_user_login</em> depends on the <em class="placeholder">Bartik</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.cti_flex_menu_menu_labori_menyy</em> depends on the <em class="placeholder">cti_flex</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.cti_flex_system_main</em> depends on the <em class="placeholder">cti_flex</em> theme that will not be installed after import. Configuration <em class="placeholder">block.block.garland_system_main</em> depends on the <em class="placeholder">garland</em> theme that will not be installed after import. Configuration <em class="placeholder">cti.settings</em> depends on the <em class="placeholder">cti</em> extension that will not be installed after import. Configuration <em class="placeholder">garland.settings</em> depends on the <em class="placeholder">garland</em> extension that will not be installed after import. 

I'm not a specialist, but the idea of import-export seems to go awry here...
D9.5.9 -- I will be happy to provide all additional necessary information; site is upgraded from D7.

💬 Support request
Status

Fixed

Version

1.1

Component

Code

Created by

🇪🇪Estonia veskimees

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @veskimees
  • 🇩🇪Germany jurgenhaas Gottmadingen

    Can you explain what steps you've taken to get to those error messages?

    Also, could you please upload the exported model for a detailed analysis?

  • 🇪🇪Estonia veskimees

    0. Made copy of the site (live is https://algernon.ee, test is https://test.algernon.ee, only difference are in front page, site information etc)
    1. Prepared ECA model in test site.
    2. Exported it (admin/config/workflow/eca Operations -> export --you know)
    3. Tried import it to live site
    (Unfortunately, some keywords in model are in Estonian, but the idea should be understandable and the model works as it should [by the way, thanks, ECA seems to be a really awesome thing... if only the documentation would be created... :-) ]; it is a movie review functionality hidden from the normal user, which creates a link to the original movie node in the message area, taking the corresponding id from the taxonomy term.)

  • 🇩🇪Germany jurgenhaas Gottmadingen

    Thanks for uploading your model. I've looked into it and it declares the following dependencies:

    config:
      - eca.eca.process_xmmexjh
      - eca.model.process_xmmexjh
      - field.field.node.arvustus.field_film
      - field.storage.node.field_film
      - node.type.arvustus
      - taxonomy.vocabulary.filmid
      - field.field.node.kino_page.field_film
      - node.type.kino_page
    module:
      - eca_content
      - field_permissions
      - node
      - taxonomy
      - menu_ui
    

    There is no dependency for bartik, garland or any of the others that are mentioned in your error message above. That sounds like the config on that live site is somehow invalid already before importing the model. This should be fixed first. But I'm not sure what to do and how to fix it. I would probably export the config with drush cex and if that worked, re-import everything with drush cim. If that throws any errors, then they need to fix them first.

    Before you do any of that, please make backups!

  • Status changed to Postponed: needs info over 1 year ago
  • 🇩🇪Germany jurgenhaas Gottmadingen
  • 🇪🇪Estonia veskimees

    Sorry for taking so long to reply.
    I have to admit I've never used drush and I can't seem to get around to using it in the provider environment I'm using (maybe I am just stupid...) However, I repeat, mine is an old, repeatedly changed and from D7 converted site that also behaves strangely with some other modules -- so maybe it's an exception that's not worth wasting time on. Besides -- I have three tiny ECA models, I just made them manually in the live site and problem solved...
    Thanks for your time!

  • Status changed to Fixed over 1 year ago
  • 🇩🇪Germany jurgenhaas Gottmadingen

    Thanks for your feedback.

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

Production build 0.71.5 2024