Issue Bug Closed

#84951Localization: Copying new record in existing localization has off-by-one issue

Andreas Kienast 05/09/18, 09:04 updated 10/02/18, 10:47

Description

The default language has two records, which are copied (not translated) into a different language.
A new record is added in the default language at any position. If the records gets copied into the other language, the calculated position is wrong, the record is one “slot” above.

The issue is caused by BackendUtility::getRecordLocalization() (called by DataHandler::getPreviousLocalizedRecordUid()) which uses the l18n_parent field to get the original record. For copied records, this is not correct, as the parent is always 0.

Reviews 4