- How do I log in to my site?
- How do I add a page?
- How do I edit a page?
- How do I change the settings (name, security, etc.) for a page?
- How do I make a copy of a page?
- How do I delete a page?
- How do I restore a deleted a page?
- How do I add a module (text, blog, forum, etc.) to a page?
- How do I edit a module on the page?
- How do I move a module on the page?
- How do I copy a module to another page?
- How do I delete a module on a page?
- How do I restore a deleted module?
- How do I download a backup copy of my site?
- How do I restore a backup copy of my site?
- How can I learn more about DotNetNuke?
- Which browsers can I use to maintain my DotNetNuke site?
- How do I update the copyright notice / date displayed on my site?
- Should I upgrade to the latest version of DotNetNuke?
- What is the procedure to upgrade DotNetNuke on a site?
1. How do I log in to my site?
You need to log in to your DotNetNuke site to do all administrative tasks (i.e. add, edit, move, delete modules or pages). All the subsequent questions assume you are logged in to your site.
To log in:
- Click on the "Login" link usually located in the upper right corner or bottom of the page (depending on your site design).

- Enter your User Name and Password in the form.

If you have forgotten your password, select the "Forgot Password?" link on this page. If you have forgotten your User Name (and you are one of our clients), please contact us for help.
- (Optional) Check the "Remember Login" to have the browser save your login information.
- Click the Login button.
Once you are logged in, you will see the "Login" link change to "Logout" and your name will be displayed next to this link.

Note: Even if you have "Remember Login" checked, the site will occasionally ask you for your password as a security measure.
2. How do I add a page?
To add a page to your site:
- If the Control Panel is not open, click the button to the right of the "Show Control Panel?" label in the upper right corner of the page.

- Near the top left, you will see an area labeled "Page Functions". Click the "Add" button or text to add a page.

- On the "Page Management" page, enter the "Page Name". This is the name that will be displayed in the menu and on the browser's title bar. Note: You do not need to enter a Page Title unless you want to override the title automatically generated by DotNetNuke that includes the complete path to this page.

- (Optional) Set the Parent Page of this page (if it should be organized under one of the main pages on the site).
- In the "Permissions" section, check the "All Users" "View Page" box if the page is ready to be seen by all users. Or you can do this later.
- Click the "Update" link at the bottom of the page to save your changes.
Once you have added a page, you can add modules, add content to those modules, etc.
3. How do I edit a page?
To edit a page:
- Make sure the "Mode:" control is set to "Edit" (near the top right corner of the window).

This will put all modules in Edit mode.
You can then edit any individual module via the modules' drop-down menu (usually near the upper left corner of the module, depending on the skin).

You can also use any commands listed at the bottom of a module (e.g. "Delete", "Settings" or "Edit Text").

4. How do I change the settings (name, security, etc.) for a page?
To change page settings (like its name):
- Navigate to the page
- Make sure the Control Panel is open. (If not, click the button to the right of "Show Control Panel".)
- Press the "Settings" button in the "Page Functions" portion of the Control Panel.

5. How do I make a copy of a page?
You may want to copy a page for any number of reasons:
- To use the original page as a template for a similar page
- To work on a major overhaul of the page
- etc.
To copy a page:
- Navigate to the page.
- Make sure the Control Panel is open. (If not, click the button to the right of "Show Control Panel".)
- Press the "Copy" button in the "Page Functions" portion of the Control Panel.

- On the "Page Management" page, notice the "Copy Page" section of settings. Here, under "Specify Modules", you can pick and choose which modules to copy and what kind of copy to make. (See below for more details on this.)

- Press "Update" to complete the copy.
There are three kinds of "copy":
- "New" creates a new (empty) instance of the module on the new page.
- "Copy" copies the module and its content to the new page.
- "Reference" creates a reference to the original module on the new page (i.e. both pages shares the same module and content).
6. How do I delete a page?
To delete a page:
- Navigate to the page.
- Make sure the Control Panel is open. (If not, click the button to the right of "Show Control Panel".)
- Press the "Delete" button in the "Page Functions" portion of the Control Panel.

- Press "OK" to confirm the deletion.
If you accidentally delete a page, you can restore it.
7. How do I restore a deleted a page?
To restore a deleted page:
- Select "Admin" > "Recycle Bin" from the menu to display the Recycle Bin page.

- Select the page you wish to restore from the Pages section.
- Press the Restore Selected Page button to restore the page.
8. How do I add a module (text, blog, forum, etc.) to a page?
To add a module to a page:
- Navigate to the page
- Make sure the Control Panel is open. (If not, click the button to the right of "Show Control Panel".)
- In the center (module) section of the Control Panel, choose the module you wish to add.

- Type in a Title for the module to identify it. (If you leave it blank, the module will set a name by default.)
- (Optional) Set the Visibility of the module. Most often you will leave this as "Same as Page".
- (Optional) Set the Pane for the modulue. Often, you will leave this as Content.
- (Optional) Set the Insert point for the module. Often, you will leave this as "Bottom". Note this option only applies to new module's position in the Pane. You can always change the position from the module's Move menu later.
- (Optional) Set the Align setting for the module. Often, you will leave this as "Left". You have more complete control over text alignment within the Text/HTML module itself.
- Select the Add link or button to the right of these settings to add the module to the page.
Once you have added a module, you will most likely need to edit its contents or settings.
9. How do I edit a module on the page?
How you edit the settings and content of a module depends on the module itself. All modules have a "Settings" command in the module menu. Most modules add one or more module-specific commands to this menu. For example, the Text;/HTML module adds the "Edit Text" command.
To edit a module's settings:
- Select the module's drop-down menu button (a small black triangle).

- Choose the Settings command.
- Make any desired changes and select Update when done.
To edit the Text/HTML module text:
- Select the module's drop-down menu button (a small black triangle).

- Select "Edit Text" from the menu.
- Make your changes in the text editor.

- Select Update (near the bottom of the page) when you're done.
10. How do I move a module on the page?
To move a module on the page:
- Select the module's drop-down menu button (a small black triangle).
- Move the mouse over the "Move" entry and then select the Pane to move the module to.

11. How do I copy a module to another page?
You can create a reference to an existing module on another page via the "Add Existing Module" setting in the Control Panel. This allows both pages to share the same module and content. It does not make a separate copy of a module.
To add a reference to a module from another page on the current page:
- Navigate to the "current" page (not the page with the module on it).
- Make sure the Control Panel is open. (If not, click the button to the right of "Show Control Panel".)
- In the center (module) section of the Control Panel, select "Add Existing Module".

- Select the Page that contains the module that you want to reference.
- Selecte the Module from that page that you want to reference.
- (Optional) Set the Visibility of the module. Most often you will leave this as "Same as Page".
- (Optional) Set the Pane for the modulue. Often, you will leave this as Content.
- (Optional) Set the Insert point for the module. Often, you will leave this as "Bottom". Note this option only applies to new module's position in the Pane. You can always change the position from the module's Move menu later.
- (Optional) Set the Align setting for the module. Often, you will leave this as "Left". You have more complete control over text alignment within the Text/HTML module itself.
- Select the Add link or button to the right of these settings to add the module to the page.
Note: This technique can be used to move a module from one page to another. First, make a refernce to the module on a new page, then delete it from the old page.
12. How do I delete a module on a page?
To delete a module:
- Select the "Delete" command from the module's drop-down menu.

- Press "OK" to confirm the deletion.
If you accidentally delete a module, you can restore it.
13. How do I restore a deleted module?
To restore a deleted module:
- Navigate to Admin > Recycle Bin in the menu.

- In the Modules section, select the module you wish to restore. Note that the most-recently deleted module is at the bottom of the list.
- In the "Restore to Page", select the page to put the module on.
- Select the Restore Module button (to the right of the modules list).
14. How do I download a backup copy of my site?
It is very important to back up your site on a regular basis. Dynamic DotNetNuke sites are different than the "old-fashioned" static HTML sites of the past. DotNetNuke site can be constantly updated by any authorized users. All the site content and changes is kept in a database. Therefore, there may be no "backup" copy of the site unless you make a copy of the site files and database.
Now, most web hosting providers do back up their computers and databases on a regular basis. However, it is certainly prudent to download your own backup periodically.
How you back up your site depends on your web host and the site control panel that they use. Below, we document the basic steps for creating and downloading backups from:
- PowerDNN using the Parallels Business Automation control panel, and
- iHostASP.net using the Helm control panel.
To download a site backup on PowerDNN using the Plesk control panel:
- Sign in to your PowerDNN web host control panel. (See your "Credentials" document for your username and password.)

- In the Parallels control panel, select your domain name from the list (near the bottom of the page).

- Select the Backup button.

- If your site is set up to do regular automatic backups, click the "Diskette" (download) button to the right of the most recent backup to download the backup. You are done and can skip the rest of the steps. Otherwise, select "Create Backup" button.
or 
- Make sure "Backup method" is set to "create backup file and store in repository".

- Enter a "Backup file name". We recommend a name that contains the domain name and current date and the ".zip" extension (e.g. "MyDomain.com2008-01-13Backup.zip")

- Uncheck "Suspend Domain". (You can usually leave your domain running while the backup is being done. Check this if there is a problem completing the backup.)

- Enter your email address in the "Notify by email" field. In this way, you don't have to wait for the backup to complete. You will be notified by email when it is done.

- You can check or uncheck "Backup the content of mailboxes" as desired.
- Click the "Back Up" button on the bottom of the page.
- Once the backup is complete, it will be listed in the repository and can be downloaded as described in step 4.
iHost creates nightly backups of your database and put it in a Backups folder on your web server. Note that this backup contains database (i.e. the content) for your site, it does not contain the DotNetNuke framework files. These should be downloaded separately using an FTP tool.
To download a site database backup on iHostASP.net using the Helm control panel:
- Logon to the iHostASP.net Helm control panel and press Continue. (See your "Credentials" document for your username and password.)

- Click on the Domains button.

- Click on your domain name in the list.

- Click on the File Manager button.

- Click on the Backups folder to display its contents.

- Right-click on the latest file and choose "Save Target As..." (or your browser's equivalent command) to save the file to your computer.

15. How do I restore a backup copy of my site?
Restoring a backup is best done by contacting your web host and working with a support representative.
16. How can I learn more about DotNetNuke?
There are many ways to learn more about DotNetNuke. Please understand that DotNetNuke is a very rich system. It would take a lifetime to understand everything about the system. So the best strategy is to find help with the portion of the system you are interested in.
Here are some resources that I am aware of (and my comments about them):
- The DotNetNuke website including its Guided Tour and Online Help. The Guided Tour is nice but currently is a little dated. In general, I don't find the DNN site very helpful for beginners, but it is the primary source of information about the platform.
- DotNetNuke For Dummies and other DotNetNuke books. I don't have a specific recommendation for beginners, but the "Dummies" book would probably be a good place to start.
- The DNNCreative online magazine with an extensive video library of "how to" videos. A subscription is about $78 / year, but well worth it (I subscribe). While there are a good number of "beginner" videos in there, this library is most useful to more advanced users.

17. Which browsers can I use to maintain my DotNetNuke site?
You can use just about any modern browser to edit DotNetNuke sites. I have used the latest versions of Internet Explorer, Firefox, Chrome, Opera and Safari without any major issues. If you have a problem with a particular combination, make sure you are using the latest version of the browser and that your site is using the current version of DotNetNuke.
Currently, Google Chrome is my preferred browser. But if I ever have trouble editing a site, I fall back on Firefox or Internet Explorer.
18. How do I update the copyright notice / date displayed on my site?
To update the copyright notice (and other settings that affect the site as a whole):
- Select Admin > Site Settings.
- Edit the Copyright field.

- Scroll down near the bottom of the page and select Update.
19. Should I upgrade to the latest version of DotNetNuke?
When you log in to your site, you may see an "Updates Available" graphic like these at the top of the Control Panel:


These indicate that there is a DotNetNuke update or critical update available for download from the DotNetNuke website. Like most computer software, DotNetNuke frequently comes out with minor and major upgrades and security updates. These updates often fix obscure, but significant problems. It is a good idea to upgrade to the latest stable version periodically (just like with any software program you use on a regular basis). However, if you installed every new release that comes out, you'd be upgrading every month or so - not usually a desirable thing.
So the question is, "If I see one of these buttons, should I upgrade to the latest version of DotNetNuke?"
The answer: a definite maybe. It is usually safe to upgrade, but the decision to upgrade depends on a number of factors including:
- How big a jump is the upgrade? Little upgrades are usually the easiest, but provide the least benefit. On the other hand, the longer you wait, the harder the upgrade. But you don't want to get too far behind or else you won't be able to use the latest modules and skins.
- Does the upgrade fix a problem your users are experiencing? "If it ain't broke, don't fix it."
- Does the upgrade fix a critical security problem that may affect your site? You may not know it, but your site might be vulnerable to hackers.
- Are all my modules and skin supported on the new version of DotNetNuke? If you upgrade, you may have to update some modules and/or your skin.
- How long has the new release been out? Do you really want to be the first site to install a new release? You might want to wait a week to make sure it is stable.
- Do you have a complete backup in case something goes wrong? Upgrades usually go smoothly, but if they don't you absolutely need a backup.
- Can your budget afford the upgrade? Unless you do the upgrade yourself, expect to pay $25 - $120 per upgrade (more if anything goes wrong). Most professional sites don't install every new DotNetNuke release, but they do upgrade periodically.
- Can you afford a little downtime? Your website will be unavailable for about 10 to 15 minutes while the upgrade is being performed. This could be longer if there are any problems. So make sure you do the upgrade when you can afford some potential downtime.
The bottom line is that you don't have to apply every upgrade, but you should probably upgrade on a regular basis to keep up with fixes, improvements and critical security patches.
20. What is the procedure to upgrade DotNetNuke on a site?
Here is one professional way to upgrade DotNetNuke on a site:
- Backup your files and database. It is essential that you backup both your files for the site and the database for the site. If available, you can use a Control Panel command like the Plesk > Domain > Backup command. Or use the excellent DNNBackup module from Evotiva. It is also important to verify the backups to make sure they really are a valid backup. This can be done as part of step 2. (Step 2. assumes your site has a site alias such as "localhost/MyDomain.com". If not, add it to your live site via Admin > Site Settings before doing the backup.)
- Install the backup on a local computer. Restore the files and database to a local computer (localhost), so you can test the upgrade on a different computer instead of using your live site as a 'guinea pig'. This will also verify that your backup is good.
- Verify that the original localhost site is working properly before the upgrade. You don't want to do the upgrade until you are sure the site is working properly.
- Download and unzip DNN install package to localhost installation. This is the heart of the upgrade. Go to the DotNetNuke website and get the latest installer. Make sure you get the upgrade installer if you're doing an upgrade!
- Browse to http://localost/MyDomain.com/install/install.aspx?mode=install. Replace MyDomain.com with your actual localhost site name. This will trigger the upgrade process to begin. Watch carefully for any error or warning messages as they may indicate a problem.
- Verify that the upgraded localhost site is working properly after the upgrade. This is a critical step. You want to make sure all the pages display right and that all the modules are working properly. If not, now is the time to see what needs to be fixed and what modules need to be updated. You can test the updates locally, but they will have to be reapplied to the live site, if needed.
- Upload and unzip DNN install package to online site. Once you are happy with the localhost version of the site, you are ready to upgrade the live site.
- Browse to http://www.yourdomain.com/install/install.aspx?mode=install. Trigger the installer on the live site. Again, watch carefully for any error or warning messages as they may indicate a problem.
- Verify that the live site is working properly after the upgrade. This is also a critical step. You want to make sure all the pages display right and that all the modules are working properly. If you had to update anything for the local site, you need to reapply those updates to the live site.
This procedure assumes you have a local machine that is set up to run a DotNetNuke (ASP.NET) website. It can take a fair amount of time (maybe one to four hours) to complete the process but helps to minimize the risks of an upgrade.
If you want to assume more risk, you can just perform steps 1, 7, 8 and 9. I often do this for my clients that can't afford or don't want to do the complete localhost process. It works (taking an hour or less), but may require some scrambling after the upgrade to make sure everything is working.
And while I wouldn't recommend it, you could skip the backup and just do steps 7 - 9. This is a bad idea, but in a pinch it works if you're lucky (and only takes about 10-15 minutes if all goes well).