Followup from #1969698: ConfigEntity::save() should disallow saving ID/UUID conflicts (Field UUID changes can badly corrupt field data), postponed on discussion in #1969800: Add UUIDs to default configuration.

We're adding this exception handling to both Field and FieldInstance. Should ConfigEntity (or even entity) enforce that the UUID cannot change for an existing entity?

Comments

xjm’s picture

Assigned: Unassigned » xjm
xjm’s picture

swentel’s picture

Also related #1740378: Implement renames in the import cycle (but more or less duplicate) - and a big problem for fields at the moment (unless we start dropping features), see this comment http://drupal.org/node/1740378#comment-7130190

tstoeckler’s picture

Title: Throw an exception in ConfigEntity::save() (or even Entity::save() ?) if the UUID is changed » Throw an exception in Entity::save() if the UUID is changed

This makes total sense. I see no reason why this should be specific to ConfigEntities. Adjusting title for that.

xjm’s picture

sun’s picture

Issue summary: View changes
Status: Postponed » Active

Looks like the deps are resolved.

tim.plunkett’s picture

ConfigEntityBase::preSave() has partial handling for this.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.

tim.plunkett’s picture

Issue tags: -Blocks-Layouts

Not actively part of the Blocks-Layouts work.

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

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.