[5.x] Ensure unique blueprint instance #10353
Open
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.
This PR allows to programmatically add fields to an entry's blueprint without also altering the fields of other entries that use the same blueprint.
I've come across this issue on a multisite, where I need to extend the blueprint for only one localization. Consider this simplified event listener:
While the listener would only add the
description
field when it encounters a German entry, the fields would still be added to other entries that share the same blueprint because we are dealing with the same blueprint instance.A simple way to reproduce this issue on a fresh installation:
german
as the second sitegerman
site to thepages
collectionHome
pageThe
EntryBlueprintFound
event is triggered for thegerman
localization and its origin. Without this PR, the origin also ends up with the ensureddescription
field.