It was reported in #2404999: Don't save records for default values that when an entity has a non-default, non-custom display (i.e. there are multiple displays available, but it's not using the one configured as the default for that view mode) changing the value to the default doesn't make the change take effect.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

DamienMcKenna created an issue. See original summary.

DamienMcKenna’s picture

Status: Active » Needs review
FileSize
2.02 KB

This test shows it appears to be working correctly after all.

DamienMcKenna’s picture

An updated test to see if the display can be switched back to the default display.

Status: Needs review » Needs work

The last submitted patch, 3: panelizer-n2758569-3.patch, failed testing.

DamienMcKenna’s picture

Status: Needs work » Needs review
FileSize
5.75 KB

Lets see if this fixes the bug.

  • DamienMcKenna committed a9d771a on 7.x-3.x
    Issue #2758569 by DamienMcKenna: When changing a node from a non-default...
DamienMcKenna’s picture

Status: Needs review » Fixed

*phew*. Committed.

FeyP’s picture

@DamienMcKenna: Thanks a lot for the quick fix! It works like a charm now. I'm so glad, that this made it into the new release :). Keep up the good work, it is much appreciated!

Status: Fixed » Closed (fixed)

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