ASPHostPortal.com is a premiere web hosting company that specializes in Windows and ASP.NET-based hosting with innovative technology  solutions, proudly announced the best osCommerce 3.0.2 hosting service with a combination of affordable price, high customer  satisfaction rate and commendable quality in all ASP.NET and Windows web hosting plans.

osCommerce 3.0.2 are made to showcase the new features being worked on and to generalize a version specific for testing to help fix  and improve subsequent alpha releases for a final, stable, secure, and production ready 3.0.2 releases. The osCommerce solution offers  great flexibility and empowers even amateur webmasters to develop highly competitive ecommerce websites.

Until recently, the cost involved in hiring a web development company to develop a similar ecommerce web site was prohibiting several  small businesses from selling on-line. The osCommerce solution is one of the best fruits of the open source community and which poses  a serious challenge to other similar commercial software products.

Installation for this software can be performed easily from within the web hosting control panel, even by customers with poor  programming experience. The installation process takes up to a minute to perform, thus enabling customers to deploy an entire  ecommerce storefront for their business within a few clicks of the mouse.

ASPHostPortal.com is the among the few top web hosting company that tested and offer ASP.NET hosting plan that compliance with  osCommerce 3.0.2 hosting. There are several companies out there that offer e-Commerce hosting plan but at ASPHostPortal.com, we provide quality e-Commerce  hosting plan at affordable prices that will not only keep your operating costs low but also help you to maximize your profits.

ASPHostPortal.com development teams have fully tested and deployed the latest osCommerce 3.0.2 in hosting control panel systems.  Clients can install and use osCommerce 3.0.2 hosting with few clicks of installation steps. For more information about this topics or  have any enquiries related to osCommerce hosting, please visit http://www.asphostportal.com/osCommerce-Hosting.

About the Company
ASPHostPortal.com is a hosting company that best support in Windows and ASP.NET-based hosting. Services include shared hosting,  reseller hosting, and sharepoint hosting, with specialty in ASP.NET, SQL Server, and architecting highly scalable solutions. As a  leading small to mid-sized business web hosting provider, ASPHostPortal.com strive to offer the most technologically advanced hosting  solutions available to all customers across the world. Security, reliability, and performance are at the core of hosting operations to  ensure each site and/or application hosted is highly secured and performs at optimum level.

ASPHostPortal.com is a premiere web hosting company that specializes in Windows and ASP.NET-based hosting with innovative technology  solutions, proudly announced the best nopCommerce 3.2 hosting service with a combination of affordable price, high customer  satisfaction rate and commendable quality.

nopCommerce is an open source e-commerce solution that contains both a catalog frontend and an administration tool backend.  nopCommerce is a fully customizable shopping cart. It's stable and highly usable. From downloads to documentation, nopCommerce.com  offers a comprehensive base of information, resources, and support to the nopCommerce community. The latest version of nopCommerce is  3.2 with lots of awesome features.

The first feature that will grab the attention of every nopCommerce store owner is the new Facebook Shop. The next major functionality  that comes with nopCommerce 3.20 is its support for warehouses. What this means is that you can configure individual products to be  shipped from a specific location (warehouse). You can also configure the system to use the warehouse location when calculating the  shipping cost for the product. While we are on the nopCommerce 3.20 shipping functionality, there is another new feature worth  mentioning. Now the store owner can specify when a product will be shipped. In nopCommerce this information is referred to as delivery  date. This is useful for example when you are selling products, which are manufactured on demand.

Nopcommerce 3.2 is simply the best and most powerful open source shopping cart on the planet. It is the only open source shopping  cart application that supports both multi-sites and multi-vendors. NopCommerce is fast, easy, and fun. I definitely recommend  NopCommerce to anyone who wants to start an online business.

ASPHostPortal.com is a popular online nopCommerce 3.2 hosting service provider with all of its hosting plans to help users to automate  and simplify website and server administration tasks such as installation and migration. There are several companies out there that offer e-Commerce hosting plan but at ASPHostPortal.com provide quality e-Commerce  hosting plan at affordable prices that will not only keep your operating costs low but also help you to maximize your profits.

nopCommerce is ASP.NET 4.0 based supporting MS SQL databases. It features an embedded graphic installer, so nopCommerce can be setup  in few minutes and run immediately. For more information about this topics or have any enquiries related to nopCommerce hosting,  please visit http://www.asphostportal.com/nopCommerce-Hosting.

About the Company
ASPHostPortal.com is a hosting company that best support in Windows and ASP.NET-based hosting. Services include shared hosting,  reseller hosting, and sharepoint hosting, with specialty in ASP.NET, SQL Server, and architecting highly scalable solutions. As a  leading small to mid-sized business web hosting provider, ASPHostPortal.com strive to offer the most technologically advanced hosting  solutions available to all customers across the world. Security, reliability, and performance are at the core of hosting operations to  ensure each site and/or application hosted is highly secured and performs at optimum level.

ASPHostPortal.com is a premiere web hosting company that specializes in Windows and ASP.NET-based  hosting with innovative technology solutions, proudly announced the best DotNetNuke (DNN) 7.2 hosting  service with a combination of affordable price, high customer satisfaction rate and commendable quality.

DotNetNuke is an open source web content management system that is built on ASP.net infrastructure and  solely has its life wire running smoothly on Microsoft platform. Furthermore, it is an open source web  content management system that started in the year 2002 by a team of developers which was headed by the  original creator Shaun Walker who happens to have bagged his certification as a certified Microsoft Most  Valuable Professional in the year 2004 and the latest version is 7.2 with lots of awesome features.

DotNetNuke (DNN) 7.2 includes a number of new features and enhancements that will benefit users and  developers alike along with a large number of bug fixes. DNN 7.2 version incorporates some of the  interesting features to elevate the existing functionality and make your site administration process a  lot easier. DNN 7.2 also allows you to install JavaScript libraries as first party extensions. Once  installed your module or skin can request that JavaScript library and the platform will automatically  add the library into the page. The API mirrors the one used for jQuery and JQuery UI making it very easy  to use.

Some benefits that the DotNetNuke content management system includes are greater site consistency,  improved site navigation, streamlined authoring process, faster turnaround time for new pages and  changes, increased site flexibility, support for decentralised authoring, increased security, reduced  duplication of information, greater capacity for growth, and reduced site maintenance costs. DotNetNuke is the best CMS (content management system) for businesses and  is easier to create and manage with ASPHostPortal.com.

ASPHostPortal.com is a popular online DotNetNuke (DNN) 7.2 hosting service provider with all of its  hosting plans to help users to automate and simplify website and server administration tasks such as  installation and migration. For more information about this topics or have any enquiries related to DotNetNuke (DNN) 7.2 hosting,  please visit http://www.asphostportal.com/DotNetNuke-Hosting

About the Company
ASPHostPortal.com is a hosting company that best support in Windows and ASP.NET-based hosting. Services  include shared hosting, reseller hosting, and sharepoint hosting, with specialty in ASP.NET, SQL Server,  and architecting highly scalable solutions. As a leading small to mid-sized business web hosting  provider, ASPHostPortal.com strive to offer the most technologically advanced hosting solutions available to  all customers across the world. Security, reliability, and performance are at the core of hosting  operations to ensure each site and/or application hosted is highly secured and performs at optimum  level.

DotNetNuke is an open-source content management system ideal for creating and deploying projects such as commercial websites, corporate intranets and extranets, and online publishing portals. DotNetNuke is built on a Microsoft ASP.NET (VB.NET) platform, and is easily installed and hosted with all of our Windows Hosting Plans. If there is an upgrade available, follow the following steps to perform the upgrade.

In Preparation:

• Back up the DNN database
• Back up all website files
• Check your database and website backups!
• Download the latest DotNetNuke upgrade package:
  a. From the www.dotnetnuke.com site. You may need login credentials if you are using a non-community version of DNN.
  or
  b. Click the "Upgrade Available" button that appears when you are *not* running the latest version.
• Create a basic html document called app_offline.htm. This page will be shown on the site while you are doing the upgrade.

See figure about no maintenance page. Users may see errors while the site is partially upgraded.

Good Example - HTML page to let users know the site is offline:

This site is offline for routine maintenance. Please check back later.

To Perform the Upgrade:

1. Upload the app_offline.htm file to the root web folder for the site.
2. Navigate to the site in a web browser and check that the app_offline.htm file is shown instead of the usual default page.
3. Copy the contents of the latest DotNetNuke upgrade package over the top of the existing files. All files should be copied because the package should only contain generic files ?no configuration files.
4. When the copy is complete, rename the app_offline.htm file to app_offline.htm.save. When you navigate to the site, you will see a new construction page:

   

5. Access the /install/install.aspx?mode=upgrade page (e.g.www.mysite.com/install/install.aspx?mode=upgrade) using a web browser. The site will begin an automatic upgrade process:

   

   
   

6. On completion of the upgrade, you will see the following message at the bottom of the page. Click on the link to return to the site.
   

   

   
   

7. Click through the newly upgraded site to perform a smoke test.
8. Log in to the DNN site and navigate to "Host", then "Host Settings". You will see that the site is running the newest version of DNN and that there are no upgrades available.
   

   

If you are planning to start using the new Advanced URL functionality in DNN 7.1, and you have an existing license for the Url Master module, there is a conversion path. This converts all of the Url Master redirects, portal alias settings and configuration settings over to the DNN format. The Advanced functionality is heavily based on the Url Master codebase, but they are not exactly the same. Many changes have been made in order to properly integrate the product into the DNN Core.

Therefore, I suggest that people test the switch-over carefully, and make sure that they have checked that redirects, third-party modules, and all other URL-related functionality works correctly. I strongly recommend that people do this in a 'localhost' test environment if they have the capability. If not, you must take a backup immediately prior to doing the conversion and be prepared to revert to the backed-up version of the site if the tests do not pass.

This process applies both to the DNN Platform (formerly DotNetNuke Community Edition) and those who have upgraded DotNetNuke Professional Edition to Evoq Content.   While the DNN Platform has very few UI configuration locations for the Advanced URL Settings, the functionality is fully operational once the Url Master settings are converted.

Please note : you need to have a fully licensed version of Url Master in order to activate the conversion functionality, except if you are running on ‘localhost’, in which case it will work with an unlicensed version.

The actual process of conversion is very simple:

1. Upgrade your Url Master version to 2.8

2. Go to the Host->Friendly Url Settings page, and find the 'Convert to DNN Advanced Urls' button.

3.  This will load the Conversion Dialog:

Click 'Start Conversion' when you are ready to do the conversion.

4.  The conversion process will run, and then show a summary of the changes made:

The figures in the boxes apply to the entire DNN installation. Check through the numbers to do a 'sanity check' and make sure that the figures seem correct. You can then close the dialog – the conversion is complete and your site is now activated in DNN 'Advanced' mode. Note that because this requires a web.config change, the site will automatically restart when the process is complete.  The 'close' button triggers a page refresh to complete this process.

5. Check functionality on your site to make sure that the conversion has worked correctly. A brief set of tests should include:

1. Basic site operation : all public URLs work as expected
2. Edit Mode : does the Edit Mode functionality work as before?
3. Any third-party module functionality : do blog posts, forum threads, e-commerce pages, photo galleries etc load up correctly?
4. Login/Logoff functions : are you able to login and log out as normal?
5. 404 Handling : if you had 404 handling configured, check that the 404 error handling works as expected.
6. Admin/Host Urls : are you able to do basic functions like search for a user, save site settings, etc?
7. Custom Urls : do custom redirects you had configured in Url Master still work OK?  Are any custom URLs showing for pages correctly?
8. Site Alias redirects : does the site respond correctly in terms of alias redirects (like example.com –> www.example.com)
9. User Profile pages : if you had vanity user profile URLs activated, do they still work correctly?  Are the profile pictures showing correctly, can users post updates, edit their profiles?

This is only a brief list to get you thinking; you should execute a comprehensive test plan to make sure the site is working as expected.  Your SEO depends on making sure there are no surprises and everything is working as before. In the vast majority of cases, there should be no difference in behaviour or functionality, but it is imperative that this be tested and confirmed. While I have tested this functionality to make sure a like-for-like conversion of settings is working as expected, it is impossible to test the entire universe of Url Master installations.

6.  When the conversion is finished, it’s up to you whether or not you uninstall the Url Master module. You may wish to keep it installed as a backup for the short term in case you find a problem with the conversion process. You can run the conversion process as many times as you like – it has been designed to be run repeatedly without causing any issue, to allow for iterative checks. Each time it is run, the settings are taken from the Url Master configuration and applied to the DNN install – thus any changes in the DNN installation may be overwritten each time you do this.

Anyone using Custom Module Providers for the Url Master module – the settings specific to Custom Module Providers are not converted during this process.  Any Custom Module providers will have to be replaced like-for-like with a DNN 7.1 specific Extension Url Provider which provides the same functionality, and the settings specific to that provider will have to be carried across.

If you are planning to start using the new Advanced URL functionality in DNN 7.1, and you have an existing license for the Url Master module, there is a conversion path. This converts all of the Url Master redirects, portal alias settings and configuration settings over to the DNN format. The Advanced functionality is heavily based on the Url Master codebase, but they are not exactly the same. Many changes have been made in order to properly integrate the product into the DNN Core.

Therefore, I suggest that people test the switch-over carefully, and make sure that they have checked that redirects, third-party modules, and all other URL-related functionality works correctly. I strongly recommend that people do this in a 'localhost' test environment if they have the capability. If not, you must take a backup immediately prior to doing the conversion and be prepared to revert to the backed-up version of the site if the tests do not pass.

This process applies both to the DNN Platform (formerly DotNetNuke Community Edition) and those who have upgraded DotNetNuke Professional Edition to Evoq Content.   While the DNN Platform has very few UI configuration locations for the Advanced URL Settings, the functionality is fully operational once the Url Master settings are converted.

Please note : you need to have a fully licensed version of Url Master in order to activate the conversion functionality, except if you are running on ‘localhost’, in which case it will work with an unlicensed version.

The actual process of conversion is very simple:

1. Upgrade your Url Master version to 2.8

2. Go to the Host->Friendly Url Settings page, and find the 'Convert to DNN Advanced Urls' button.

3.  This will load the Conversion Dialog:

Click 'Start Conversion' when you are ready to do the conversion.

4.  The conversion process will run, and then show a summary of the changes made:

The figures in the boxes apply to the entire DNN installation. Check through the numbers to do a 'sanity check' and make sure that the figures seem correct. You can then close the dialog – the conversion is complete and your site is now activated in DNN 'Advanced' mode. Note that because this requires a web.config change, the site will automatically restart when the process is complete.  The 'close' button triggers a page refresh to complete this process.

5. Check functionality on your site to make sure that the conversion has worked correctly. A brief set of tests should include:

1. Basic site operation : all public URLs work as expected
2. Edit Mode : does the Edit Mode functionality work as before?
3. Any third-party module functionality : do blog posts, forum threads, e-commerce pages, photo galleries etc load up correctly?
4. Login/Logoff functions : are you able to login and log out as normal?
5. 404 Handling : if you had 404 handling configured, check that the 404 error handling works as expected.
6. Admin/Host Urls : are you able to do basic functions like search for a user, save site settings, etc?
7. Custom Urls : do custom redirects you had configured in Url Master still work OK?  Are any custom URLs showing for pages correctly?
8. Site Alias redirects : does the site respond correctly in terms of alias redirects (like example.com –> www.example.com)
9. User Profile pages : if you had vanity user profile URLs activated, do they still work correctly?  Are the profile pictures showing correctly, can users post updates, edit their profiles?

This is only a brief list to get you thinking; you should execute a comprehensive test plan to make sure the site is working as expected.  Your SEO depends on making sure there are no surprises and everything is working as before. In the vast majority of cases, there should be no difference in behaviour or functionality, but it is imperative that this be tested and confirmed. While I have tested this functionality to make sure a like-for-like conversion of settings is working as expected, it is impossible to test the entire universe of Url Master installations.

6.  When the conversion is finished, it’s up to you whether or not you uninstall the Url Master module. You may wish to keep it installed as a backup for the short term in case you find a problem with the conversion process. You can run the conversion process as many times as you like – it has been designed to be run repeatedly without causing any issue, to allow for iterative checks. Each time it is run, the settings are taken from the Url Master configuration and applied to the DNN install – thus any changes in the DNN installation may be overwritten each time you do this.

Anyone using Custom Module Providers for the Url Master module – the settings specific to Custom Module Providers are not converted during this process.  Any Custom Module providers will have to be replaced like-for-like with a DNN 7.1 specific Extension Url Provider which provides the same functionality, and the settings specific to that provider will have to be carried across.

DotNetNuke has many SEO features, but some are less obvious to the casual administrator. These SEO features, however, can have a dramatic effect on how your DNN website is indexed by Google, Bing and others, and as such, can have an effect on your page rank and search results.

Here are a few DNN tips and tricks to help in your DNN’s SEO:

1. Site Map Priority
Buried within your page settings is a feature that allows you to set indexing priorities to your DNN pages. To get there (once logged in as an administrator), go to “page settings”, then “advanced settings”, then at the bottom of the window, go to “other settings”.

Here you will find the item: “Site Map Priority”. The default for this is .5. However, if your page is the home page, or perhaps a landing page, you will want to up the number to 1.0, or .9 (1.0 being the highest). This will increase the perceived importance of the page by search engines such as Google. Where is this relevant? When your organization appears in a Google search, high priority pages may be presented as sub-links to the home page more frequently. This can be critical in immediately directing visitors to key pages in an organic search result.

2. Site Settings
Here we’ll talk about one of things NOT to do when it comes to SEO in DotNetNuke. In the “site settings” of DotNetNuke, administrators have the ability to enter descriptions and keywords. By doing that, those items will then be placed in the META tags for EVERY page on the DNN website. For SEO, this is an extreme no-no, as it will confuse the search engines and reduce the relevancy and page rank of your overall DNN website. It may be an easy way to get keywords throughout your site… but it will definitely hurt you in the long run!

3. Page Titles
One of the nice features about DotNetNuke is its ability to add dashes between spaced words in your page title. For example, if you title a page “DNN SEO Tips”, DNN will title the actual URL as “DNN-SEO-Tips”. This ensures that the individual words in the title will be relevant to Google.
Some administrators like to use underscores between words. For example: “DNN_SEO_Tips”. This is strongly discouraged as Google will index the entire string as one item. This means people searching for DNN, or SEO or Tips will not see your site on Google. They would only find you if they specifically put “DNN SEO Tips”. In some cases this may be a good thing, if your content is very niche-oriented. But if you’re looking to gather visitors based on more broad searches, using underscores will hurt you.

4. Robots.txt
OK, this one gets a bit technical for the casual DotNetNuke administrator, but robots.txt is an important factor when comes to SEO, so what we’ll do in this section is give you enough information that you can intelligently go to your IT person or your hosting provider to ask questions.

In short, the robots.txt function (which not accessible via the administration tools in DNN), tells various search engines such as Google what pages to index and what pages they should not. Pretty important! But, if your DNN website is with a host provider and you are operating on a shared instance (one installation of DNN with many portals), you may be operating on one, centralized robots.txt file, which may be configured to tell the robots to ignore all pages on your site!

There is a way to take control and get around this, but it takes someone with access to the server and a bit of IT knowledge. But, don’t let that stop you from finding out if your robots.txt file is configured properly.

Ask your IT or host provider:
Is your DNN website on a shared instance?
Do you have an individual robots.txt file for your specific DNN website?

That’s it a few simple tools and information on how to squeeze more effectiveness with your DotNetNuke’s SEO. Hope useful.

Professional web hosting provider – ASPHostPortal.com proudly announced the integration of the latest Web Deploy 3.5 in all  web hosting plans. We are the first few hosting company that provide ASP.NET hosting plan that support the brand new Web  Deploy 3.5 Hosting.

WebDeploy v3.5 is now available and there are a few features to consider in this minor release:

1. Load Balancer Support with Session Affinity. 
2. Encrypting web.config Settings Post-Publish.
3. App Offline Template.
4. Seamless integration with IIS Manager (IIS7 and above), Visual Studio (2010 and above) for creating packages and  deploying them onto a machine, both locally and remotely.
5. Integration with WebMatrix for deploying and downloading web applications.
6. Seamless integration with the Web Platform Installer to install community web applications simply and easily.
7. Web application packaging and deployment.
8. Web server migration and synchronization.
9. Automatic backup of Web Sites before making any changes.
10. In addition to the IIS Manager, Visual Studio 10, Web Matrix tasks can be performed using the command-line, PowerShell  Cmdlets or public APIs.

According to ASPHostPortal.com, it's Web Deploy 3.5 offerings are distinguished by their low cost, with many of the hosting  services supporting the technology being of the more expensive variety.
For more information about this topics or have any enquiries related to Web Deploy 3.5 hosting, please visit  http://www.asphostportal.com

About ASPHostPortal.com:
ASPHostPortal.com is a hosting company that best support in Windows and ASP.NET-based hosting. Services include shared  hosting, reseller hosting, and sharepoint hosting, with specialty in ASP.NET, SQL Server, and architecting highly scalable  solutions. As a leading small to mid-sized business web hosting provider, ASPHostPortal strive to offer the most  technologically advanced hosting solutions available to all customers across the world. Security, reliability, and  performance are at the core of hosting operations to ensure each site and/or application hosted is highly secured and  performs at optimum level.

DotNetNuke (DNN) is a web application Open Source Platform and has grown in popularity over the years because it does a very good job of solving the problem of basic web solution. In this article, I am going to explain how we can create custom role and assign roles to the user.

Using "Roles" is one of the greatest features in DotNetNuke (DNN). Based on that, we can give rights to user to view pages, View Modules, access menus, etc. Roles can be customizable. We can restrict a user to view some page or some part of a Page based on the role only. Let's see how we can assign a role to a newly created user.

1.  Click on Edit (Pencil) icon for that user to whom we want to add a Role. Let's say I clicked on Edit icon of user "Abhijit Jana".


2. Click on "Manage Roles for this User" Link. This will redirect you to Create and Assign Role Page.


Here we can select the Roles for user. One user can have multiple Roles. We can give theeffective and Expiry date for roles too. Just Select Role from "Security Role" Dropdown and Select date if needed then click on the "Add Role to User" Link. This means selected role is now given to that user. We can also remove the added role in a similar way by clicking on Delete (Cross) Icon.

Creating new roles are very simple. Follow steps bellow:

1. From Admin Menu Clicks on "Security Roles" Link. This will open a new page with the list of all existing Roles.


2. Click on Down Arrow Icon with Security Roles (Lock Icon), and select "Add New Role" as shown in the picture given below, I am going to create a new Role:


3. Here we need to give the Role Name and Description with other details. Then we need to click on the Update button to save the Role:


5. On update, "Sales Team" roles will be added with the list of Roles. We can use the Edit (Pencil) Icon to Edit the Role.



I have already discussed how to assign a role to a user. We need to flow the same steps. Below are the sample screen shots where I am assigning the newly created "Sales Team" Role to a user.


Hope it will be helpful for those who are starting with DNN.

One of the many benefits of DotNetNuke is the ability to easily control which users of the website can see and interact with what content. You can control the security and settings at the Page and Module level. This is useful if you wanted to create sections of your website that are for registered website users, members only, or for employee only sections.

Roles

A role is usually a group of users. There are a couple default roles such as Registered User, Unauthenticated user as well as a subscriber. However, you can create as many roles as you may need for your website. Examples may include PaidMembership, Employee, BoardofDirector, or Blogger. You can then add users of the website to a role.

Users

A user is anyone who has a username and password to access the website. You may have created them an account, or possibly they registered and created their own account. By default every user will be in the Registered Users and Subscribers role. You can then manually add that user to additional roles as needed. Some modules like the 3rdparty DNNspot.com Store can automatically add users to roles after buying a certain product. For example, after they purchase a ‘membership’ it can add them into a member’s role.

You can read about page and module settings to learn more about how to configure what users on your website can access which areas or control who can edit what.

Managing Users

From the admin Users page, which can be accessed in the upper right corner under ‘common tasks,’ you are able to Add/Edit/Delete Users, manage passwords, as well as determine what fields you want to collect when a user registers.

Extending User Profile & Account Registration

By default, when you register DotNetNuke will collect a username, first name, last name, display name, email address, and a password. If you want to collect more information than the basics, roll over the blue arrow on the Users module and select Manage Profile Properties. You will notice when you access this area that you will see many more properties that you can enable and also you can add more fields by clicking Add New Profile Property. If Required is checked then the user must provide a value for that field. If visible is selected then it will be shown on the new user registration page. 

However, by default, DotNetNuke is configured for the basics registration options unless explicitly told otherwise. To get DNN to honor the custom profile fields you need to access the Users section then select “User Settings.”

The setting you want to change is Require a valid Profile for Registration. Set that to true and DNN will then use the custom profile fields on the new user registration page.

User Settings

You will notice a lot of settings in the User Settings area. The first two sections regarding Membership Provider Settings and Password Aging Settings are all controlled from your DotNetNuke web.config file. These cannot be configured from within DNN, only by editing that file. Many of the User Account settings are for configuring how the administrators User list is displayed. Then you have some valuable options like where to redirect the user after logging in, after logging out, or after registering. You can also require them to complete a CAPTCHA during the login or registration process. The require valid profile option is to show the user the additional profile properties when creating an account. Require a valid profile for login is an option in case you want to create someone’s username and password then send that to them. Once they login, they will have to complete the rest of their profile before getting access to the site.