Problem/Motivation

When I upgraded from 1.7 to 1.8 for the security release, the upgrade included a number of bug fixes, one adding a field to the configuration schema (commit f2871338). During our build using BLT, the testing configuration import does 2 drush config:imports followed by a config:status which showed the config was still different, even though I did "drush updb" and "drush cex". I had to manually edit each facet and save it (no changes to the facet itself) to get the updated configuration to export.

Steps to reproduce

  1. Install Facets 1.7, create one or more facets and export the configuration.
  2. Update to Facets 1.8 (I used "composer update drupal/facets -W")
  3. Run database updates (I used "drush updb", no updates reported)
  4. Export configuration (I used "drush cex", no configuration exported)
  5. (following is on our CI/CD pipeline)
  6. Fresh install of Drupal using minimal profile and clear caches
  7. Import configuration ("drush cim")
  8. Import configuration ("drush cim")
  9. Check configuration status ("drush config:status")

The drush config:status will show the facets configuration is still different.

Issue fork facets-3213733

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

greggmarshall created an issue. See original summary.

grahl made their first commit to this issue’s fork.

grahl opened merge request !22

grahl’s picture

grahl
he/him
Location Zürich
commented
Status: Active » Needs review

Same thing here, added an update hook to resave all facets so that the correct schema is picked up and can be exported. Not sure if there is a more elegant way of doing this.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Status: Needs review » Reviewed & tested by the community

Looks like a simple fix. Thanks @grahl!

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Version: 8.x-1.8 » 2.0.x-dev
Status: Reviewed & tested by the community » Needs review

Test again with 2.0.x and Drupal 9.

  • mkalkbrenner committed c12cd3a on 2.0.x 
    Issue #3213733 by grahl, greggmarshall, borisson_, mkalkbrenner: 1.7 to...
mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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