Hello!
While this solves one big issue (allow to fill up the content for a language before it's visible) it still means 2 code changes (and webserver restarts) are required:
- to add a new language, with public False
- to pass that language to True
This means a customer would have to call the developer for each new language; the dev would have to log-in to the server (often his own), push a tiny code change, restart, do this again when it's done, etc.
Wouldn't it be better to have those settings for the languages through the admin?
This would imply that all possible languages are, by default, added to the setting
LANGUAGES; a main Language of course should also be set. Then all CMS languages are selected - and configured - in the admin!
Wheter
CMS_LANGUAGES could still be used for a sensible default or not (eg. to populate the corresponding database table /if empty/ and for easy initial migration) is left as an option.
What do you think?