After creating a new content type in DEV, and then in STAGE importing the exported DEV; After successful import, I find below file in in CHANGED state(STAGE)(1 Changed).

core.entity_view_display.node.my_node_type.teaser

CommentFileSizeAuthor
d8issue.png24.64 KBabhaysaraf

Comments

abhaysaraf created an issue. See original summary.

chi’s picture

chi commented
Project: Configuration Management » Drupal core
Version: 7.x-2.x-dev » 8.2.x-dev
Component: User interface » configuration system
Status: Needs work » Active

Configuration Management module has no D8 release. I suppose you are dealing with Drupal core configuration system.

abhaysaraf’s picture

abhaysaraf commented

Yes. Drupal core configuration system.

jonathanshaw’s picture

jonathanshaw
Primary language English
Location Stroud, UK
commented
Title: Drupal 8: At Synchronize, Teaser Config File Issue » Sync is confused about teasers

I have the same or related issue.

I created new fields and added them to both existing and new content types. When I import them into an upstream environment, the import is successful.
But on the Configuration synchronisation page (and in drush), I'm told that "core.entity_view_display.node.content_type_name.teaser" has changed.
The diff shows active as correctly having the fields as hidden:field_name:true, but staging simply has hidden:{}. Staging is actually right, that is what the YAML has.

So the teaser configuration is getting automatically updated on import, adding in the new fields, in some way that either didn't ever happen on the dev environment or happened and didn't get exported.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

xem8vfdh’s picture

xem8vfdh commented

+1
I am experiencing this too

calbasi’s picture

calbasi
Primary language Catalan
Location Catalonia
commented

I am experiencing this too (drupal 8.2.x)

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

WorldFallz’s picture

WorldFallz commented
Status: Active » Closed (duplicate)

For anyone following/confused by these issues, I believe the work is going on at #2915036: Display mode configurations don't get updated with new fields.