Bug #29293

Translated Fields with Relations not showing when l10_mode exclude is used

Added by Matthias Krappitz over 1 year ago. Updated over 1 year ago.

Status:Closed Start date:2011-08-27
Priority:Must have Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Has patch:No Tags:
Votes: 0

Description

If I set the following in the TCA for a field, wich is a relation to another table, it means that this field won't be shown and translated in a translated child records of the master language record:

$TCA['tx_travel_domain_model_trip']['columns']['positions']['l10n_mode'] = 'exclude';

But when I later output the object the getter for positions returns nothing even if in the master language records there are values in this field.

The l10n_mode set to exclude only works for fields that are no relations to other records.

History

#1
Updated by Marc Bastian Heinrichs over 1 year ago

  • Target version deleted (4.5.6)

#2
Updated by Matthias Krappitz over 1 year ago

I have to revise my last sentence - this does not even work for fields that are no relation, it generally does not seem to work.

I'm using TYPO3 4.5.5.

#3
Updated by Marc Bastian Heinrichs over 1 year ago

  • Status changed from New to Needs Feedback

This overlay is done by core functions. You could exclude a misconfiguration of the language overlay settings?
e.g. config.sys_language_mode is not strict and $TCA['tx_travel_domain_model_trip']['ctrl']['languageField'] is defined?

#4
Updated by Matthias Krappitz over 1 year ago

Hi, thanks for pointing me into this direction. The whole thing was actually caused by config.sys_language_mode set to strict, because I didn't want untranslated trip records to show up. This lead to all fields set to l10n_mode to exclude and having relations (in our case to dam images) being empty. Once the systm was set to config.sys_language_mode set to content_fallback the dam images were showing.

Still I don't think this situation is desirable. I would always want fields of the model to show up, when they've got set l10n_mode to exclude while I don't want untranslated models to show up. I guess there is nothing we can do about this, since this a core behaviour. Well we could bypass this behaviour in extbase for fields set l10_mode to exclude, but this would also be kind of dirty, i guess.

So you can close it if you think so.

#5
Updated by Marc Bastian Heinrichs over 1 year ago

  • Category deleted (Extbase: Generic Persistence)
  • Status changed from Needs Feedback to Closed

no bug in extbase.

you could have a look at the languagevisibility extension.

Also available in: Atom PDF