If you've never worked with a CMS or portal site system before, you might find some of the features and settings a bit complicated. But keep in mind, after you have done the initial setup, the majority of those options will not change often during the life of your site, if they change at all. Try out different settings to see what works best for your site.
For most of the site settings, making changes will not outright break your site. But there are some circumstances where you might have problems making changes, or even accidentially lock yourself out of your own site. Three common concerns with initial setups are discussed in the following sections.
No Authorization as Administrator
A very common problem when navigating through the PostNuke administration system is the appearance of the error message "No Authorization to Carry Out Operation" after submitting a form. Secure operations are accomplished using authids created for you when you log in using an administrative account. The message occurs when you use browser navigation buttons instead of in-page navigation links. PostNuke is designed to work this way as an additional security feature to prevent URL data submissions.
For example, suppose you filled out a form, clicked the Submit button, and then clicked the Back button to make a change and submit again. The second submit is not valid because you did not go to the form page in a legal way. To prevent this from happening, you must use the navigation links built in to PostNuke whenever possible.
Locked Out Without Intranet Mode
If your PostNuke site is running on an intranet and you accidentally turn the Intranet Mode setting off, you might find yourself locked out of your site if your only browsing option is to use an unqualified domain. A quick fix for this problem is to set an FQDN for your server's IP in your local machine's host file. Then, you can use a complete name from your local machine, and the server will respond to you, allowing you to turn Intranet Mode back on. Your Windows XP hosts file is found at c:\windows\system32\drivers\etc\hosts, and in Linux, the file is usually at /etc/hosts. You can edit the file with any text editor. The hosts entry would look something like this:
Bad Default User Account Group
You can easily fix a user account locked out due to a group name error by going to Administration Menu, and click on the Groups link. Select the Group Name to which you want to add the lost account, and choose the user account from the list provided. After being added to a valid group, the user account can log in normally.