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 On Wed, Sep 30, 2015 at 11:37 PM, Eduardo Rivas <[email protected]> wrote: > 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 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 > [email protected]. > For more options, visit https://groups.google.com/d/optout. -- 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.
