Problem/Motivation

Follow-up to #2341357: Views entity area config is not deployable and missing dependencies. In that issue, we added support to store UUIDs for entity area handlers while displaying the serial ID to the user in the configuration form. However, when a view is deployed referencing a content entity UUID that does not exist on the target site, the user interface displays a UUID instead of the expected serial ID.

Proposed resolution

Determine what to present to the user when a Views plugin has a dependency on a content entity when it is not available. We might:

  • Decide the current behavior is fine, since 8.0.0 core will not support content entity dependency selection. (This would mean that we'd have to allow UUIDs in #2392833: Entity area handler input is not validated, despite that they are not valid input.)
  • Allow a UUID as input.
  • Display a message/warning to the user in the admin form that the content entity was not available and tell them to pick a different entity or see a handbook page.
  • Leave this postponed until core potentially supports some UI for finding content dependencies, and let contrib sort it out in the meanwhile.
  • Or something in between...

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Postponed until

#2341357: Views entity area config is not deployable and missing dependencies

Comments

xjm’s picture

Status: Postponed » Active

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.

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.