Extbase MVC Framework

Not sure whether this is an extbase thing.
Might also be a bug in Core.
Had a discussion recently about this, but didn't try on my own.

all what TYPO3 does:
-------------

1 $overlayMode = ($languageMode === 'strict') ? 'hideNonTranslated' : '';
2 $row = $this->pageSelectObject->getRecordOverlay($tableName, $row, $languageUid, $overlayMode);

which calls t3lib_page::getRecordOverlay()

core in tslib_fe handles it that way

 1 case 'content_fallback':
 2     $fallBackOrder = t3lib_div::intExplode(',', $sys_language_content);
 3     foreach($fallBackOrder as $orderValue)    {
 4         if (!strcmp($orderValue,'0') || count($this->sys_page->getPageOverlay($this->id, $orderValue)))    {
 5             $this->sys_language_content = $orderValue;    // Setting content uid (but leaving the sys_language_uid)
 6             break;
 7         }
 8     }
 9 break;
10 

You can see this behaviour here: http://www.its-united.com/index.php?id=19&L=0

Look at "19. ITS Weltkongress in Wien", third article in the right column. The language is german.
Change the language to englisch, the article is shown in english language
Change the language to russian, the article is shown in german language.
But in this case, the sys_language_mode ist set to 'content_fallback;2,0'.

Before the code in tslib_fe mentioned by Georg are conditions:

1 // Request the overlay record for the sys_language_uid:
2     $olRec = $this->sys_page->getPageOverlay($this->id, $this->sys_language_uid);
3     if (!count($olRec))    {

1 // If requested translation is not available:
2     if (t3lib_div::hideIfNotTranslated($this->page['l18n_cfg']))

Therefore the content_fallback works only for whole pages and the idea is following: If the page is not translated and also in localconf is not set hideIfNotTranslated, then the whole page (not just some content elements) are rendered in fallback language. The real "content fallback" is always 0.

I tried to check the code, how hard would be to integrate proper "content fallback", but it seems you need to do changes in templavoila (if you are using it). Haven't tested it without it.

Are only the news elements affected with this behaviour or is it a general thingy with all other content elements in TYPO3?

@Oliver: Was my example helpful for you?

@Jozef: I haven't tested it without templavoila. What do you mean "you need to do changes in templavoila" ?

I think this is a dublicate of #17354

What do you think?

I don't think so, but I'm not sure.

I have test my scenario once more with TYPO3 4.6.7, TemplaVoila 1.6.1 and the Extension "News System" 1.3.2.
Here you can see the result and description of the test: http://its-united.webseiten.cc/index.php?id=33&L=0

I'm confused, sorry. Yet it seems, the conntent_fallback error only refer to the news single view and menu items (navigation / page title)!?