This same conflict is occurring in many modules after new drush version, eg #2870864: Default configuration provided by modules breaks core configuration management.

CommentFileSizeAuthor
#2 2926050-2.patch727 bytesmikran
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikran created an issue. See original summary.

mikran’s picture

mikran CreditAttribution: mikran at Mediamaisteri Oy commented
Status: Active » Needs review
FileSize
2926050-2.patch727 bytes

and a patch, same fix has been applied to other projects too.

mikran’s picture

mikran CreditAttribution: mikran at Mediamaisteri Oy commented
Title: Errors from config syncing, field_item storage is being created twice » Errors from config syncing, feeds_item storage is being created twice
MegaChriz’s picture

MegaChriz CreditAttribution: MegaChriz as a volunteer commented

@mikran
Just to be sure, the patch aims to fix the following error?

[error] The import failed due to the following reasons:
Configuratie-entiteit 'field.storage.commerce_product.feeds_item' verwijderd en vervangen
Configuratie-entiteit 'field.storage.commerce_product_variation.feeds_item' verwijderd en vervangen
Configuratie-entiteit 'field.storage.node.feeds_item' verwijderd en vervangen

mikran’s picture

mikran CreditAttribution: mikran at Mediamaisteri Oy commented

This is the error in English. I'm not sure if it is the same

Deleted and replaced configuration entity "field.storage.crm_core_individual.feeds_item"

  • MegaChriz committed b88b613 on 8.x-3.x authored by mikran 
    Issue #2926050 by mikran: Fixed errors from config syncing, feeds_item...
MegaChriz’s picture

MegaChriz CreditAttribution: MegaChriz at WebCoo commented
Status: Needs review » Fixed

Yes, that is the same error. I've tested the patch this way:

  1. Created a few Feeds types.
  2. Exported config with drush cex.
  3. Removed feed_item fields.
  4. Uninstalled Feeds.
  5. Imported config with drush cim.

Without the patch applied I received the error that I reported in #4.
With the patch applied no more errors.

I also verified that the feeds_item field still got created when adding a new feed type or when removed a feed_item field and then resaving the feed type where that field was associated with.

I also checked if Drupal::isConfigSyncing() exists in Drupal 8.3.x, the currently minimum requirement for Feeds.

Committed #2.

Status: Fixed » Closed (fixed)

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