TypeError: Argument 1 passed to Drupal\field\ConfigImporterFieldPurger::getFieldStoragesToPurge() must be of the type array, bool given

Created on 12 April 2023, almost 2 years ago
Updated 4 January 2024, about 1 year ago

Installed module, visitied Ignore tab at: /admin/config/development/configuration/ignore

added the following:

system.site
update.settings

Clicked save.
Visited syncronise tab at: /admin/config/development/configuration

Get the below error:

TypeError: Argument 1 passed to Drupal\field\ConfigImporterFieldPurger::getFieldStoragesToPurge() must be of the type array, bool given, called in /modules/field/field.module on line 323 in Drupal\field\ConfigImporterFieldPurger::getFieldStoragesToPurge() (line 111 of core/modules/field/src/ConfigImporterFieldPurger.php).

🐛 Bug report
Status

Closed: outdated

Version

2.4

Component

Code

Created by

🇬🇧United Kingdom problue solutions Northern Ireland

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

Comments & Activities

  • Issue created by @problue solutions
  • 🇬🇧United Kingdom problue solutions Northern Ireland
  • Status changed to Postponed: needs info almost 2 years ago
  • 🇨🇦Canada nord102

    That error message doesn't look like it has anything to do with the Config Ignore module.

    I would encourage you to investigate a bit more into your site configuration as a whole.

  • 🇸🇮Slovenia useernamee Ljubljana

    I'm seeing this error if the `config/sync` directory is empty.

  • Status changed to Closed: outdated about 1 year ago
  • 🇨🇭Switzerland bircher 🇨🇿

    This issue is being closed because Config Ignore 2.x is deprecated.

    The new 3,x version has been re-written from the ground up and works in a totally different way, yet it provides the same backwards compatible functionality. All the 2.x tests pass in 3.x and the 3.x codebase is easier to maintain.
    Users of 2.x are strongly encouraged to upgrade to 3.x, as there is a very simple update path.

    So likely this issue is no longer relevant. If you think that this issue still applies please open it again and target the new branch. All issues on the 2.x branch were closed in bulk.

Production build 0.71.5 2024