adoptNodeMatchesTargetContextDimensions()
공개 메소드
createVariantForContextAlsoWorksIfTheTargetWorkspaceDiffersFromTheSourceWorkspace()
공개 메소드
createVariantForContextMatchesTargetContextDimensions()
공개 메소드
getPropertyDoesNotReturnNodeReferencesIfTheyAreNotVisibleAccordingToTheContentContext()
공개 메소드
nodesCreatedInTheLiveWorkspacesCanBeRetrievedAgainInTheLiveContext()
공개 메소드
postprocessorUpdatesNodeTypesProperty()
공개 메소드
renumberingTakesUnpersistedNodeOrderChangesIntoAccount()
공개 메소드
The error can be reproduced in the following way:
- First, create some nodes, and persist.
- Then, move a node after another one, filling the LAST free sorting index between the nodes. Do NOT persist after that.
- After that, try to *again* move a node to this spot. In this case, we need to *renumber*
the node indices, and the system needs to take the before-moved node into account as well.
The bug tested by this testcase led to wrong orderings on the floworg website in
the documentation part under some circumstances.
$contentDimensionRepository 보호되어 있는 프로퍼티
protected ContentDimensionRepository,Neos\ContentRepository\Domain\Repository $contentDimensionRepository |
리턴 |
Neos\ContentRepository\Domain\Repository\ContentDimensionRepository |
|
$contextFactory 보호되어 있는 프로퍼티
protected ContextFactoryInterface,Neos\ContentRepository\Domain\Service $contextFactory |
리턴 |
Neos\ContentRepository\Domain\Service\ContextFactoryInterface |
|