[FEATURE] Upgrade wizard for problematic content element "sorting" values #1929
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
…lues Copying pages will fail to adjust the colPos values when the "sorting" value of child elements is larger than that of its parent record. This leads to "lost" content records that are visible in the list view, but not in the web view in the TYPO3 backend. This problem happens at least when migrating from TYPO3 v7 to v8 while upgrading to flux 9.5.0. Old content records exhibit this problem, while newly created content is fine - TYPO3 takes care of modifying the "sorting" values correctly. This wizard fixes the problematic sorting values by finding the largest child sorting value and adjusting the parent's "sorting" accordingly, as well as all following content element siblings. Resolves: FluidTYPO3#1824
NamelessCoder
approved these changes
Mar 27, 2022
NamelessCoder
approved these changes
Mar 27, 2022
|
Excellent - thanks @cweiske! |
cweiske
added a commit
to mogic-le/flux
that referenced
this pull request
Mar 30, 2022
We drop support for TYPO3v8 for that feature. Resolves: FluidTYPO3#1934 Related: FluidTYPO3#1929
cweiske
added a commit
to mogic-le/flux
that referenced
this pull request
Mar 30, 2022
The v8 API is not available on TYPO3v10 and v11, so to support them we have to use the new upgrade wizard API. We drop support for TYPO3v8 for that feature. See https://docs.typo3.org/c/typo3/cms-core/9.5/en-us/Changelog/9.4/Feature-86076-NewAPIForUpgradeWizards.html Resolves: FluidTYPO3#1934 Related: FluidTYPO3#1929
cweiske
added a commit
to mogic-le/flux
that referenced
this pull request
May 6, 2022
The v8 API is not available on TYPO3v10 and v11, so to support them we have to use the new upgrade wizard API. We drop support for TYPO3v8 for that feature. See https://docs.typo3.org/c/typo3/cms-core/9.5/en-us/Changelog/9.4/Feature-86076-NewAPIForUpgradeWizards.html Resolves: FluidTYPO3#1934 Related: FluidTYPO3#1929
NamelessCoder
pushed a commit
that referenced
this pull request
May 6, 2022
The v8 API is not available on TYPO3v10 and v11, so to support them we have to use the new upgrade wizard API. We drop support for TYPO3v8 for that feature. See https://docs.typo3.org/c/typo3/cms-core/9.5/en-us/Changelog/9.4/Feature-86076-NewAPIForUpgradeWizards.html Resolves: #1934 Related: #1929
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Copying pages will fail to adjust the colPos values when the "sorting" value
of child elements is larger than that of its parent record.
This leads to "lost" content records that are visible in the list view,
but not in the web view in the TYPO3 backend.
This problem happens at least when migrating from TYPO3 v7 to v8 while
upgrading to flux 9.5.0.
Old content records exhibit this problem, while newly created content
is fine - TYPO3 takes care of modifying the "sorting" values correctly.
This wizard fixes the problematic sorting values by finding the largest
child sorting value and adjusting the parent's "sorting" accordingly,
as well as all following content element siblings.
Resolves: #1824