Bug #89413
closed
Cannot save page with translated page resources (media)
0%
Description
Hi,
after upgrading from Typo3 8 LTS to Typo3 9.5.9 LTS translation handling of page resources (media) get´s totally broken as soon as I am saving the page the first time in Typo3 9 LTS. The page cannot be saved any more always with the same error.
public/typo3/sysext/core/Classes/DataHandling/Localization/DataMapProcessor.php" => 626 => #1486233164 RuntimeException Child record was not processed
This does not occur with newly created pages, only with pages which have already existed before the upgrade to Typo3 9.
It seems this is related to translated page resouces .
Situation:
- The page exists with the default language (English)) and multiple translated languages, having the same page media in all languages
- Each translation has the same page resources as the default language. Typo3 has set the media i10N_state to parent.
- When I save the default language, the above mentioned error occurs. Afterwards only the default language has page media left but duplicated. The page media in "German" is empty. It seems that Typo3 moves the page media from German to English and runs in an error before beeing able to cleanup the duplicate items.
Files
Updated by Christian Ebert about 5 years ago
- Category changed from File Abstraction Layer (FAL) to Localization
I could provide a sql dump for easier analysis on a private basis. I cannot attach it public here. In case just let me know how I can submit it.
Updated by Christian Ebert about 5 years ago
- File 16-10-_2019_10-20-25.jpg 16-10-_2019_10-20-25.jpg added
so far as I can see, the problem is l10n_parent beeing 0 in sys_file_reference for all sys_language_uid .
Updated by Michael Stopp about 5 years ago
I can confirm this. As a quick fix after the migration I used a query like this:
UPDATE sys_file_reference r
JOIN pages p ON r.uid_foreign = p.uid
JOIN sys_file_reference r2 ON p.l10n_parent = r2.uid_foreign AND r.uid_local = r2.uid_local
SET r.l10n_parent = r2.uid
WHERE r.deleted = 0 AND r.tablenames = 'pages' AND r.sys_language_uid > 0 AND r.l10n_parent = 0;
This is probably far from perfect, but it seems to have done the trick for me.
But obviously that's not the solution to the original problem. It's just clean-up after the mess has happened already...
Updated by Benni Mack over 4 years ago
- Status changed from New to Needs Feedback
Can you let me know if the issue is fixed with TYPO3 v9.5.14?
It is often related to the fact that a record with language=0 has a child record with language>0 - which both then get saved.
Updated by Christian Ebert over 4 years ago
Because nobody was caring about the problem when it came up I had to resolve it on my own (similar to Michael Stopp). So I cannot test this anymore
Updated by Michael Stopp over 4 years ago
Similar situation here: I don't have a freshly migrated site at hand (and nothing planned in the near future), so I can test this right now.
Updated by Oliver Hader over 3 years ago
- Status changed from Needs Feedback to Closed
Seems it cannot be reproduced anymore for further analysis.