First Time Install
Make sure you've completed the core installation of DotNetNuke and that you have host access to the installation. The basic requirements include IIS on Windows as well an MS SQL Server (2000+ or Express).
Download the install packet and extract the contents of the zip file. You’ll only see three directories. These are numbered and the components within should thus be installed according to that order, starting from one (1).
Access the DNN interface and login in as a host. Under the host tab go to Host-> Host Settings browse down to [+] Advanced Settings, expand this and expand [+] Other Settings. "File Upload Extensions" contains a list of files that are permitted. We need to ad js to that list. Simply add “,js” at the end of this (exclude the quotes).
We’ll now add the modules. Go to Host->Module Definitions and select "Install New Module." Upload each item from the "Upload [Module]" directory in the zip file. A log of the updated files will be generated for each zip file you upload. You shouldn’t see any errors but feel free to report any problems if you do.
Current modules are as follows:
- Amber Alert (will change when the RSS component is finalized)
- Campaigns (need to be updated to us JS interface as noted in the last meeting)
- SSILinks – Our extension of the links module. Removes table based structure and provides a <ul> <li> list of elements instead.
- SSISkinObject – not properly labeled but it contains the dll files that generate to top navigation.
- SkipTo - Configurable Skin Container offering "Content | Footer" links and a configurable component that can be used for custom Accessibility and other links.
- ToTop - Skin Object preconfigured with the back to top link. Customizable to allow any other set of links the administrator desires.
The containers are basically the mini skins that wrap around each module. They can be changed individually for each component or set as default across all pages within a single portal. To add the containers: go to Host-> Skins and select "Upload Container" (at the very bottom in the default look and feel). You’ll find that we only provide one file.
After validating has completed, return to the skins page and add the Skin from the "Portal[Skin]" directory by selecting to "Upload Skin". If you did this out of order or if you forgot to add the js extension to the permissible files, you’ll see that the entire javascript directory will be excluded from the upload. This is obviously, not desirable. The step can be repeated if necessary.
You’ll be able to set your skin after this. From the Skins drop down select Ca-Portal and apply "2 column-main page" to get started. I suggesting also selecting the "text header – no background" container as the default. Using the "internal" skin will cause the CA branding, governor images to be removed and the Google search engine will be replaced by the one provided by DotNetNuke.
You may return to your home page from here. In order to use the proper Links in the body of the template, you’ll have browse up to the control panel (at the top), select to add the SSILinks module and select your pane, LeftNav_TOP/LeftNav_BOTTOM. At this point you’ll be able to add individual links.
About the zip files provided:
You’ll notice the Container and the skin zip file names are exactly the same. This is intentional.
Contact the developers
We'd be happy to hear from you. Let us know how we can help.
- Steve Rodda: srodda@stanfieldsystems.com
- Rogelio Ortiz
Previous page: California Redesign
Next page: Upgrades