How To Fixing PortalSettings issue on multilingual Websites in DNN 7.3.2

Today I will share about How to fixing issue on multilingual website in DNN 7.3.2.
DNN 7.3.2 enhanced the stored procedure for saving Site Settings to add multilanguage support, unfortunately it missed to include proper handling of language specific settings within the business layer and some other aspects. As effect, DNN 7.3.2 fails to load site settings for multilingual sites and renders an error message.
I created a full solution to add localization support for website settings, which is scheduled to be included with DNN 7.4.0, meanwhile you may run the script below from Host > SQL, in order to fix this issue.

"NOTE: DO NOT APPLY TO DNN 7.4.0 OR LATER"

This fix is also included in TurboDNN 0.9.3 ff. - the solution to improve database performance of DNN, which might be downloaded for free from here. (Please take the time to read instructions enclosed.)

-- ensure, last modified is not Null (should not exist)
UPDATE {databaseOwner}[{objectQualifier}PortalSettings]
 SET   LastModifiedOnDate = '2000-01-01'
 WHERE LastModifiedOnDate is Null
GO
IF OBJECT_ID(N'{databaseOwner}[{objectQualifier}GetPortalSetting]', N'P') IS NOT NULL
    DROP PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSetting]
GO
CREATE PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSetting]
    @PortalID    Int,     -- Not Null
    @SettingName nVarChar(50), -- Not Null
    @CultureCode nVarChar(50) -- not Null
AS
BEGIN
 SELECT TOP (1)
 SettingName,
 CASE WHEN Lower(SettingValue) Like 'fileid=%'
 THEN {databaseOwner}[{objectQualifier}FilePath](SettingValue)
 ELSE SettingValue
 END   AS SettingValue,
 CreatedByUserID,
 CreatedOnDate,
 LastModifiedByUserID,
 LastModifiedOnDate,
 CultureCode
 FROM  {databaseOwner}[{objectQualifier}PortalSettings]
 WHERE PortalID    = @PortalID
   AND SettingName = @SettingName
 ORDER BY LastModifiedOnDate DESC
END
GO
IF OBJECT_ID(N'{databaseOwner}[{objectQualifier}GetPortalSettings]', N'P') IS NOT NULL
    DROP PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSettings]
GO
CREATE PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSettings]
    @PortalId    Int,            -- not Null!
    @CultureCode nVarChar(20)    -- not Null!
AS
BEGIN
 SELECT
 SettingName,
 CASE WHEN Lower(SettingValue) Like 'fileid=%'
 THEN {databaseOwner}[{objectQualifier}FilePath](SettingValue)
 ELSE SettingValue
 END   AS SettingValue,
 CreatedByUserID,
 CreatedOnDate,
 LastModifiedByUserID,
 LastModifiedOnDate,
 CultureCode
 FROM  {databaseOwner}[{objectQualifier}PortalSettings] P
 JOIN  (SELECT PortalID, SettingName SN, Max(LastModifiedOnDate) MD
        FROM {databaseOwner}[{objectQualifier}PortalSettings]
 WHERE PortalID = @PortalId
 GROUP BY PortalID, SettingName) S
   ON P.PortalID = S.PortalID AND P.SettingName = S.SN AND P.LastModifiedOnDate = S.MD;
END
GO

UPDATE: this fix has been included with DNN 7.3.4, you shouldn't need it, if you upgraded to 7.3.4 and don't apply it to DNN 7.4.0 or later.

DNN 7.3 has been released and contains lots of changes for performance and stability, bug fixes and some new features.
I was first alerted to an issue with Url Master and DNN 7.3, who found that the API cleanup in 7.3 had removed an old DNN API that Url Master was leveraging, which meant that the site would stop working after the 7.3 Upgrade.   The error you get if you upgrade DNN without first upgrading Url Master to 2.8.2 is this:

500 Internal Server Error
The requested Url does not return any valid content.
Administrators
Change this message by configuring a specific 404 Error Page or Url for this website.

This is the default URL Master error output (unless you have debug mode enabled) which intentionally hides the actual exception for security reasons.  If you open the event log, you’ll find something like this:

Exception: Method not found: 'DotNetNuke.Entities.Portals.PortalAliasCollection DotNetNuke.Entities.Portals.PortalAliasController.GetPortalAliases()

The solution is that you need the latest version of the Url Master module, version 2.8.2, which uses a newer method to get the portal alias data.
Get the Url Master Module 2.8.2 Download

If you haven't upgraded to DNN 7.3 already, you must upgrade to 2.8.2 before upgrading.

Just download the 2.8.2 install package, and upgrade via the Host->Extensions page.  You do not need to update your licence – this version is available to *all* existing Url Master customers.

If you have already upgraded and have found that your site is dead with this error, then you will need to manually patch the files.  Here are the steps:

• Download the Url Master install package
• Extract the zip file locally on your computer to a folder, so you can see the files inside the zip
• Within the extracted zip file, you will see 4  files.
• Copy these 4 files into the \bin directory of your site that needs to be upgraded.  Use FTP or copy/paste or any other method to get it into the \bin directory.
• Once they are copied into the bin directory, try the site again.  It should start and run normally.
• Once your site is running again, install the (compressed) file as normal through the Host->Extensions page.  This won't change the versions installed, but it will bring your extensions catalog up to date.

I appreciate if people spread these instructions to those who are running Url Master and are intending to upgrade to 7.3 as a preventative measure.

Quick tips : Getting rid of spam users

After getting a couple of questions, I'd like to provide options for getting rid of spam users, which is cumbersome via UI, if thousands of registration have been added by a bot.
Unfortunately, it is not as easy as just deleting items from a single table, as user Information is distributed in multiple tables inside the database, therefore we need.
You are in a comfortable situation, if your site is using verified or private registration - in this case all spam users are unauthorized and you simply need to hit "delete unauthorized users" in Admin > User Accounts.
In all other cases, you will need to identify the users to delete from the database and mark as "deleted", in order to use "remove deleted users" (hard-delete) those users from all tables.

ALWAYS START WITH A DATABASE BACKUP!!

If your site only has a host and admin user you would run the following statement inside Host > SQL (check "run as script" in all DNN versions prior to 7.3):
UPDATE {databaseOwner}[{objectQualifier}UserPortals]
 SET   isDeleted = 1
 WHERE UserID NOT IN (SELECT UserID FROM  {databaseOwner}[{objectQualifier}Users
                                    WHERE isSuperuser = 1 OR UserName Like 'Admin')
If you may identify all users by registration date, e.g. since first of November, you would run
UPDATE {databaseOwner}[{objectQualifier}UserPortals]
 SET   isDeleted = 1
 WHERE UserID NOT IN (SELECT UserID FROM  {databaseOwner}[{objectQualifier}Users]
                                    WHERE isSuperuser = 1 OR UserName Like 'Admin' or CreatedOnDate < 2014-18-11)

Of course, this will become more difficult, if regular users registered the same time. You may consider creating a role "verifiedUsers" and move all regular users manually into this group. Now the command would look like

UPDATE {databaseOwner}[{objectQualifier}UserPortals]
 SET   isDeleted = 1
 WHERE UserID NOT IN (SELECT UserID FROM  {databaseOwner}[{objectQualifier}Users]
                                    WHERE isSuperuser = 1 OR UserName Like 'Admin' or CreatedOnDate < 2014-18-11)
   AND UserID NOT IN (SELECT UserID FROM {databaseOwner}[{objectQualifier}vw_UserRoles]
                                    WHERE RoleName Like 'verifiedUsers')

Afterwards you may use "Remove Deleted Users" link in Admin > User Management, to delete all rows.
For DNN Versions prior to DNN 7.3.1, you need to delete user folders manually, which reside nested inside users subfolder of the portal folder. Unfortunately, it is difficult to identify all folders from deleted users, but you may delete all empty folders without subfolder and files inside, as the folder for a still existing user will be re-created, once the user logs in again for the first time. You may use the following command (sing a command line on the server, while being inside the users folder)
for /f "delims=" %i in ('dir /ad /s /b') do @rd "%i"
Finally, you should enter file manager in DNN Admin menu and perform a recursive sync to get rid of all folder entries and folder permissions in the database

I am pleased to announce that DNN Platform 7.3.4 has been released. The 7.3.4 release is a stabilization release. DNN 7.3.4 is a smaller maintenance release than normal and is focused on addressing the most serious platform issues. It is expected that this will be the final platform release prior to DNN 7.4.0 which is expected to be released in January 2015. Once again the community has provided a number of significant fixes for this release. I look forward to increasing this level of participation coming in future releases.
You can find all of the issues resolved in this release in our issue tracker. Download 7.3.4 from the DotNetNuke Downloads page.

Major Highlights

• Fixed issue where site settings were not updating correctly in multi-language installations
• Fixed issue where partial site templates were not working correctly with child sites
• Fixed issue where links created in Telerik RadEditor were not correct
• Fixed issue where search results might be duplicated
• Fixed issue where user could not change default value for a profile property
• Fixed issue where a file uploaded from the web is not visible in the Host File Management
• Fixed issue where ControlBarController returned invalid JSON
• Fixed issue where you couldn't add a module in a spanish language site
• Fixed issue where a clustered index was missing from a search table
• Fixed issue where uploading an ICO file failed
• Fixed issue where HTML Editor Permissions were not working correctly
• Fixed issue where popups were not centered on the screen
• Fixed issue where popup iframe is not initialized correctly
• Fixed issue where AUM was not correctly handling 301 redirects
• Fixed issue where multiple region/country controls in a profile did not work correctly
• Added ability to save localized lists to resource file
• Added method to remove all subscriptions from a ContentItem

Security Issues

• None

Certainly one of the commonest queries which i get by way of the community forums on this website, or via e-mail is "How does one get your websites to operate so fast". Although not excellent, my web sites normally operate somewhat more quickly than your typical DotNetNuke 7.3 websites. Formerly I have stored the exact particulars of my changes to myself, nevertheless, with a litle encouragement from the neighborhood I've chose to share the full context of the changes that i make into a default DotNetNuke set up to acquire better baseline performance, as well as added products that i do to aid when i actually want that "boost".

Overview

To begin with I want to begin out by declaring that a great deal in the details that's shown listed here could be located in previous website postings. Posts this sort of as DotNetNuke Host Options Explained, DotNetNuke Scheduler Explained, DotNetNuke Overall performance Options Defined, and straightforward DotNetNuke Performance Enhancements. Are good beginning factors for a few of the element driving my recommended adjustments.

The subsequent changes are merely the configurations that i have found for being the very best "baseline" configurations. Consideration is required in regards to the web site setup, update frequency, traffic, hosting environment and users to ensure that you have the correct set up for your particular atmosphere. I'll talk about the options section by segment, merely noting the modifications which can be created. Remember to reference the specific "Detail" doc for more information.

DISCLAIMER: Adhere to these suggestions as a manual only, I am not responsible for any results of employing these adjustments.

Host -> Host Options Changes
The first place I pay a visit to may be the Host Options page. There are a selection of key updates and adjustments required on this segment. Again, only changes are noted right here.

Appearance
In this segment I uncheck the "Show Copyright Credits" box

Advanced -> Authentication Settings
Within this segment I uncheck "Enabled" for almost any provider that will not be utilized in the portal, normally the LiveId and OpenId companies

Advanced -> Performance Settings
On this area I change the "Module Caching Method" to Memory. the "Performance Setting" to HeavyCaching. As well as the "Compression Setting" to GZip Compression.

Advanced -> Other Options
In this section I modify the "Scheduler Mode" to Timer. I enable the "Event Log Buffer" and i disable the "Auto-Sync File System" alternative

They are the commonest Host Options adjustments which i total. Based within the website I'll make a couple of other little edits.

Host -> Scheduler Changes
The largest alter that i make right here would be to modify the "SearchEngineScheduler" task to run normally as soon as every 12/24 several hours. This reduces a big load around the server.

Other Modifications
From a DotNetNuke configuration alter which is all that I modify. Overall these adjustments typically outcome in extremely noticable efficiency advancements, but often times it just isn't adequate to maintain the web sites operating as smooth as possible. So according to the specific situation I have numerous other things which i function with.

Normal Purging of Occasion Log
As a lot of people which have utilized DotNetNuke have identified the EventLog table could become a very troublesome hinderance within the performance facet of a web site. Enabling the Event Log Buffer helps reduce the consequences of the huge EventLog, nonetheless, the most effective policy is always to thoroughly clean the EventLog on a normal foundation.

I try this one of two methods. By myself sites I have an SSIS package deal inside of SQL Server that truncates the desk each 24 hrs. On customer web sites I make use of my Scheduled SQL Employment module to keep a seven working day rolling historical past of the EventLog information. The key here is the fact that we must keep the occasion log tiny.

Skin Choice and Menu Provider
The next item of thought is actually a multi-part thought. I target on finding CSS primarily based pores and skin layouts that use 3rd party menu parts this sort of as Telerik and Css NavMenu. With a straightforward pores and skin modify to sites I've seen webpage load occasions which have decreased by more than 50%.

Discovering an excellent designer that creates well laid-out skins with 3rd get together menu suppliers is a crucial overall performance enhancement, a minimum of in the page. I've NOT benchmarked these numbers although because DNN 4.six.2, so the core menu company might have much better performance.

Compression/Caching Modules
Like a last stage, if I actually need to get the most performance out of a website I will often lean towards Snapsis PageBlaster as being a good alternative. I at present use PageBlaster on this website only and also have had really excellent luck with it, though when configuring the module you have to be cautious to test all functionality very first. This was another change that after applied I seen really noticeable efficiency advancements.

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.

Best and Cheap DotNetNuke 7.3 Hosting

DNN 7.3 has been released and contains lots of changes for performance and stability, bug fixes and some new features. The DNN 7.3 release improves the run-time characteristics of the platform in a variety of ways. End users will notice faster page response time and administrators will appreciate a more responsive user experience, especially on larger scale web sites. Server processing has been optimized and resource consumption has been dramatically reduced, resulting in greater scalability and improved site density in all infrastructure environments.

New Features of DotNetNuke 7.3 Hosting

DotNetNuke 7.3 includes a number of new features and enhancements that will benefit users and developers alike along with a large number of bug fixes. Here is the new features of DNN 7.3:

Platform performance enhancements
dnnPanels enhancements
HTML 5 tags as skin panes
Added support for Google Analytics tracking code to support Display Advertising
Save/Restore Module with Settings/Content

How to Reset DNN 7.3 Password

You can use the below steps to reset the DNN 7.3 password :

1. Open SQL Query Analyzer – Connect to your dotNetNuke database.

2. Paste the following Stored Procedure code into the window,

ALTER procedure [dbo].[uap_ResetPassword]
@UserName NVarChar(255),
@NewPassword NVarChar(255)
as
begin
Declare @PasswordSalt NVarChar(128)
Declare @ApplicationID NVarChar(255)
Declare @ApplicationName NVarChar(255)
Set @ApplicationID = (SELECT [ApplicationID] FROM aspnet_Users WHERE UserName=@UserName)
Set @ApplicationName = (SELECT [ApplicationName] FROM aspnet_Applications WHERE ApplicationID=@ApplicationID)
Set @PasswordSalt = (SELECT PasswordSalt FROM aspnet_Membership WHERE UserID IN (SELECT UserID FROM aspnet_Users WHERE UserName=@UserName))
–select @ApplicationID, @ApplicationName
declare @RetVal as int
Exec @RetVal = dbo.aspnet_Membership_ResetPassword @ApplicationName, @UserName, @NewPassword, 10, 10, @PasswordSalt, -5
return @RetVal
end

3. Now you can reset your DotNetNuke 7.3 passwords by simply opening up SQL Query Analyzer, connecting to your dotNetNuke database, then typing uap_ResetPassword ‘username’, ‘newpassword’.

Reason to Choose DotNetNuke 7.3 Hosting with ASPHostPortal.com
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 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.

DotNetNuke is an open source CMS based on Microsoft .Net technology. DotNetNuke can be easily installed and hosted. In general, DotNetNuke framework allows individuals to do whatever they wish with the application framework both commercially and non-commercially, with the simple requirement of giving credit back to the DotNetNuke project community. In this article, I will tell you how to automate the packaging of your DNN Module.

DotNetNuke is a program that runs on Microsoft ASP.NET. It is also a framework, meaning, it is a program that is designed to be extended. One of the ways you extend the framework is to create modules. These modules are installed inside a DotNetNuke installation and when they run in that DotNetNuke installation they extend the framework to create a DotNetNuke website also called a portal.

Here are the steps for automate the packaging of your DNN Module:

• Delete all source code and start over from scratch with my templates installed. If you really don’t want to go through step #1, you can skip it, but you must then go on to Step 2 below

• Open your project in Visual Studio

• Install the MSBuildTasks project from Nuget:

PM> Install-Package MSBuildTasks

• Create a BuildScripts folder in your project

• Add two files

ModulePackage.targets

MSBuild.Community.Tasks.Targets

• Right click on the project in Visual Studio Solution Explorer and choose “Unload Project”

• Save changes if prompted

• Right click on the unloaded project and choose the Edit option

• At the bottom of the file, before the </Project> section add

<PropertyGroup>
  <Extension>zip</Extension>
  <DNNFileName>CHANGEME.dnn</DNNFileName>
  <PackageName>CHANGEME</PackageName>
  <MSBuildCommunityTasksPath>$(SolutionDir)\Build</MSBuildCommunityTasksPath>
</PropertyGroup>
<Import Project="BuildScripts\ModulePackage.Targets" />
<Target Name="AfterBuild" DependsOnTargets="PackageModule">
</Target>
<Import Project="$(SolutionDir)\.nuget\nuget.targets" />

• Change the “CHANGEME” text to match the name of your .DNN file and the name of the ZIP file that you want the package created as.

• Save the Project changes.

• Right click on the project in Solution Explorer and choose Reload Project.

• Switch into Release mode in Visual Studio and do a Build of your project.

• This should create two files, ModuleName_Version#_Install.zip and ModuleName_Version#_Source.zip.

What I typically do then is install the module to a test DNN install to make sure that everything is working correctly. You’ll want to make sure that the ZIP files created contain all the right files, and they get installed correctly, so a test installation is the best way to go through that process.

If something fails, try to track it down, then do another Build in Release mode, rinse and repeat the installation process in your test install until you get everything working properly.

Now going forward, after you do a release, you go into your AssemblyInfo file, change your version number there, and into your .DNN File and change your Version number there. Next time you build in Release mode the module will create a new VERSION number ZIP file, leaving your last version builds there as well.