New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!


Return to previous page

  • 4/7/2015




Last updated long time ago



(Enter the content of this article below)


Superusers ("Host") may specify Localization options, offered to all Web Sites of the current DotNetNuke installation.

Those Host options for Localization are included in Languages item in Admin menu (default location). Besides International Portal Configuration, presented to site administrators, the following superuser options are available:
  • Add / Edit or delete a language
  • Install a language pack
  • Verify intalled resource files for missing files or keys
  • modify static resources for a language pack (system level)
  • override static translations for all web sites of the current DNN installation (host level)
  • Create a language pack
  • enable / disable the option to use Content Localization in any of the web sited, belonging to the current DNN installation.

    To add a language, you need to select the appropriate Locale from a dropdown list of all .Net cultures, installed on the current machine. A culture consists of the ISO code for the language (e.g. "en" for English), the country where it is used (e.g. US for United states) and optionally a character set. If your desired culture is missing, you may follow these instructions to create your custom culture. For each language (besides System language), you need to specify another installed language as fallback language, which will be used, if a language key is not present in the current language. You may edit fallback language lateron, if needed. Be careful deleting a language, it may be used by any of the sites in your installation.

To install a language pack, you may follow the command or use Extensions item in Host menu, and install it like any other extension type. Afterwards you may use the resource file verifier to check for missing files, missing keys, obsolete files or keys or translated resource files, older than the system resource files it translates. This will be helpful, to update language packs after an upgrade of the DNN version or an installed module.

To modify resource files on system or host level, use the Language Editor.

To create a language pack, use the module command in Languages or in  Extensions item in Host menu. You need to select the appropriate component(s) - DNN will select associated resource files automatically - and fill in information about the author.

If you Enable Content Localiztion (option is located in Host Settings modules until DNN 6.1.0), admins will get an option to convert all pages of their web site into language specific ones and create clones for each enabled language. Note: this operation cannot be reverted!!!
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out