Installation of the Module/SkinObject is done in the same way as any other DotNetNuke® Module: select the option 'module definitions' from the 'Host' menu, and select "Upload new module" from the action menu. Select the PA zip file on your local computer, and click "upload new file". The selector is now installed. The language selector can be used as a skin object or as a module. You can see in the sample skin how you can use the selector as a skin object.

The package also contains one sample skin, derived from the standard dnn-blue skin, you can install this skin in your portal to start working immediately with the language selector. Mind you, the sample skin also contains references to the Apollo PageLocalization module. If you did not install Apollo PageLocalization, the skins that have "PL" in the name, will not work as expected.


If you are using a previous version of MLLanguageSelector, you can just install this version in the normal way. However, due to the changes in rendering of the selector, if you are using the language selector as a skinobject, and the admin skin contains a language selector, you will see a viewstate load error. This error will look something like this:

Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request.

Once you navigate to any other page in your portal, this error will disapperar, and everything will be ok.

Last edited Jul 11, 2011 at 6:10 AM by erikvb, version 1


No comments yet.