Sebastian, I'm not that sure this will work. I'm returning from some sunny days on the beach so I'm still not 100% but ...

Disabling a language will only remove it from all places where users can select it. But it will not make the resource files "invisible" to the core, so it by any mean someone requests a page using any "disabled" language it will work.

I think what you suggest has not been taken into consideration yet, will take a look.

Vicenç,

thanks for your correction. I have not thought of this being possible: imho "disabled" should not only disable the selection option, but also all framework and content. That was my first thought, but now I am thinking of the situation, having a multiligual site running with DNN 3.7.2 (e.g.), and I want to support an additional language. How do I disable for users the option to select the new lanugage, while I am still not finished adding content? so maybe the disabeled language should only prevent access from non-authenticated users; this would be consistent with premium modules: if I revoke access to a module for I specific site, the module is neither deleted from pages, where is is already placed nor disabled. It only cannot be added to pages any more, as it is not displayed in the selector box.

In both cases I would like to have a help text and confirmation message, stating this situation after disabling a language/module, so the admin get to know the consequences.

Sebastian