"fallbackType: free" in the config.yaml seems not to work with displaying sys_categories in the frontend. Backend works as expected, but in the frontend default and foreign language are shown together.
My news template shows a list of categories to filter news by categories. With "fallbackType: strict" this works fine, but not with "fallbackType: free": In the default language the list is shown in the default language, as expected. But in the foreign language we get a list of all translated categories and additional all categories in the default language. In single view of news i get the category list bound to the news always in the default language, never translated.
Is this a feature or a bug? How can i work around? I need "fallbackType: free" because my client wants to publish news in the foreign language without a news in the default language. So i can't simply switch back to "fallbackType: strict".
(TYPO3 10.4)
Thanks!
Related
I am working on a TYPO3 v10 LTS website with integration of the news extension v8.3.0. Many news are assigned to multiple categories and they are displayed on different detail pages according to their assigned categories. Now I would like to define one categories as master and use this category for the generation of canonical links to avoid duplicate content problems. On an older version of the website (TYPO3 v7 LTS) I used the solution explained here: https://www.typo3.net/forum/thematik/zeige/thema/116056/
I'm not so experienced with TYPO3 v9/v10 LTS yet, but I think that there must be a solution with routeEnhancers.
Any hints are welcome.
You need no route enhancer, just use the basic configuration of EXT:news.
one solution would be: for detail-view (show) always use one page. in this way each news will have a unique url. (problem: you can't ´return´ to the former list view with a hard link[1], as you don't know from which list you came)
2nd: configure a show-page with your news-categories: this page will be preferred for detail view (it always will be the first category) and each news will always be shown on this category detail page. (no ´return´ to the original list as above)
[1] you can't use a page as link target, but you can use javascript:history.back()
I've been building a TYPO3 website. I wanted to use the multi-language capacity of TYPO3 and get acquainted with the CMS. I'm using V.9.5.6 at the moment with the Introduction Package.
I followed the manual on multi-language setup here : https://docs.typo3.org/m/typo3/guide-frontendlocalization/9.5/en-us/Index.html
When switching languages, the page refreshes but no visible changes occur.
I deleted the original "German" et "Dansk" languages, then added "French" and "German". I used the contact page as proving grounds.
I added translations in germand and french from the original english page I built. There's only a header and a contact form. In english, it reads "contact form". In german and french it should read respectively "Kontaktieren Sie uns" and "Contactez-nous".
The languages UIDs are 2 for German and 3 for French. The template, in the languages section, has "auto" for the list of languages and it pulls correctly the 2 I added, in the correct order.
In a properly setup website, if default language is English, and I click on the "German" or "French" language button at the bottom, the page should refresh and display the content translated in the language I selected and have the selected language in bold at the bottom of the page.
When clicking on the bottom links, it adds the correct L= parameter and the page loads but no visible change occur on the page. Even the language link at the bottom of the page has "Default" in bold instead of whatever I clicked.
There is NO error message when clicking on the language buttons.
I'm pretty sure this is not the standard behavior of a TYPO3 multi-lingual installation. What can cause the CMS to not fetch a translated content OR fail to get the language change information from the parameters passed in the URL ?
I'll try to answer this vague question.
Usually there are three pitfalls you should look at:
realurl (or routes in v9) here is a nice gist: https://gist.github.com/koehlersimon/9dcbabb6b1b2adcbc84db96fd144fb08
TypoScript settings for the languages: https://docs.typo3.org/m/typo3/guide-frontendlocalization/9.5/en-us/TyposcriptConfiguration/Index.html#typoscript-configuration
proper .htaccess in connection with [1.]
I also suggest to update to v 9.5.9
There have been plenty bugfixes since v 9.5.6 and updating within branch 9.5.X is really easy and non-breaking!
i have a Problem regarding TYPO3 and the extension tt_news.
I have a multilingual Site with 2 Languages, english and german. The news on the site are generatet by the extension tt_news - everything is working fine except one thing:
When i put an internal direct link in the news body, the language parameter is lost. So when the user klicks on the Link, it always comes back to the default language. How can i make TYPO3 generate the links with the selected language parameter, or how can i add them?
I'm not a big typo3 expert nor have I access to typoscript options at the typo3 instance I'm working with (It's a very big site and I don't have the authorization to do so). So I hope this question fits on stackoverflow (Please don't hate me if it does not, I'll happily post this on another site)
What I'm trying to achieve is:
My website has two possible translations (German and English). I see
that it's possible to switch languages during surfing through
clicking the "German"/"English"-Button
On the website are also informations about our staff (who may not be speaking german)
If one staff member doesn't speak german, I copy redundantly their english profile on the german translation mode (that it appears, because otherwise it doesn't - might be no good style, but it's better than not having them appear at all)
I'm not happy with these kind of redundancy since it means that I have to do the same action twice on the exactly same content. Does there exist a possibility in the backend of typo3 where I can set that the german translation shall be the exact same as the english content?
I hope my question is clear, thanks a lot for your help.
As you say you don't have access to typoscript templates etc, I guess you are not an integrator/developer in this project, but an editor.
Your only way to achieve an automatic "fallback" behaviour is asking the person who takes care of the site's configuration to set that up for you.
But if that's not possible, you can still use the "insert records" content element (german: "Datensatz einfügen") to avoid duplicate entries.
This content type is not in the wizard when you create a new content element. But you can create a text element and then change the type to "insert records". Now you can select another record which is then mirrored here:
You'll have a similar amount of work when setting it up, but you won't have redundant text, which is way better.
If this content type isn't available either, I would insist on the administrator enabling it for editors - it's very useful to maintain a site's content healthy.
Would be helpful to see your TypoScript configuration. Maybe theres something wrong with the sys_language_mode. Given that the sys_language_uid of english is 0 (which means its default language) and german is 1, the default behaviour should be, that german translations are shown, if available. If a translation is not available the default version of a content element is shown. However, you can change this behaviour with Typoscript:
config.sys_language_mode = content_fallback ; 5,3,1
This will set the content fallback of an content element (which is triggered if no translation exists) to sys_language_uid 5, if its not available in that language sys_language_uid 3 will be displayed etc.
Maybe your installation is set to
config.sys_language_overlay = hideNonTranslated
This will hide non-translated content-elements. Remove this entry to enable content fallback again.
You can always check the current Typoscript in the Template module via the TypoScript Object Browser. However, to really get help you need to share your TypoScript language configuration. The behaviour you describe is not the default behaviour, so its configured somewhere.
Here I have tt_news 3.0.1 and a TYPO3 4.3.1. There are tt_news articles translated. If I look into the database (tt_news_cat_mm) than in the default language there are the categories 1,2,6,8 assigned. If I look on the translated article it only has the category 1 assigned.
In my opinion the translated article should have the same categories as the one in the default language. If I look into the backend I can only change the categories in the default language. There is no option available in the translated article.
Is that an error for the old tt_news extension?
Update:
It seems that the categories are only taken for the first translation. If you change the categories later they don't get updated in the translated version. Very annoying ...