DotNetNuke Hosting with

BLOG about DotNetNuke CMS, latest technology and Special DotNetNuke Hosting Package with

DotNetNuke 7.3 Hosting with :: Set Cache in DNN application/ site

clock Desember 9, 2014 07:44 by author Ben

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>

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

DotNetNuke 7.3 Hosting - :: How To Fixing PortalSettings issue on multilingual Websites in DNN 7.3.2

clock Desember 5, 2014 08:33 by author Ben

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.


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
IF OBJECT_ID(N'{databaseOwner}[{objectQualifier}GetPortalSetting]', N'P') IS NOT NULL
    DROP PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSetting]
CREATE PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSetting]
    @PortalID    Int,     -- Not Null
    @SettingName nVarChar(50), -- Not Null
    @CultureCode nVarChar(50) -- not Null
 CASE WHEN Lower(SettingValue) Like 'fileid=%'
 THEN {databaseOwner}[{objectQualifier}FilePath](SettingValue)
 ELSE SettingValue
 END   AS SettingValue,
 FROM  {databaseOwner}[{objectQualifier}PortalSettings]
 WHERE PortalID    = @PortalID
   AND SettingName = @SettingName
 ORDER BY LastModifiedOnDate DESC
IF OBJECT_ID(N'{databaseOwner}[{objectQualifier}GetPortalSettings]', N'P') IS NOT NULL
    DROP PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSettings]
CREATE PROCEDURE {databaseOwner}[{objectQualifier}GetPortalSettings]
    @PortalId    Int,            -- not Null!
    @CultureCode nVarChar(20)    -- not Null!
 CASE WHEN Lower(SettingValue) Like 'fileid=%'
 THEN {databaseOwner}[{objectQualifier}FilePath](SettingValue)
 ELSE SettingValue
 END   AS SettingValue,
 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;

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.

DotNetNuke 7.3 Hosting With :: DNN 7.3 Issue with Url Master

clock Desember 2, 2014 07:12 by author Mark

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.
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.

DotNetNuke 7.3 Hosting with :: How to Resolve the Registered Script Control Error in DotNetNuke 7

clock November 28, 2014 05:14 by author Mark

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>
     <DNN:DNNTab runat=”server” Label-Text=”Properties” ID=”tabSecond”>
       <dnnui:DnnAjaxPanel runat=”server” ID=”dapSecond”>
         <asp:Label runat=”server” ID=”lblMessage”></asp:Label>

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.

DotNetNuke 7.3 Hosting with :: How to Integrate DotNetNuke with SharePoint?

clock Augustus 18, 2014 10:14 by author Kenny

What is DotNetNuke?

DotNetNuke Platform, formerly called DotNetNuke, is a free, open source website builder and content management system based on the .NET framework. It is a tool designed to be used from a web browser that can create any type of website, from small business sites to online communities and intranets. In this article we will tell you about how to integrate DotNetNuke with SharePoint.

Integrate DotNetNuke with SharePoint

  1. Good knowledge of SharePoint and DotNetNuke - This particular approach helps in easy as well as seamless integration of both the document management system and the software making it easy for content monitoring along with modification. It is important to have good knowledge of the software as well as the application before taking up integration.
  2. Always integrate with SharePoint 2007 and 2010 – This particular objective helps you enjoy the best benefits of both the DotNetNuke along with the document management system. After all, it helps publishing fresh contents extracting it straight from the SharePoint Document library. The published documents are carefully protected by the role based security network of DNN. 
  3. Always publish documents that are approved for display – Undertaking this particular approach always helps you to avoid any sort of interference with the team. This helps you ensure the use of a streamlined alongside a collaborative procedure that helps in effective management of the document. Additionally, it also allows you to share the best documents that are carefully edited and ready for use. 
  4. Ensure consistent permission throughout the work – This particular objective if maintained right helps preventing any sort of unauthorized access thereby, ensuring a secure digital asset management. Additionally, it also helps preventing the redistribution of assets that are digital. 
  5. Make use of views and not folders – This helps you ensure having unlimited flexibility along with extreme level of granularity. It is also important for you to be able to combine the properties easily and this particular approach helps in successful combination. The biggest advantage rests with the fact that it helps reducing overall risk alongside human error. 
  6. Synchronize the deletes – Taking up this particular approaching during the process of integration also helps avoiding the errors of “file not found” during the successful execution of removal of files. This particular approach of cleaning also ensures reduction of unimportant database clogging, duplication, overall risk, and human errors. 
  7. Enabling of error notification is must – This specific task helps in automatic synchronization eliminating the need of active viewing or monitoring of the document in concern. This result in a smooth process that helps you to lessen the effort along with the time required for content monitoring. 
  8. Avoid the firewall – Always make sure that the SharePoint server can enjoy an easy access to the DotNetNuke server. This helps in smoother as well as better content management without any modification of security policies. 
  9. Allow filtering of documents to be transferred – This particular approach helps the users to filter the documents easily through the integrated SharePoint filtering views. This helps the users to make use of the Create View UI and need not rely upon two different sets of filters.

DotNetNuke 7 Hosting with :: Is DotNetNuke The Best Application for Developers, End Users and Organization?

clock Augustus 14, 2014 12:41 by author Kenny

Is DotNetNuke The Best Application for Developers, End Users and Organization?

Based on the.NET framework by Microsoft, DotNetNuke is a content managing system for websites. One of its advantages is the fact that the framework's Community Edition is open-sourced and has an MIT free software license, allowing free download, usage, modification, and extension. This, combined with the modular structure of the framework, has allowed various third-party developers to write and publish additional modules and upgrades to the basic package. Professional and Enterprise editions of DotNetNuke are paid for, but offer better tech support and certain features critical for business-level web-site management. However, the Community edition also receives a lot unofficial tech support from the extensive user and modder community.

DotNetNuke for Developers

DotNetNuke is a brilliant combination of Content management System (CMS) and Web application development framework. This adaptable architecture allows developers to effortlessly add functionality or make changes in the look of the website through addition of DotNetNuke applications. There are lots of websites where you can find free applications, you can use or customize these applications according to your need. That is reason DotNetNuke has become the first choice of developers.

DotNetNuke for End Users

DotNetNuke is very good tool for end users as they can within minutes post contents on the websites.This powerful and simple tool allows end users to modify the content without support from IT personnel.

Systems administrators find the granular security model very useful as they can define accessing rights for the end users. Both end users and administrators find it extremely helpful as the end users enjoys the freedom to post and modify content as per their wish and system administrators need not to be bothered about the rest of the website being modified as they have defined the extent of access.

We are in an era where internet is considered to be the principal source to find out reliable information. It gives you a platform to reach out to people and to know about their views also.People can write their views and it gets online for others to read.A positive article will absolutely add feather in your cap but a wrong or misleading one can spoil image of the company. Content Approval Workflow feature is the perfect solution for it and it takes web content controls one step ahead. In this your website is configured with custom approval workflows so whatever changes is made to the website, needs to be approved by authored person before it gets online. This helps you to monitor the quality and content of the article. This path breaking Content Approval Workflow feature is available in DotNetNuke Enterprise and Professional Editions.

DotNetNuke for Organization

Organization needs to make changes to websites on a regular basic. The flexible and reliable Content management platform of DotNetNuke allows organization to swiftly execute wining web strategies.Using DotNetNuke application you can easily control and change the look of the website.

The DotNetNuke Enterprise and Professional edition are reasonably priced and have very good technical support. Their free edition is known as Community Edition which you can download from internet and use it.

DotNetNuke 7.2 Hosting with :: DotNetNuke Mobile Friendly

clock April 2, 2014 09:56 by author Kenny

Good news, no you can adapt DotNetNuke portal to mobile devices without changing your existing desktop experience. The latest trend in web development is exciting to say the least - with increasing in Mobile device penetration around the globe. Mobile devices already have displaced many of the fixed-location technologies especially in rural in developed world or countries like India Brazil and China that are currently filling the global economic growth. MobiNuke is exposing a rich set of mobile device capabilities available to be used by module or skin developers.

Main Features

  1. You will apply separate skins for mobile experience.
    It can be when you want to set different skins that will be applied when pages are accessed from mobile devices. Don’t worry it will not change the skin for your desktop browsers. And now skin designers can develop mobile friendly skin sets together with desktop skins.
  2. Mobile devices access the portal through a lighter page.
    It will be fast, because anything that is not needed by a mobile device is cleaned out. The content type and MIME type are set to specific values for mobile browsers.
  3. It’s up to you for enable or disable any existing modules for mobile context or for PC.
    You can set some modules to show only on PC and others only on mobile devices. You can do different set up for each page.
  4. Support for mobile versions of existing modules.
    Developers can extend their modules for mobile context.
  5. Expose mobile device capabilities.
    Developers can get properties such as device type, screen dimensions, if JavaScript or online video is supported and more than 500 other mobile device properties.

How to Make it Work

  • Download and install MobiNuke through Host->Module Definitions-> Install New Module.
  • Add mobiNuke to any page. It will add itself to all the pages and will act as an extra setting.
  • Click on Mobile Settings to configure general settings and page specific settings for mobile access.

Technical Details

MobiNuke contains 5 components:

  • A httpModule that redirects request coming from a mobile device to DefaultMobi.aspx
  • A DotNetNuke Module with the following functions:
      - When added for the first time it will auto-configure itself to be present on all pages;

      - Manage the skin to be loaded when the page is accessed from a mobile device;

      - Preview the page close to the way it looks on a mobile device;

      - Enable or disable tab modules for mobile pages;
  • A DefaultMobi.aspx page for mobile context that has the same function as Default.aspx. Anything that is not usable on mobile devices is cleaned out.
  • A set of minimal skins suitable for mobile browsing. Currently the mobile skin contains only the ContentPane. It only shows the corresponding modules from the ContentPane of the desktop skin.
  • A mobile friendly navigation provider.


We’re a company that works differently to most. Value is what we output and help our customers achieve, not how much money we put in the bank. It’s not because we are altruistic. It’s based on an even simpler principle. "Do good things, and good things will come to you".

Success for us is something that is continually experienced, not something that is reached. For us it is all about the experience – more than the journey. Life is a continual experience. We see the Internet as being an incredible amplifier to the experience of life for all of us. It can help humanity come together to explode in knowledge exploration and discussion. It is continual enlightenment of new ideas, experiences, and passions

Author Link

 photo ahp banner aspnet-01_zps87l92lcl.png

Corporate Address (Location)

170 W 56th Street, Suite 121
New York, NY 10019
United States

Tag cloud

Sign in