DNN 7 permits customization of the enlistment structure through a simple interface, with intellisense. You simply select "Custom" for Registration Form Type in Admin - Site Settings - User Account Settings tab and you can include all the fields you like to your enlistment structure.

Site Settings

Right now of composing, this doesn't appear to function admirably with custom enlistment properties (i.e. fields you have made yourself through the "Profile Settings - Add New Profile Property catch underneath on the same tab). On the off chance that you attempt to sort a custom property's name on the Registration Fields box, it simply won't come up (despite the fact that its been accounted for that properties of datatype "Content" do come up).

With a specific end goal to make these properties accessible to your enrollment structure until a fix is connected to this, you can utilize SSMS (gave that you have entry and experience utilizing it) and do the accompanying:

• Go to your DNN database

• Open the "Portalsettings" table for alter and discover the record that has the worth "Registration_registrationfields" in the "Settingname" field

• You'll see that the "Settingvalue" field is a comma-delimited rundown containing the field monikers of the properties that are to be shown on the custom enlistment structure. Include the nom de plumes you could call your own fields in the rundown.

• Redesign the table and go to your DNN establishment (as the Host client), and click on Tools - Clear Cache

• In the event that everything goes well, you'll see that the "Enrollment Fields" box now contains your properties as well, and they will seem regularly on the enlistment structure.

An alternate approach to do this is to utilize the Host - SQL segment on your DNN establishment. To see the current profile properties that are shown on the custom enrollment structure, sort this into the Script box and click "Run Script":

SELECT
SettingValue
FROM  {databaseOwner}{objectQualifier}PortalSettings
WHERE
SettingName = 'Registration_RegistrationFields'

With a specific end goal to include one or more fields toward the end of the rundown, you must run something like this (where "Myfield" is your custom field's assumed name). Keep in mind the comma and utilize no spaces.

UPDATE

{databaseOwner}{objectQualifier}PortalSettings
SET
SettingValue = SettingValue + ',MyField'
WHERE
SettingName = 'Registration_RegistrationFields'

After you run it, go to Tools and click Clear Cache and you will see your fields on the "Enrollment Fields" box in the Admin - Site Settings - User Account Settings tab.

On the off chance that despite everything you require more power and customization with your custom enlistment page, take a gander at the Dynamic Registration module from Datasprings - right now of composing this, form 5.0 has quite recently been discharged for DNN 7.x.

Standard disclaimer: When you do stuff like the above on your database, you do it at your own danger, and I have no obligation if you harm your database, your machine, or the universe. Continuously have a reinforcement helpful!

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5/month only. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.

Introduction

Today we will show you about Managing 'Couldn't load type "Dotnetnuke.common.global".There are a thousand reasons this feared message can show up, yet suppose it is possible that it shows up on a site that you are 100% certain no one has messed with in any capacity other than transferring documents for a long while.

The problem

The error itself is as follows:
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'DotNetNuke.Common.Global'.

Source Error:

Line 1:  <%@ Application Inherits="DotNetNuke.Common.Global" Language="VB" %>
Source File: /global.asax    Line: 1

The setting

That was precisely the case I confronted today when a customer called me and reported the lapse. The customer was totally certain that no progressions had been performed other than transferring a few records, both to the application and the server itself (no redesigns, no apppool changes, no iis design changes). Just to be protected, I checked the dates of the records in the container envelope and additionally the date of the global.asax record and all had not been changed amid the recent months.

Conceivable reasons

Seeking the Web, I was panicked to see that there were in any event a couple of dozen conceivable reasons for this lapse. Case in point, there's a multi-page string in the Dotnetnuke discussions dicussing this blunder. Unfortunately, the greater part of the cases respected moves up to the center stage, recompiling or other stuff that had been changed.

So what else could not be right? All things considered, I again found than when something appears incomprehensible, it doesn't generally must be some amazingly confounded specialized issue.

Solution

The customer had admittance to the full site root by means of a FTP client. After attempting to transfer stuff, the customer coincidentally moved the App_data organizer inside an alternate envelope. That was it! I moved the App_data organizer once more to the root and everything was fine once more.

What I realized from this occurrence: Always search for the least difficult conceivable reason for a blunder first. Trust it bails some of you out there.

Best Recommendation for DotNetNuke Hosting

ASPHostPortal.com is The Leader of Best DotNetNuke Hosting Provider. They provide DotNetNuke Hosting with Affordable Price, Fast & Stable Network, and Structured Recovery System. They start their hosting plan from $1/month. With that price, your data will be safe and always properly backed up. Moreover, they also provide uptime and 30 days money back guarantees for all hosting plan. They have 5 different data centers in the world that can give best support for your DotNetNuke site. With their complete features and cheap price, your DotNetNuke site will be turn into great performance.

DNN Security Out Of the Box
DNN (DotNetNuke) is currently the premier CMS of the US Government as a result of it's robust security and integration with current safety functions. Nevertheless even DNN is not totally excellent out of the box, and there are numerous additional safety attributes that can be put in location depending on your particular DNN eCommerce requirements. These security suggestions variety from easy to complex and cover many various aspects of possible security risks. No guide can accurately assess your particular safety requirements. In the event you would prefer to adequately secure your DNN web site, contact Clarity these days.

Improve Password Complexity and Use Specifications

Increasing password complexity is among the easiest and most successful methods to significantly boost security. Probably the most common and successful requirements are length and complexity. eight or much more characters along with a minimum of a single capital letter, one lowercase letter and 1 number is a good begin. You are able to contemplate requiring a non-alphanumeric character as well as putting restrictions on how lengthy a password may be used. Even with powerful password needs, you might be only preventing against brute force attacks.

Modify 'Host' and 'Admin' Passwords and Limit Their Use

Altering the Host and Admin password to incredibly complicated passwords is the single most successful step for safety, as each accounts are recognized to exist and are the most vulnerable to brute force attacks as a result of that. Make sure that any password you set for these accounts exceeds the password recommendations listed above. You should also think about limiting access to these accounts, as they may be essentially the most powerful accounts and would leave your site essentially the most vulnerable if they have been compromised.

Hash Password Storage

By default DotNetNuke utilizes encryption of user passwords. This provides a good degree of protection, and enables you to retrieve your password as encryption is a reversible operation. Nonetheless, should you usually do not want to help password retrieval, or want to make certain maximum protection, you may select to utilize Hashing as an alternative. Hashing is really a non-reversible operation, so even if your database is accessed or stolen, a hacker can't reverse engineer your password.

How to set Cache in DNN application/ site

Today I will show you how to set cache in DNN application/site. It is very important to set cache timing for your applications. In DNN application/ site you can set cache in host setting page. To do that you need to login with the application/ site with host login and go to “Host Settings” page. Hit the “Advance Settings” tree and then click on “Performance Settings” link. Then you can find a dropdown where all the cache types are listed, name as below,

• No Caching: 0
• Light Caching: 1
• Moderate Caching: 3
• Heavy Caching: 6

I will mention later on about the number associated with the cache name, its importance  and where you need to choose a cache type, later in this tip.
This is the screenshot of the “Performance Settings” panel.

Below is the code I have picked from hostsetting.aspx file (admin\host\hostsettings.ascx).. To set the cache time of your site you need to set the value with the cache name which will render in the host settings page under performance settings panel.

<asp:dropdownlist runat="server" Width="150">
<asp:listitem resourcekey="NoCaching" value="0">No Caching</asp:listitem>
<asp:listitem resourcekey="LightCaching" value="1">Light Caching</asp:listitem>
<asp:listitem resourcekey="ModerateCaching" value="3">Moderate aching</asp:listitem>
<asp:listitem resourcekey="HeavyCaching" value="6">Heavy Caching</asp:listitem>
</asp:dropdownlist>

The value in dropdown ranges from 0 to 6. The code above takes the value set in the dropdown and multiplies it by 20 to determine the cache duration

Today, we will explain about Navigating to Another Page from DotNetNuke Custom Module. In a few circumstances, there is a prerequisite to add usefulness that permits clients to explore from one page then onto the next in Dotnetnuke Custom Module. For instance, in the event that you have a custom module called "Register" and the client has successfully registered, you may need to explore the client to an alternate page to view client login detail where an alternate custom module as of now been included request to view login client detail.

In Dotnetnuke module we require the Tab Id of the page so as to explore to an alternate page.So to attain this we can include a dropdown field in Edit page of our custom module(register) to demonstrate all the accessible Tab/ Page names of DNN site where client can choose the Page name to redirect which  inside keeps the Tab Id as quality. Then, we can utilize that Tab Id value as a part of request to explore to other page.

[Code in C#]

EditRegister.ascx

//Adding a Dropdown field in EditRegister.ascx page to allow admin or host to select the redirect page name
<asp:DropDownList ID="ddlTabNames" runat="server"></asp:DropDownList>

EditRegister.ascx.cs

//Adding available page names to the dropdown using object of TabController
if (Page.IsPostBack == false)
{
       DotNetNuke.Entities.Tabs.TabController objTabController = new DotNetNuke.Entities.Tabs.TabController();
 
        ArrayList arrlTabs = null;
        arrlTabs = objTabController.GetTabs(this.PortalId);

        string strKey = string.Empty;
        string strValue = string.Empty;

        ddlTabNames.Items.Clear();
 
       //Get the tabname and tabid of each tabs or page using object of TabInfo and added to dropdownlist field
        foreach (Entities.Tabs.TabInfo objTab in arrlTabs)
        {
            strKey = objTab.TabName;
            strValue = objTab.TabID.ToString();

            ddlTabNames.Items.Add(new ListItem(strKey, strValue));
        }
}

       //Using ModuleControler object we need to save selected Page TabId in module specific variable
        ModuleController objController = new ModuleController();
        objController.UpdateModuleSetting(this.ModuleId, "TabID", ddlTabNames.SelectedValue);

ViewRegister.ascx.cs

       Now From custom module view page we can redirect to another Page or Tab of DNN website using following code

       //Get the selected TabId
       int iProfileTabId = Convert.ToInt32(Settings["TabID"]);

       //Redirect to selected Page
        this.Response.Redirect(Globals.NavigateURL(iProfileTabId), true);

Registered Script Control Error in DotNetNuke 7

If you’ve made the transition from DotNetNuke 6 to DotNetNuke 7 you’ve probably discovered that the AJAX Toolkit controls don’t play nice with DotNetNuke any more.  Fortunately the Telerik AJAX controls have been bundled with DotNetNuke for version 7.  I’ve discovered that converting to the Telerik controls has been beneficial and worth the upgrade.
Still, it can be a pain getting the code right.  One particular error that I ran into today was the Registered Script Control error.  It looks something like this:

"Script control ‘{controlname}’ is not a registered script control. Script controls must be registered using RegisterScriptControl() before calling RegisterScriptDescriptors().  Parameter name: scriptControl"

The error results from “stacked” AJAX controls.  Consider the following HTML

<%@ Register TagPrefix=”dnnui” Namespace=”DotNetNuke.Web.UI.WebControls” Assembly=”DotNetNuke.Web” %>
<%@ Register TagPrefix=”DNN” Namespace=”DotNetNuke.UI.WebControls” Assembly=”DotNetNuke.WebControls” %>
   <DNN:DNNTabStrip ID=”tabsProject” runat=”server” TabRenderMode=”All” Visible=”true”>
     <DNN:DNNTab runat=”server” Label-Text=”Properties” ID=”tabGeneral”>
       <dnnui:DnnAjaxPanel runat=”server” ID=”dapMain”>
         <asp:Label runat=”server” ID=”lblInfo”></asp:Label>
       </dnnui:DnnAjaxPanel>
   </DNN:DNNTab>
     <DNN:DNNTab runat=”server” Label-Text=”Properties” ID=”tabSecond”>
       <dnnui:DnnAjaxPanel runat=”server” ID=”dapSecond”>
         <asp:Label runat=”server” ID=”lblMessage”></asp:Label>
       </dnnui:DnnAjaxPanel>
   </DNN:DNNTab>
      </DNN:DNNTabStrip>

Let’s say that the second tab (tabSecond) should only appear under certain conditions; a record was created, a particular user is logged, whatever the condition is doesn’t matter, just that the tab should appear at certain times and not appear at other times.
In the code behind the condition block might look like this:

if (condition) then
tabSecond.Visible = False
end if

But this results in the Registered Script Control error.  Modify the condition block this way:

if (condition) then
dapSecond.EnableAJAX = False
tabSecond.Visible = False
end if

This should resolve the error

What was the issue?  I’m glad you asked.
The issue causing the error is that AJAX controls are registered with the AJAX script manager and cannot be unregistered, or moved.  Hiding an AJAX control is equivalent to moving it from the script.  In order to circumvent that we’re disabling AJAX on the control before it has a chance to be rendered and registered with the script manager.

This is a single that threw me for a long time, nevertheless the remedy is actually quite simple. Easy sufficient that i really don't understand why there is not much more documentation on it.

Here’s the scenario: You've got a module with two, or maybe more, achievable interfaces depending on the web page the module is additional to. The view handle features a blank important area and you cannot have copy crucial fields, blank or in any other case. How can you power the non-blank module control to point out around the page with out further coding?

The answer: make use of the module definitions.

Here’s how.

A number of assumptions very first:

You’ve developed a custom made DotNetNuke module.
You have at the very least two module controls in that module.
You've got a DotNetNuke set up to check on as well as the custom module is installed.

Now stick to these actions to show multiple view controls.

1. Log in as the host user, open the extensions page, and click the edit icon to edit your module
   
   

   

2. Your module already has a default definition that typically includes a view, edit and settings control.  The setup looks something like the picture below.  (Note: In editing this image I accidentally shortened the source paths.  The format should be DesktopModules/My Custom Module/View.ascx)
   
   

   

3. Click the “Add Definition” link next the “Select Definition” drop down.
   
   

   

4. On the new screen fill in the information to create the new definition and click “Create Definition”.  In this case I’m calling it “Definition 2″, but you’ll want to make your definition names descriptive, or whatever meets your naming convention needs.
   
   

   

5. Now you’ll have a fresh new module definition to fill out just like the default definition.
   
   

   

6. You can now add new module controls to the definition.  Click the “Add Module Control” link and fill out the form as a new View control by leaving the “Key” field blank.  Fill in the title field, select the source and leave the Type as “View”.
   
   

   

   
   
7. Update the definition and navigate to the web page in which you would like to incorporate the module. Incorporate the module towards the webpage. In the event you had already additional the module you’ll require to delete it and incorporate it once again or else DotNetNuke will not operate the code to add all of the see controls. Once you incorporate the module you ought to see each check out handle you produced a definition for look around the page as being a individual module occasion. In the event you do not, return and verify you accomplished the steps properly.
8. At this time whatever check out controls you really don't want to look on the web page, merely delete that instance from the module.
   

With all the introduction of the DDRMenu to DotNetNuke, we've experienced much more manage above what is rendered from the menu. This has authorized for a a lot more semantic menu and custom made styling for easy menus to mega menus. There are numerous methods to create the template that the DDR makes use of but we'll be using the token primarily based templating because it is quite easy.

Menu Template (Bootstrap Nav)

I copied the easy folder from your Gravity pores and skin that will come with DNN 7, which incorporates a manifest file “menudef.xml” and the “SimpleToken.txt” file. I updated the SimpleToken.txt file as follows:
Notice: this isn’t a tutorial on DDRMenu, just how to apply Bootstrap.

<ul class="nav nav-pills">
    [*>NODE]
    </ul>
    [>NODE]
        <li class="[?NODE]dropdown [/?][?SELECTED]active[/?]">
        [?ENABLED]
            <a href="[=URL]">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [?ELSE]
            <a href="#">[=TEXT] [?NODE]<b class="caret"></b>[/?]</a>
        [/?]
        [?NODE]
            <ul class="dropdown-menu">
            [*>NODE]
            </ul>
        [/?]
        </li>
    [/>]

1. Add the classes nav and nav-pills to the outer ul. Individually, I favor the simplicity in the Simple tablets nav that bootstrap gives. This appears to be the easiest to override with my own custom design and style as I have a tendency to use more flat UI’s in my style.
2. Include the category “dropdown” for the list merchandise if it's youngsters using the [?NODE] examination.
3. Add the category “active” for the listing product whether it is selected utilizing the [?SELECTED] examination.
4. Add a caret to the merchandise if it's a baby item.

Up coming, we are able to include the HTML and pores and skin object within the pores and skin as follows:

Logo and Menu pores and skin objects (Bootstrap Navbar)

<div class="navbar">
        <div class="navbar-inner">
            <span class="brand">
                <dnn:LOGO runat="server" id="dnnLOGO" />
            </span><!--/Logo-->
            <dnn:MENU MenuStyle="Simple" runat="server"></dnn:MENU>
        </div><!-- END navbar-inner -->
    </div><!-- END navbar -->

1. add link with class “btn” and btn-navbar”. Also, requires markup for collapse. You are able to use either JavaScript or information attributes.
2. Wrap dnn:MENU pores and skin item using a div using the adhering to class
   “nav-collapse” and “collapse” - this permits the menu to break down at smaller display screen sizes
   “pull-right” to drift the menu to the correct side, if you so desire.

Note: making use of this process will disable a menu merchandise which has children. In order that this is a click to open up motion. This can be to make things function much better for contact units.

The Simple Way to Install DotNetNuke

DotNetNuke is a Web-content management platform for those who use the Microsoft ASP.NET framework. Based on your company needs, whatever version of DNN you choose, it will be a significant cost saving venture over other options. Installing DotNetNuke is not a task well-suited for beginners to this sort of website framework. If you are familiar with websites, databases, and ASP.NET, you can use these instructions to learn how to install DotNetNuke.

Check the DotNetNuke installation requirements before getting started. To install DotNetNuke, you need a database with either Microsoft SQL Server 2005/2008 or SQL Express. If you have an older version of DotNetNuke 5.2 or earlier, you can use SQL Server 2000. You should also have a Microsoft IIS (Internet Information Services) with version 5 or higher, and the Microsoft .NET 3.5 SP1 framework. This service pack is available through the Windows Update feature.

Download the latest version of DotNetNuke to your computer, and unzip the file.

Use the FTP software of your choice to connect to your website, and upload the installation files into the directory of your choice. If necessary, create the directory where you want to install DotNetNuke on your server.

Select the folder where DotNetNuke is located. Click "Properties," choose the "Security" tab, and add the necessary user permissions. Use either the local ASP.NET service (for Windows 2000 and XP) or the local Network Service account (for Windows 2003, Vista, 2008, or 7). You should have permission to modify the folder.

• Open the IIS server console. Go to "Start" > "Run" > INETMGR. Click on the "websites" node, and select the "Default website" node.
• Right click on the DotNetNuke folder. Click "Convert to Application." If this option is not available, select "Properties" and add the application.

Install DotNetNuke with SQL Express.

• Open your web browser, and go to: http://yoursite.com/dotnetnuke.
• Walk through the installation wizard as presented on the screen. The database information should already be configured, and you should not need to change it.
• Look for the default login information for the "host" and "admin" users, which is shown when installation is complete.
• Log in immediately, and change the passwords to protect against hacking.

Install DotNetNuke with SQL Server 2005/2008 for your database server.

• Open SQL Management Studio, and connect to your database server.
• Walk through the installation wizard as presented on the screen.
• Create a new database by expanding the server node, then the databases node, and filling in necessary values for all the database properties.
• Set up the SQL user and security account, and choose the appropriate integrated-security or user-security setting under the "server/security" node.
• Open your web browser, and go to: http://yoursite.com/dotnetnuke.
• Walk through the installation wizard as presented on the screen. Choose SQL 2000/2005/2008, and follow the security steps according to the option chosen in the previous steps. Test the database connection.
• Finish the installation wizard, and look for the default login information for the "host" and "admin" users.
• Log in, and immediately change the passwords for those accounts to protect against a hack.

Best and Cheap DotNetNuke Hosting Provider

Are you looking for best and cheap DotNetNuke Hosting Provider? ASPHostPortal is the answer. ASPHostPortal.com is a windows-based hosting service provider. ASPHostPortal.com offers the most reliable and stable DotNetNuke 7.3 web hosting infrastructure on the net with great features, fast and secure servers. Our hosting can be done via USA, Amsterdams or Singapore based server. Depending on your requirements, we can scale so we can deliver the right service for the right price. All of our windows hosting plan supports DotNetNuke 7.3 and you can install DotNetNuke 7.3 with just one click.

Cart Viper is The Best DotNetNuke eCommerce Solution

If you read this article, of course you interest with ecommerce. In this article, we will tell you that you now you will develop your online store easily with DotNetNuke platform. If you are already using DotNetNuke then you will know what a great platform it is to build rich and engaging websites but what if you could use the same platform to run an online DNN shop?

Why you should using Cart Viper?

Cart Viper is an ecommerce solution built for DNN providing a PCI compliant online store for your business. You will start to sell online today using the simple to use ecommerce store easily. From now you will sell anything; physical products, digital downloads and events. Using Cart Viper you can create a fully functioning online shop within 30 minutes.

Is Cart Viper The Best DotNetNuke Store?

The answer absolutely is YES. In their official website, they said that, “Since starting Cart Viper we've added hundreds of new features and improvements all with the aim of making the best dotnetnuke store available on the market. A great product is no good without great support so we are dedicated to providing help and support so that you can get the best out of our product. Take a look at the feedback we have received from our satisfied customers.”

Features of Cart Viper

There are some features of Cart Viper:

• Categories and Sub-Categories – You can create and manage an unlimited number of product categories. In here you also can find SEO optimized product categories page - define the category URL, META description and title tags.

• Products – You can create an unlimited number of products. Automatic re-sizing of product images (small, medium, large) based on your predefined image size.
• Product Variants - Choose the variant option display e.g. dropdown list, checkbox, radio button, textbox, multi-line textbox or image uploader. Track stock quantities for each product variant, so you know exactly how many of each product variation you have in stock.
• Catalog Localization - Ability to enter categories and products in multiple languages. Categories and products will fully localize to the current language that is being viewed by the user.
• Product Offers - Create and manage product offers. Define start, end date and offer price. Offer is applied and removed from a product without any user interaction.
• Coupons - Define rules for each coupon. e.g. minimum subtotal, can be used multiple times, start date, end date, customer email address, etc. Offer a monetary or percentage discount.
• Promotions - Create store wide promotions, so every product has a specific discount during the given period. Create category wide promotions, so every product in the category has the specific discount during the given period.
• Product Discount Bundles - Create product discount bundles where a user receives a discount if they purchase 2 or more items at the same time. Promote up-selling and maximise each sale via product discount bundles.
• User Specific Pricing - Define a product price for a specific user of your DNN site. Define a product price for a specific role of your DNN site. When browsing the store the individual user price is displayed to that user.
• Digital Downloads - Define which products have a digital download. Digital downloads now support PDFs as a valid file type. Allow admin to define how long / how many times a user can download a digital download after they have purchased it.
• Product Comparison - Allow users to select up to 4 products then compare them side by side! Store admin defines the product details they can compare e.g. weight, size, model number etc. Allow the user to quickly and easily see the advantage of 1 product over another.
• Wishlists - Wish list automatically updated if admin deletes / edit a product in a user’s wish list. Anonymous users can create wish lists, and then they will automatically be transferred into their user account if they then sign in to your store. Customers can make their wish list public and send friends a link to view the wish list.
• Product Visualizer - Allow a user to see a mockup of what their product will look like once they have made their specific choices. e.g. select text or upload an image.
• Product Reviews & Ratings - Enable / disable product reviews. Product average rating calculated from customer reviews. Product reviews approved by admin before appearing on site.
• Shipping - Enable / disable shipping to be calculated on an order. Support an unlimited number of shipping providers so customer can select when they checkout e.g. FedEx, UPS, default, etc
• Tax & VAT - Based on stores location and the users billing address Cart Viper automatically works out if you need to charge VAT or tax. Define VAT rates for: Zero rated product,Reduced rate products & Standard rate products. Assign each product to a VAT rate.
• Payment Methods - Let customer pick between online or offline payment methods at the point of checkout. Real time credit card payments (Mastercard, VISA, Solo, Switch, Amex and Discover). Accept offline payment methods (cash on delivery, cheque, purchase orders, etc) with or without Real time payment method as well.
• Payment Gateways - Optional ability to apply a percentage or fixed amount surcharge to an order placed with Paypal Standard. Recurring billing support when using Authorize.net payment gateway, manage subscriptions directly from Cart Viper, recieve notifications when card declined.
• Cart & Checkout - Advanced jQuery add / edit / delete items shopping cart functions. Separate mini-cart control that can be added to any content pane. User friendly wizard style checkout screen.
• Store Administration - Quick Install for Creating a New Store. Simple intuitive administration UI. Optionally assign DotNetNuke roles to admin tasks as product management, order management etc. Product moderator feature - create a new setting that allows the a DNN role to be entered users with this role can add products however they need to be moderated before appearing in the store front.
• Catalog Workflow and Version History - Define if that all changes to the store catalog requires moderation. Ability to accept / decline changes, with email notifications.
• QuickBooks Integration - Automatically transfer orders from Cart Viper into QuickBooks.
• Order PDF - Store admin or customer can download a PDF receipt of any order that has been placed. Admin can define an image along with header and footer text to brand the PDF as per your needs.
• Sales Reporting - Cart Viper automatically calculates your sales data for the current day and at a glance allows you to see how that compares to yesterday and the average of the last 30 days. View sales data by product or category for specific date you enter. Export sales data to .XLS format.
• My Account Module - Separate my account module included. Edit their account profile settings - billing / shipping address etc. Users can view / search through their order history.
• Product News Letter - Separate product newsletter module, allow users to sign up to your store product newsletter. Product newsletter automatically sent with no human interaction.
• Product Widget Module - Separate product widget module that can be used to display products anywhere on your DNN portal. Select products to display in product widget module by: random, top sellers, by category, individual selection, products currently on special offer and newly added.
• RSS 2.0 Feeds - Optionally expose RSS 2.0 feeds based on the product data in your store. 3 different RSS 2.0 feeds: top selling products, newly added products and featured products.
• HTML Email Templates - All emails that the store sends are HTML based so you can customize then to suit your needs. Fully HTML enabled so you can brand the emails as per your needs using CSS and images.
• Define the Store Currency - The following currencies are supported by Cart Viper: United States Dollar (USD) , Great British Pound (GBP), Euro (EUR), Australian dollars (AUD), Canadian dollars (CAD), Mexican peso (MXN) Swiss francs (CHF), Singapore dollar (SGD), Thailand Baht (THB), New Zealand Dollar (NZD), Phillipine Peso (PHP), Czech Koruna (CZK) and Mexican Peso (MXN).
• Donations - Optionally allow customers to place donations. Define predetermined amounts with the customer able to select or enter their own donation amount. Allow the customer to enter a name associated with the donation.
• Multi-language Support - They currently have the resource files translated into English, French, German, Spanish and Dutch. However Cart Viper can be translated into any language you require!
• Multiple Portals Supported - Cart Viper can be installed on multiple parent and child portals. Each portal would need to have its own license.
• Advanced Templating - Razor Template Support. Responsive store template, create a great store experience for desktop, tablet and mobile users. Data and presentation kept separate allowing you to create your own templates without any programming knowledge.
• Google Analytic eCommerce & Event Tracking - Full eCommerce & event tracking support integration into Google analytics. Track 25 different events inside your store. Provides detailed statistical analysis how customers are users your store. Quickly and easily find customer trend and shopping habits!
• DotNetNuke Versions Supported - Cart Viper requires version 5.x, 6.x, or 7.x of DotNetNuke. Works in both Full Trust and Medium Trust environments.

Best and Cheap DotNetNuke Hosting for Your DotNetNuke Site

ASPHostPortal.com is the best and cheap windows-based hosting service provider. ASPHostPortal.com offers the most reliable and stable DotNetNuke 7.3 web hosting infrastructure on the net with great features, fast and secure servers. Our hosting can be done via USA, Amsterdams or Singapore based server. Depending your requirements, we can scale so we can deliver the right service for the right price. All of ourwindows hosting plan supports DotNetNuke 7.3 and you can install DotNetNuke 7.3 with just one click.