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 |
|
$context защищенное свойство
protected Context,Neos\ContentRepository\Domain\Service $context |
Результат |
Neos\ContentRepository\Domain\Service\Context |
|
$contextFactory защищенное свойство
protected ContextFactoryInterface,Neos\ContentRepository\Domain\Service $contextFactory |
Результат |
Neos\ContentRepository\Domain\Service\ContextFactoryInterface |
|