Disable translations fallback

[Ilian Iliev]

I posted this originally on github as an issue, but Stephen advised that this is a better place for discussion, so here it is:

Me:
Currently if you setup the CMS to use multiple languages and then try to open a page that is missing translation for the current language there is automatic fallback to the default language.
E.g. page /en/about/ /de/about/ will show the same "en" content if there is not "de" translation.
I believe that this should be either configurable or should raise Http404 by default due to the missing translation.

Stephen:
What you're talking about then is having different navigation structures per language, which is something you would implement by using multiple sites (with a site per language) rather than one site with multiple languages.

Me:
Correct me if I am wrong but isn't the idea of multiple sites to have different domains, and different structure, and templates etc.
I can see the multisite usage for example for a big company that has separate sites for different product and wants everything in a single place but having multi-language site does not sounds like it.
Also seen the wrong translation on the website, with the URL and everything still pointing to a different language version is a bit weird, at least to me.

[Eduardo Rivas]

Well, it seems like you are looking for sites with different structures.
In a 1-to-1 site, you don't want to have a page translated into one
language but not into the other. For independent page trees, independent
sites are better.

There's also the problem of knowing what a "missing translation" is,
since all translation fields are optional. Should we check for a
translated title, translated content, translated slug? What about custom
pages defined by the developer?

In the meantime, you could implement what you want as a page processor
or a middleware. Those would be fairly easy to distribute and test
afterwards.

[Ilian Iliev]

I would generally agree but how about if we are just adding a new
language to the website. It normally takes a while to get all pages
set with the proper content and so on.
But on the other side you are right that this is much more complex
than just the page itself because it also affects the navigation
items.
--
Ilian Iliev, PhD.
Software Engineer

Mobile: +46 728 605 387
Website: http://www.ilian.io/
Skype: eng.ilian_iliev

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Mezzanine Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/mezzanine-users/kOHopiWsBDk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-use...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.