I tested it successfully with added translations, updated fields in the translation and with removed translations.
These code bits are mostly based onto the existing logic in ShallowRecordFinder::addChildPagesRecursively. Fetching the pages rows by property transOrigPointerField of the identifier of the rootRecord should always return all corresponding translations.
The transOrigPointerField one is made at the very beginning of my addition, outside of the static function. I assumed the languageField check would have been redundant, since we're targeting records with transOrigPointerField > 0, so I removed it as well. Let me know if you think we might run into edge cases.
vertexvaar
commented
9 months ago
Fixes https://github.com/in2code-de/in2publish_core/issues/107
I tested it successfully with added translations, updated fields in the translation and with removed translations.
These code bits are mostly based onto the existing logic in
ShallowRecordFinder::addChildPagesRecursively. Fetching thepagesrows by propertytransOrigPointerFieldof the identifier of the rootRecord should always return all corresponding translations. ThetransOrigPointerFieldone is made at the very beginning of my addition, outside of the static function. I assumed thelanguageFieldcheck would have been redundant, since we're targeting records withtransOrigPointerField > 0, so I removed it as well. Let me know if you think we might run into edge cases.