Try our conversational search powered by Generative AI!

Content Blocks not respecting Fallback Language


It seems like the fallback language is not being respected for content blocks.

To test this out, we have a site with 'de', 'de-DE', 'de-CH' and 'de-AT' with the last 3 locales configured to use 'de' as the fallback language. Then we took the following steps to test it out:

  1. We created a content block in 'de-DE' and provided the text "placeholder in de-DE. Originally created in de-DE".
  2. We then translated that content block to 'de' and modified the text to be "placeholder in de. Originally created in de-DE".
  3. We create a new content block in 'de' from scratch with the text "placeholder in de. Originally created in de"
  4. We created a page in 'de-DE' and then translated that to 'de'.
  5. The first block (created in de-DE) was added to a the page in de-DE
  6. The 2 blocks were added to the 'de' version of the page.

When we browse to the various locales, we get the following behaviour:

/de/ (expected behaviour)
"placeholder in de. Originally created in de-DE"
"placeholder in de. Originally created in de"

/de-CH/ (unexpected behaviour)
"placeholder in de-DE. Originally created in de-DE"
"placeholder in de. Originally created in de"

/de-AT/ (unexpected behaviour)
"placeholder in de-DE. Originally created in de-DE"
"placeholder in de. Originally created in de"

/de-DE/ (expected behavior)
"placeholder in de-DE. Originally created in de-DE"

As you can see, we expected de-CH and de-AT to show the translated content from 'de' for the first content block but they are showing the original text from de-DE

Anyone come across this before or have any thoughts?

Jun 20, 2013 18:00

I should note that before anyone else does is that 'de' could be used as the master language to build from but in our actual solution, en-GB will be the 'master' language that is used and based on the above observations, de-CH and de-AT would be in English then which is not desired at all :)

Jun 20, 2013 18:49

Is this in EPiServer 7.1?

Jun 20, 2013 20:35

Correct. This is 7.1

Jun 21, 2013 10:59

I'm really not sure but,.. maybe this is your problem:

When we create a new page, we do this mostly in the fallback language. This way all other language's automatically have a fallback page. When switching to another language you get the option to translate but it also tells you it's currently falling back to the fallback language.

In your case you created your page in the language that's not the fallback language. I can imagine this could be the source of the problem, not sure though.


Jun 21, 2013 15:14
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.