I’ve already figured out how to link views to content language by the Content: Language
filter. I know that I can create a second view to use as the No Results fallback and use the Global: View area
to feed the other in. But to do this I have to:
-
pollute my site’s blocks with Localized and Unlocalized duplicates and hope the client understands that they should only enable the Localized block.
-
make sure to maintain a duplicate of the original with only the
Content: Language
filter changed. -
tolerate a full second set of queries to generate the block? Some blocks are ordered by random, so they can’t really be cached well.
Isn’t there a better way to do this?
Also, I know I can use the rearrange feature on the languages to set up conditions like:
Content: Language (In user's current language) OR Content: Language (In default site language)
But the issue is that then these languages are mixed. I need the default site language to appear only when there are no nodes in the current user’s language.