EZP-31811: Fixed deleted relation fieldtypes #101
Merged
Conversation
This file contains 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
adamwojs
approved these changes
Aug 27, 2020
ViniTou
approved these changes
Aug 27, 2020
bogusez
approved these changes
Aug 28, 2020
|
You can merge it up. |
|
Merged: 477a7ab |
|
Hello, It seems that the relationship is preserved. But when publishing the content the field is avoided. Relations should not be deleted when content type is modified ? |
Steveb-p
pushed a commit
that referenced
this pull request
May 31, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Deleted 'Content relation' fieldtype results in an error when editing Content possessing this relation previously. When the relation does not exist anymore
mappedRelationswill be build and throw an exception before.Checklist:
$ composer fix-cs).