derekr44 wrote:

I downloaded the Spanish Language Localization pack from the DNN website.  How do I set it up on DNN?

these are the steps:

1. log on as host
2. go to the languages menu item in the host menu
3. click "upload language pack"
4. select the language pack on your local file, and upload it
5. change the portal default locale to the newly uploaded locale (in the sitesettings option in the admin menu) - this will cause anonymous/ non logged on users, to see the site in your new locale
6. change the preferred locale of the account you use to log into your site (ie admin or host). The language preferences of the user takes precedence over the language setting of the portal

thats it ....

cheers,

erik

nope, dont you just love dnn! Thank the core team for providing in (almost) everything we need!

cheers,

erik

theres another method thats very useful, especially if you're deploying multiple packs (or other resources). Simply copy/ftp the files to the Install folder. It contains a number of sub-folders, one for each type of uploadable resource. Copy your spanish language pack zipfile into the Language subfolder. You can now either wait for the ResourceInstaller scheduled task to automatically install the resources for you (the default is every 30 minutes), or kick off the task manually by using www.mysite.com/Install/Install.aspx?mode=InstallResources . Multiple files can be placed into each folder, and a status report will be generated at the end.

I've used this recently to install a dozen language packs,  a few custom skins and some modules, all in 1 step, which hugely impressed the customer.

Cathal

sorry, just checked and the ResourceInstaller scheduled task is not running by default, so either enable it, or use the explicit url I mentioned.

Cathal

Thanks for the tip Cathal, that option was kinda shimmering at the edge of my mind ...

cheers,

erik

the language name / key pair is created upon installation of the resource pack. Of course any installation into dnn works only if the aspnet user has write rights in the root directory and below ...

cheers,

erik