Fix EZP-25280: ParentDepth Limitation fails on content creation #1703
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
pspanja
force-pushed
the
fix-EZP-25280-parent-depth-content-create
branch
from
e35c041 to
aaaeaa4
Compare
|
With fix for CS +1 However should be reopened against 6.4 branch once @bdunogier has tagged final. |
pspanja
force-pushed
the
fix-EZP-25280-parent-depth-content-create
branch
from
aaaeaa4 to
d4cf6d5
Compare
|
Ok, fixed and amended. |
|
6.4 branch up ;) |
|
Closing in favor of #1706. |
# 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.
This PR resolves https://jira.ez.no/browse/EZP-25280
As described in the comment on the issue, the problem comes from missing Location on publishing the first Content draft. Solution is similar to what was already done for
LocationLimitationType.Added failing/fixed integration test and missing unit tests.