$TCA[<table>]['ctrl']['shadowColumnsForMovePlaceholders'] behaves similar to shadowColumnsForNewPlaceholders but is only used for move placeholders.
[FEATURE] Introduce shadowColumnsForMovePlaceholders property
similar to shadowColumnsForNewPlaceholders but is only used for
If shadowColumnsForMovePlaceholders is not defined in particular
for a table, but shadowColumnsForNewPlaceholders is defined,
then that value is used as a fallback - since that property
existed for a longer time already.
#4 Updated by Oliver Hader almost 6 years ago
Thorsten Kahler wrote:
Why do we need another config option for move placeholders? What's the difference to new placeholders in this context?
The difference is "it is used for move placeholders" only... as written...
The reason for that is the way move-placeholders are overlaid in the frontend.
See https://review.typo3.org/#/c/27774/ and the accordant CSV tests on sorting/moving things...
#5 Updated by Oliver Hader almost 6 years ago
Timo Webler wrote:
For IRRE that's not enough - the action happens in DataHandlerHook::moveRecord
Available changes for move placeholder:
- DataHandler::versionizeRecord (creates version and the new placeholder)
- DataHanderHook::moveRecord_wsPlaceholders (creates move placeholder after everything was processed and remapped (remapStack))
- https://travis-ci.org/ohader/TYPO3.CMS/jobs/20950988 (the expected values are not set, thus misusing the newPlaceHolder property is not enough)
- https://travis-ci.org/ohader/TYPO3.CMS/jobs/20951081 (disabled the DataSet assertions - thus behaviour in frontend is not as expected)
#7 Updated by Oliver Hader almost 6 years ago
Gerrit Code Review wrote:
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28473
This change combines the new property for "move" with the old property for "new" as a fallback...
Thus, one can decide whether to override/disable on demand.