TYPO3 Core

I observed the same problem. Then I tried the suggested patches but for me they don't Work. (I use Typo3 Version 4.12)
Has anybody another solution for the problem?

they should work.

did you set new setting:

config.sys_language_fallBackOrder=1,0

Hi Daniel,

I used: config.sys_language_mode = content_fallback; 1,0
Why did you change this config to
config.sys_language_fallBackOrder=1,0
I expected the patch to do the same thing as typo3 should do. So I used the normal config.
Now it's working.

Thanks.
Hope this bug is solved in the new Typo3 4.2.0 Version.

greetings

Sareen

Its because the sematic difference
config.sys_language_mode = content_fallback; 1,0

controls the content fallback, and the fallbackorder is not implemented in a way it could easy be used for a common fallback order.

I my opinion having that common config parameter is more clear. (It changes not only content behaviour - which can also be set to something diffrent than content_fallback - but changes common language fallback)

thanx daniel!! works perfect. i also think it's better to define the fallback order in an own config property.

Hi Daniel,

your patch is perfect, thank you. I played around with it for quite some time now.
There remains only one problem with realUrl. The text in the Url still has not the correct language fallBackOrder.
Is there a solution to this?

greetings

Sareen

Seams same problem occurs with:
pi_getFFvalue()
- used for FlexForm
Language fallback in steps seams to be quite some problem

Is this coming up in 4.2? Does anybody know?

still not in 4.2.1, please integrate this!

I will soon publish the extension langaugevisibility which resolves this and a lot more:
http://www.typo3-media.com/extensions/multilanguages-websites-with-typo3-languagevisibility.html

confirm: the extension works great, we use it in two projects! This has to be integrated into the core!

Is this extension for download and test already somewhere?

@ronald: the extension is attached to this bug report: http://bugs.typo3.org/file_download.php?file_id=2929&type=bug

as far as I see, this is "just" the bugfix. And there will be an huge extension "languagevisibility" that solves this bug and adds a lot of features.

but shouldn't such thing be integrated in the core?

I'm realy carefull with such core changing extensions, they can lead to other problems. Is it tested with TV, Workspaces and all the other needed TYPO3 things?

sure its tested with workspaces / templavoila / even introduce new templavoila features

the extension is availabe at forge: http://forge.typo3.org/projects/show/extension-languagevisibility

sildes:
http://www.typo3-media.com/extensions/multilanguages-websites-with-typo3-languagevisibility.html

thanx!! works like a charm!

Hi Daniel,

I just test your extension: languagevisability
- it seems to work fine so far, but the bug described here is not resolved, is it? Or is there a special TypoScript Configuration necessary to resolve this bug?

And it seems not possible to install that extension together with the patch you proviede here: T3X_danp_languagefallback_patch-0_0_0-z-200708151515.t3x

Schould this patch not be integrated in your extension languagevisability? Am I getting something wrong?

greetings

Ron

P.S.: For me correct language fallback in menu's is more important, so I now only use the patch and not the extension.

Daniel, can you update the patch for TYPO3 4.2 please? Additionally, please check my patch in #19114.
It seems to work quite different than the solution that you have come to. What it basically does is the provide content-fallback even if the page record has been translated, but not all content on it.

Any feedback is appreciated.

- michael

It would be great if somebody could writhe a manual on how to implement translation handling for records in extensions. But a way which supports the full features of translation handling in TYPO3.

Is this integrated in the ExtBase persitence layer?

I attach another patch, which fixes everything.

According to the docs menu and page title should be translated as well when content_fallback is in use. This means that the page record and $TSFE->sys_language_uid should be set to a fallback language. Indirectly this is confirmed by TSRef in the description of sys_language_uid:

<blockquote>Internally, the value is depending on whether a Alternative Page Language record can be found with that language. If not, the value will default to zero (default language) except if “sys_language_mode” is set to a value like “content_fallback”.</blockquote>

and

<blockquote>The system will always operate with the selected language even if the page is not translated with a page overlay record. This will keep menus etc. translated</blockquote>

So the patch checks if the fallback is set and changes page record and sys_language_uid to be the one from fallback, which makes the behavior identical to described in TSRef.

Result: menu in the fallback language, page title in the fallback language, links still stay with user's choosen language.

One possible drawback could be with language selectors. If they use $TSFE->sys_language_uid, they will show a fallback language. Instead they should use the value of "L".

The problem is´nt fixed in Typo3 4.5.2 but the patch works there.

amareco wrote:

The problem is´nt fixed in Typo3 4.5.2 but the patch works there.

what patch? dmitry's?
doesn't work for me (4.5.3)

i don't understand why this isn't part of the core...

Hi,

Dmitry Dulepov wrote:

I attach another patch, which fixes everything.
...

I checked both solutions.

While danp_languagefallback_patch adrresses the issue the patch from Dmitrij does not at all.

The main problem is not translation of the currently selected page record (while in content_fallback mode), but rather falling back while translating menu items for other pages which are present in the menu.

Dmitrij's patch works only with currently selected page, while danp_languagefallback_patch reimplements getPageOverlay which actually provides menu biulding class with translated page records.

Any news on this issue?
It`s still reproducable in 4.6.6

Hi Stefan,

meanwhile I tested Dmitrys patch - It solves the main problem with non translated navigations, but there are strange side effects I can`t discribe.
I will give your patch shortly a try - would be great to see this in core.

Hi Stefan,

I set up an test installation and imported my site (12 Languages!).
Everything is working as expected after applying your patch.

From my humble point of view you maybe could submit it to Gerrit.

PS: I think this is also related to #20623

Hi Henrik,

I fixed a possible edge-case in the patch and will upload this to one to Gerrit now. Please review it again carefully, just to be sure that nothing else slipped in and don't forget voting in Gerrit. Thanks in advance! :-)

Edit: Everyone and not just Hendrik is invited to do the same. ;-)

Thanks Stefan,

+1 by reading - Is there a way to download the changes as patch-file to apply it to my local installation?
I did not really deal with the new review system before. Sorry.

After a short test I will give my vote in Gerrit.

Why not using languagevisibility? :-) Its all working there and a lot of more things..

Just my 2 cents :-)

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Hi Daniel,

Your extension does lot's of more stuff and that's exactly the problem. Also I didn't understood the code and it didn't worked for me like I had expected it (just install it, define the fallback order and go).

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Push :)

Stefan and Ronald, could you please also look at the new patch from Markus?

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Hi together. Just tested the patch on a page with > 40 languages (on a patched 4.7.2). Works fine so far.
But it seems that it ignores l18n_cfg setting (2) in page-record (Hide page if no translation is available).
So I don't have any chance to explicitly hide certain pages that I don't want to show in fallback.

That one should be patched in t3lib_page imho... Thanks :)

Really? This setting works for me!? Please test the latest version of the patch. Will be there in a few minutes... :-)

Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 6 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 7 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 8 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 9 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 10 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 11 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 12 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 13 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 14 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9937

It seems to me this is a bug in typo3 6.0 also

Patch set 15 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Patch set 16 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Patch 16 seems to work fine for me. Thank you

Camelia M wrote:

Patch 16 seems to work fine for me. Thank you

Actually, after I apply this patch, localizations for jfmulticontent stop working. Not sure if this is the only one that stops working, but this is the first I noticed.

Camelia M wrote:

Camelia M wrote:

Patch 16 seems to work fine for me. Thank you

Actually, after I apply this patch, localizations for jfmulticontent stop working. Not sure if this is the only one that stops working, but this is the first I noticed.

I forgot to mention that I did replace getRecordOverlay function call with getRecordOverlayWithFallback

Patch set 17 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Patch set 18 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Patch set 19 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Patch set 20 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Patch set 21 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/9937

Has anyone a patch for TYPO3 6.0.4? Patch set 21 isn't working in this version.

Stefan Regniet wrote:

Hi together. Just tested the patch on a page with > 40 languages (on a patched 4.7.2). Works fine so far.
But it seems that it ignores l18n_cfg setting (2) in page-record (Hide page if no translation is available).
So I don't have any chance to explicitly hide certain pages that I don't want to show in fallback.

That one should be patched in t3lib_page imho... Thanks :)

Hi all,
we applied the patch set 21 to our 6.2 installation, but we also had the problem, that it ignores the l18n_cfg setting as mentioned above.

To fix this(at least for the basic HMENU) we changed line number 975 in the file typo3/sysext/frontend/Classes/ContentObject/Menu/AbstractMenuContentObject.php.

In function filterMenuPages after:

if ($GLOBALS['TSFE']->sys_language_uid && GeneralUtility::hideIfNotTranslated($data['l18n_cfg'])) {

-       if (!$data['_PAGES_OVERLAY']) {
+       if (!$data['_PAGES_OVERLAY'] || ($data['_PAGES_OVERLAY_LANGUAGE'] != $data['sys_language_uid'])) {

why this bug isn't resolved in typo3 6.2 yet?
is there any extension to fix it?

There is a patch under review. Maybe that works for you? But it was mentioned in the review that somebody still had an issue with it. And currently it seems to be handled as a "feature" (won't have this for 6.2 then unfortunately) and not as a bugfix.

Patch set 22 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 23 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

So ist there any current workaround for TYPO3 6.2?

Not really, but you can apply the patch yourself in 6.2 if you know how to do that. AFAIK there are not many differences, so you shouldn't get any errors.

But then I can't update the core when a new minor-version is published. Aren't there any other solutions? Isn't there any bugfix for 6.2?

Marc Hirdes wrote:

But then I can't update the core when a new minor-version is published.

You can always re-apply the patch on update. In case you are using Composer the composer-patches-plugin might prove useful here.

Aren't there any other solutions? Isn't there any bugfix for 6.2?

Since the change has not been merged yet, there cannot be a bugfix release including it.

I don't use composer. For my local distribution it is only possible to set all changes manually in files?

Is it possible, that the next bugfix release include it?

Marc Hirdes wrote:

I don't use composer. For my local distribution it is only possible to set all changes manually in files?

Not necessarily if you use the patch command. :-)

OK I used the patch command. First it looks ok. But RealURL returns also a bad URL and another Extension provides also the wrong title. In this https://forge.typo3.org/issues/18062 Issu is said, that RealURL expects the correct Lang-Param from core.

Am I the only one with this problem? I meen in many multilanguage pages I think they would have different fallbacks for different languages (austria -> german, us -> uk etc.).

Are there experiences with other extensions? And will this patch include in the Core maybe? Thanks a lot for support.

I found a fix, but realurl can't handle the resulting urls with fallback names inside them. The root cause is that sometimes getPageOverlay is called with an explicit language parameter and this means to the function that the user want's exactly this language. Changing this behaviour will automatically be a breaking change.

Patch set 24 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

To handle RealUrl I translated every page. So the title of the page is correct and also the URL. My last problem is with Gridelemnts. When I have an element inside of antother element the fallback is the default language. Other elements are shown correct in the fallback language.

OK, when I change in Gridelements.php line 161 getRecordOverlay to getRecordOverlayWithFallback it works fine.

$child = $GLOBALS['TSFE']->sys_page->getRecordOverlayWithFallback('tt_content', $child, $GLOBALS['TSFE']->sys_language_content, $GLOBALS['TSFE']->sys_language_contentOL);

Maybe the funtion getRecordOverlay can allways get the fallback, if no translation is given?

Patch set 25 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 26 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 27 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 28 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 29 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 30 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

Patch set 31 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/9937

I will give it a try maybe tomorrow. This bug is so annoying and needs to be addressed and tested to find its way to 8!
Thanks for your patch, Nikolaj.

YES. Patch is working for us also in two 7-LTS-instances.

Nicolaj, can you push it please to gerrit?

the menu dont works for sys_language_mode = content_fallback; 1 in TYPO3 8.7.10
AFTER 10 years :D

Im also having this problem with 8.7.13, any help?

Same here in 8.7.19. content_fallback has no influence on pages

Alex Kellner wrote:

Thank you all for your work.
Here is the patch for TYPO3 8.7 (tested on 8.7.19 and .20)

Can you post this to our review system please? See the Contribution Guide for details.