Hi all, first allow me to thank you reading this. I've searched high and low for information regarding this issue, but I haven't been able to find much information about this in DNN6. 

The situation
I'm creating a site in two languages (ES-ES and EN-US). To simplify administration I'm using modules for menus and all content instead of hardcoding them in the skin (it also seems like the best practice). The idea is to have a single instance of a module that is applied to all pages, using to the option "display module on all pages", in a given language [for example, some text at the footer of the page in spanish for the ES-ES localization and the same module, but in the EN-US localization with the text in english]

The workflow
I've managed to do this by creating a module in spanish, then clicking on the "ready for translation" button to duplicate the module in the english version of the page. Then, after ticking the option "display module on all pages" on each instance (spanish and english) of the module, the spanish module populated the spanish site while the english module populated the english site. So far, so good.

The issue
If I create a new page in either language, all the modules are duplicated. If I create a new page in spanish I get an instance of the spanish module (this is expected) but also another instance of english module with ES-ES localization (this is incredibly weird, but I guess it follows the "display on all pages" logic, although I would expect that it only applies to current localization). 

The question
Does this mean I will have to delete the duplicated instances everytime I create a new page? Because it seems like quite counter-productive hassle...

I'd be really grateful if someone could reply.

Regards

Hi Wes,

Thanks for the reply. I'm not familiar with the best practices for this situation, I would gladly accept any advise you could provide regarding a better solution.

From my trials I found out that the INCLUDE option only populates the current language (if it populated both I would've dismissed this approach), so the module IS influenced by the current language. The problem arises when creating new pages. It bothers me that it creates a new instance of the module (duplicating it for the opposite language). The best solution so far has been to turn off the includes, add new pages and the turn on the includes once again. It just seems like too much of a hassle to be the correct solution.