Bug #69022


Translated records can't be found when the original is hidden

Added by Daniel Dorndorf almost 9 years ago. Updated 8 months ago.

Must have
Extbase + l10n
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


If you deactivate a record and try to get the translated one you will get a: "#1297759968: Exception while property mapping at property path "":Object with identity "123" not found."

This happens because extbase always works with the uid's of the original records and does the language overlay at last.
So if the original is hidden it can't be found and so either you can't get the translated overlay.

I guess best would be to expect translated items will be deactivated too if I deactivate the original one, otherwise you have to create a single record in the target language.

Checking everytime if a record is translated would be a mess for this edge case...

Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #102578: Translated content elements can not be found when the original element is disabledNew2023-12-01

Actions #1

Updated by Markus Klein almost 8 years ago

  • Subject changed from Translated records can't be found when the orignal is hidden to Translated records can't be found when the original is hidden
  • Status changed from New to Accepted

fully agree

Actions #2

Updated by Riccardo De Contardi almost 7 years ago

  • Category changed from Extbase to Extbase + l10n
Actions #3

Updated by Tymoteusz Motylewski almost 6 years ago

  • Status changed from Accepted to Needs Feedback

Sorry for the late response. How do you get the translated record?
Can you please give some steps to reproduce, ideally a code snippet, and info about the records?
Without it I can't reproduce it, write tests and fix the issue.

Actions #4

Updated by Daniel Dorndorf almost 6 years ago


have no access to this code no more.

But as far as I can remember it was just a list with findAll() in my controller and normal product records.

I'll try to reproducs this in 7.6 or above, but in 6.2 I had the issue in other systems too.

You'll have to create a record and a translation for it, if you disable the german translation parent and call the english record in frontend you'll got an error because the translation layer wasn't able to fetch the parent.

Seems in this case the hiddden check was to strict etc.

Actions #5

Updated by Susanne Moog over 4 years ago

  • Status changed from Needs Feedback to Closed

No clear steps how to reproduce, nothing happened here for quite some time - going to close this issue now. If you still have problems, please open a new issue with steps to reproduce and a code example.

Actions #6

Updated by Daniel Dorndorf 8 months ago

  • TYPO3 Version changed from 6.2 to 11
  • PHP Version changed from 5.5 to 8.2

I encountered this issue again in v11.5.

This can be reproduced by translating a content element in connected mode and disabling the original record.
Even though the translation is still enabled extbase won't be able to fetch the translation overlay due to the disabled original.

I don't get an error message in v11, but I'm missing the enabled content elements in the frontend of my translated page.

Actions #7

Updated by Simon Schaufelberger 8 months ago

  • Related to Bug #102578: Translated content elements can not be found when the original element is disabled added
Actions #8

Updated by Benni Mack 8 months ago

  • Status changed from Closed to New

Also available in: Atom PDF