[6.x] Add field references + deletion blockers#19014
Open
riasvdv wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This brings the field references & deletion blocker that was added to CKEditor into the core.
This introduces a new
fieldreferencestable, aTracksReferencesFieldInterfacemarker contract, field lifecycle listeners that keep tracked references in sync, and a generic deletion blocker/replacement flow for referenced elements.The Markdown field now opts-in to this system, so element reference tags in Markdown content can block deletion and be replaced through the delete-elements flow.
Plugin developers can add reference tracking to custom fields by:
CraftCms\Cms\Field\Contracts\TracksReferencesFieldInterfacemarker interface.serializeValue()returns the raw serialized field content that should be scanned for element reference tags. (This should already be the case for almost all custom fields)setFieldValue()/ normalization after numeric reference IDs are replaced. (Should also already be the case for all custom fields)When tracked references are replaced, Craft updates the serialized field value and saves the source element without validation; the normal field save lifecycle then refreshes
fieldreferences.Existing content is not backfilled automatically. Sites should resave elements containing tracking-enabled fields to populate reference rows.