Follow-up to. 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.
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 , 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...
User interface changes