-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EZP-32401: Fixed handling trashed Content by LocationLimitation #3093
EZP-32401: Fixed handling trashed Content by LocationLimitation #3093
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The use case should be easily reproducible via integration test.
Besides commit message and PR title can be formed better (plural here is not "contents"). How about "Fixed handling trashed Content by LocationLimitation"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA approved on eZPlatform 2.5 & v2.5.17 with patch & diff.
Could you merge it up? |
Holding on with merge until #3092 is merged. |
When Content was trashed and it had reverse relation the Location was not accessible. Therefore additional condition had to be added which exports trashed Location and uses it as a target.
TODO:
$ composer fix-cs
).