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.
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
