Configuration import no longer possible due to missing ai_automator_address extension

Created on 26 October 2024, 6 months ago

Problem/Motivation

Hi Marcus,

After 📌 Rename data name to ai_automators Active I'm still left with one issue. I can't import any drupal config anymore due to the following error:
Configuration ai_automator_address.google_places_settings depends on the ai_automator_address extension that will not be installed after import.

I'm on the latest dev of both the ai and the google_places module.

Thanks as always

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇹🇭Thailand AlfTheCat

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

Comments & Activities

  • Issue created by @AlfTheCat
  • 🇩🇪Germany marcus_johansson

    Hi @alfthecat - thank you for finding this, its a bug where the configuration has not been updating since changing names.

    I have pushed a change to dev - I think you will have to get latest dev, flush the cache and then rename the configuration file ai_automator_address.google_places_settings.yml to google_places.settings.yml

  • 🇹🇭Thailand AlfTheCat

    Hi Marcus,

    I've updated to the latest dev but now it's not longer fetching any data. Not getting any errors in the log, it just stopped working.

  • 🇹🇭Thailand AlfTheCat

    Hi Marcus,

    I'm having no luck with this still, it's getting problematic that I can't import config updates anymore.

    Could you perhaps clarify:

    rename the configuration file ai_automator_address.google_places_settings.yml to google_places.settings.yml

    I'm looking for this file but its not in my codebase anywhere.

    I've tried drush config:delete "ai_automator_address.google_places_settings" and that gets my imports up and running again but also breaks the functionality of the module.

  • 🇩🇪Germany marcus_johansson

    In the configs directory that is defined in the settings.php there should be a file called ai_automator_address.google_places_settings.yml, this file needs to be renamed google_places.settings.yml

  • 🇹🇭Thailand AlfTheCat

    Hi Marcus,

    Thanks, I figured that would be it, but in my case that directory was empty.

    I ran drush cex, changed the config file name, and flushed caches.

    When I try to import, I get a new error:

    vendor/bin/drush cim
    +------------+---------------------------------------------+-----------+
    | Collection | Config                                      | Operation |
    +------------+---------------------------------------------+-----------+
    |            | google_places_settings                      | Create    |
    |            | ai_automator_address.google_places_settings | Delete    |
    +------------+---------------------------------------------+-----------+
    
     ┌ Import the listed configuration changes? ────────────────────┐
     │ Yes                                                          │
     └──────────────────────────────────────────────────────────────┘
    
    
    In ConfigImportCommands.php line 291:
    
      The import failed due to the following reasons:
      The config name google_places_settings is invalid.
      Configuration <em class="placeholder">google_places_settings</em> depends on the <em class="placeholder">google_
      places_settings</em> extension that will not be installed after import.

    Appreciate your thoughts on this. I also tried removing the multi-field, uninstalling the module, installing it again, re-creating the field, and strangely enough I get the same error when trying to import config files and on top of it the module stops working.... It has me scratching my head a bit, I can't figure out what is wrong :)

  • 🇩🇪Germany marcus_johansson

    could you check if you renamed to google_places.settings? it looks like it got renamed to google_places_settings

  • 🇹🇭Thailand AlfTheCat

    Ah! That did it.

    Thanks very much. All systems are go again! Very happy with this.

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

Production build 0.71.5 2024