Project

General

Profile

Bug #103582

Updated by Markus Klein 8 months ago

Hi,  
 Since the latest update to V12.4.14, the "fallbacks" field from the SiteConfiguration for languages no longer seems to work. 
 Previously I had the following configuration in my languages: 

 <pre><code class="yaml"> 
 languages: 
   - languageId: 0 
     enabled: true 
     title: Deutsch 
     base: 'https://www.darf-ich-mit.de/' 
     locale: de_DE.utf8 
     navigationTitle: Deutsch 
     hreflang: de-DE 
     direction: '' 
     flag: de 
     websiteTitle: '' 
     deeplTargetLanguage: DE 
   - languageId: 1 
     enabled: true 
     title: Polnisch 
     base: 'https://www.fellow.dog/pl/' 
     locale: pl_PL.utf8 
     navigationTitle: Polski 
     hreflang: pl-PL 
     direction: '' 
     fallbackType: strict 
     fallbacks: '' *fallbacks: ''* 
     flag: pl 
     websiteTitle: '' 
     deeplTargetLanguage: PL 
   - languageId: 2 
     enabled: true 
     title: Englisch 
     websiteTitle: fellow.dog 
     base: 'https://www.fellow.dog/' 
     locale: en_US.utf8 
     navigationTitle: English 
     hreflang: en-US 
     direction: '' 
     fallbackType: strict 
     fallbacks: '' *fallbacks: ''* 
     flag: en-us-gb 
     deeplTargetLanguage: EN-US 
 </code></pre> 

 The MainLanguage works, but all other languages only render an empty content area. 
 The remedy is to define "fallbacks: '0'" everywhere, but this is a behavior I don't want because I only want to display data records for which a translation exists 

 I reverted the update back to 12.4.13 and it works again.

Back