DotNetNuke Hosting with ASPHostPortal.com

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

DotNetNuke Hosting - ASPHostPortal.com :: How to Edit the Privacy Statement on Your DotNetNuke Site

clock Oktober 6, 2016 20:32 by author Armend

How to Edit the Privacy Statement on Your DotNetNuke Site

You will eventually find the need to edit your DotNetNuke privacy statement.  Whether it is to add statements for COPPA compliance, DART cookies, third party vendors , or a number of other situations, the default statement just does not include everything you need.

The first time I decided to edit this statement, finding it was no small task.  Therefore, I thought I would lay out an easy to follow tutorial which, hopefully will be useful to you, and one which I can refer back on the next time I need to edit my own. This example is from DotNetNuke version 6.2.1, but the procedure is not so different in other versions.
The Terms of Use statement is stored in Global Resources for the site.  The easiest way to edit these resources is to login as an administrator and navigate to the “admin” panel.   Once there, select the “Languages” icon.

Click the “Manage” button near the “Language Management” text.  Click “Settings”.  Scroll down, if necessary and you will see a localized content section which will list the languages installed for the site.  In the “Static Resources” section to the right, find the column labeled “site” and click the “edit” icon

The “Language Editor” screen opens.   In the top left corner, you will see a treeview with “Local Resources” and “Global Resources”.   Verify that the “Select Mode” radio button is set to “Site”.  Open “Global Resources”, and select “Global Resources” again in the dropdown.

Scroll down the list until you find “ResourceName:MESSAGE_PORTAL_PRIVACY.text”.
Click the “edit” icon.

 

An editor window will open with the contents of your “Privacy” statement for the website.  Edit as you desire then save it. 
One further note, using the variable [Portal:PortalName] in your statement will insert the name of your portal into the displayed text. [Portal:Email] will insert the default email address of the portal.
Task complete !

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.

 



DotNetNuke Hosting - ASPHostPortal.com :: Security Levels & Types of DotNetNuke (DNN) Security Services

clock September 29, 2016 19:07 by author Armend

Security Levels & Types of DotNetNuke (DNN) Security Services

DotNetNuke (DNN) is a leader in open source content management system (CMS) for enterprises and it is the most widely used as a web CMS for Microsoft (Microsoft.NET). It helps businesses structure and manage content on their websites and their online clout which can be accessible by any device. As of now, it supports over 2500 commercial applications, 3200 customers and 910,000 websites. DNN adopts a 3 tier architectural design supporting the basic modules which are offered by them. It offers extensions using  3rd party modules & developers can add functionalities & features & integrate on to websites using the same. DNN skins have the capabilities to customize the look & the feel of the website through DNN skins. DNN works very hard to ensure that security issues are routed, reported & resolved through a proper channel through the DNN Security Centre. DNN provides requisite workaround or fixes in the applications for developers for any kind of security issues arising out of them. DNN task force reviews all the information given by members with immense confidentiality & a severity level is assigned against the issue reported in accordance with the impact it can have on DNN applications worldwide.

 

Security Levels in DNN

The severity level is classified as critical, moderate & low.

  • Critical means the DNN application can exploited recklessly to get access into confidential DNN information, data & functionalities and could have a huge impact on the application as well. All critical issues have to be addressed ASAP by the DNN security centre.
  • Moderate means an issue could be compromised if one or the other prerequisites are met which can have a not so high impact on the DNN applications. There is a set of recommended actions to resolve such kind of moderate issues.
  • Low means the issue has very low level of impact on DNN applications & chances of it getting affected is miniscule.

Also, the Task Force at DNN Security Centre issues a regular security bulletin via DNN blogposts to the community members & developers where it provides details about the issues reported by global partners & the process they implemented in resolving these issues. It also says the versions which were impacted & the suggested fixes & workaround provided for the same.

DNN understands that customers have invested a great amount of time, money & energy during DNN implementations & DNN works hard towards insulating these investments. One such area is devising security policies & offering upgrades on a constant basis to partners & developers worldwide. It's important to note that it's very critical to protect customers' investments & the work that have done using DNN architectures & Evoq solutions. DNN constantly works in a direction where security upgrades are quick, easy & effortless which ensures that it doesn't meddle with your existing site structures, skins, templates, layouts or modules. It's the core function of offering world class DNN services to customers globally.

Types of DotNetNuke (DNN) Security Services

  • Module Security -  The very objective of this is to assist developers in ensuring that they write modules (during web designing) with security in mind. It highlights common issues & provides guidance on how to identify & tackle expectant security issues. It provides recommended practices & gives general guidelines on web security & explains how to add layers to defend architectures by a hacker community. A hacker may have all the technical skills but may not possess the know-how of breaking through multiple layers thus making the architecture very secure. Adding a feature to validate the user at multiple layers can also make the system more resilient to such attacks.
  • Hosting Security – The main purpose of this is to offer users/developers safe & secure installations. Its all about offering the best fit during deployments from a range of different available environments. Environments can be hardened to make systems more secure & better decisions can be taken from a host of available scenarios offered by DNN to developers from its already available database.

Developers will have to follows a set of guidelines to tighten deployments & installations to make site architectures more secure & safe. Finally, its the job of developers to see to it that their servers are clean, secure & safe for both IIS & SQL servers.

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.



DotNetNuke Hosting - ASPHostPortal.com :: Tips To editing your DNN website

clock September 22, 2016 19:20 by author Armend

Tips To editing your DNN website

The following tips will help you with five of the most common tasks you'll perform on your DNN website.

1)Decrease Your File Upload Time

Save time - upload more than one file at a time! First, compress all the files you want to upload into a .zip file.  Then go to File Manager and select Upload A File.  Choose the zip file on your computer, then select which folder you want to upload it to. Be sure to check "decompress zip file." Now press the Upload File button.  This will move the single compressed file to the target location on the server, and decompress it.  So you just uploaded all of the files in the compressed folder with one upload.  If you are really watching your file quota, you may want to go back into the file manager and remove the zip file.  One downside of this little trick, it leaves the compressed file on the server after it is done.

 

2) Changing Your Workflow: Publish Content Before It's Visible

The more recent versions of DNN support this feature.  To turn this on, go to any HTML module settings.  Under HTML Settings, you'll find Work Flow. The default is Direct Publish while the other option is Content Staging.  If you choose Content Staging, the content will need to be published before it is made live on the site.  If you leave it as Direct Publish, the changes will go live as soon as you press save.  From HTML Settings, you can also see which modules are using these settings.  If you choose module, the setting is active in the module you are working on only. If you choose page, the setting is active on all of the HTML modules on the single page you are working on. If you choose site, the setting is active on the entire site.

3) Make Your Content Appear and Disappear Based on a Date Range

DNN Software has a date range on pages and modules that enables you to schedule a module's visibility. You can use many different variations of these 2 settings:

  •     Start Date (not supplied), Expiration Date (not supplied): module or page will always be visible
  •     Start Date (supplied), Expiration Date (not supplied): module or page will not be visible until the start date; once it is, if will show until you delete the page or module
  •     Start Date (not supplied), Expiration Date (supplied): module or page will be visible immediately and will continue to be visible until the expiration date.
  •     Start Date (supplied), Expiration Date (supplied): module or page will be visible on the start date and automatically stop showing on the expiration date.

4) Accidental Deletions: You Can Recover Them!

Don’t worry.  If you unintentionally deleted something, go to Admin->Recycling Bin.  You'll see a tab for pages and a tab for modules.  Choose which one you need and click Restore Selected Pages or Restore Selected Modules. Do not click Empty Recycle Bin. If you do, you'll need to contact our support team for a more involved solution.

5)  Copying and Pasting Advice

If you've ever tried to copy and paste from a third party editor (like Word), you may have noticed that everything ends up looking funky. There's a reason for this.  Word uses several hidden characters for formatting that you never see while typing or copying. But you definitely see the end result when you press save! Because of this, DNN Software provides a tool for you to migrate your content from your editor to your website.  Check out the toolbar of your HTML/Text Editor, and you'll see a paste options button. Your choices are:

  •     Paste (same as Control + V): this will paste the contents of your clipboard to your web editor. 
  •     Paste from Word: this strips out any non-essential word tags and characters.  This will leave the fonts in place.
  •     Paste from Word, strip font: this is the same as Paste from Word, only now we strip the fonts as well.
  •     Paste Plain Text: this means no fonts, not formats, no fluff.  Just text.
  •     Paste As HTML: this pastes the content in your clipboard as HTML code.
  •     Paste HTML: this will paste HTML code directly to the text editor.

We recommend using either the Paste from word, strip font or Paste as plain text.  If you strip the font, the content will adopt the font that the rest of your site uses.  This means everything still looks uniform.  If you don’t mind going back in and reading some bolds, underlines, lists, or any of that, then Paste plain text is for you.  This will make sure that just words, numbers and punctuation get pasted.
I hope you find these DNN tips useful. Contact our support team any time for extra help!

 

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.



DotNetNuke Hosting - ASPHostPortal.com :: Tips Responsive Bootstrap skin for DNN

clock September 15, 2016 20:13 by author Armend

Bootstrap is a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation and other interface components, as well as optional JavaScript extensions.

Twitter's Bootstrap is an excellent set of carefully crafted user interface elements, layouts, and javascript tools, freely available to use in your next web design project. This video series aims to introduce you to Bootstrap; taking you all the way from downloading the resources, to building a complete Bootstrap-based website.

While in the process of developing our own Responsive Twitter Bootstrap Skin for DotNetNuke , we had to jump over a couple of hurdles. First we had to figure out how to implement a dropdown on hover menu. Secondly, we had to overcome the Bootstrap issue where once you are on a child page, you cannot navigate back to the parent page in the menu. Bootstrap is against both of these features, however we feel as though these features provide a user friendly interface, especially while using a tablet or smartphone. With that said, we wrote this article to save you the headache to incorporate these two features in your Responsive Twitter Bootstrap Skin for DotNetNuke .

 

The real beauty was that I realized, I had included both the data-toggle="dropdown" and the data-hover="dropdown". You must only use the data-hover="dropdown" to fix both issues! The correct code is below:

Now you will have dropdown on hover menu items AND will be able to navigate to the parent page from the child page.

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability



DotNetNuke Hosting - ASPHostPortal.com :: Tips To Create Portals in DotNetNuke

clock September 8, 2016 20:11 by author Armend

In this post I will explains you how to create portal in DotNetNuke. Lets check it out

Introduction

DotNetNuke's portal system is one of its most compelling features. DNN Portals can be either Parent or Child. The different is from the url.

 


Parent Portal (example):

  • http://www.asphostportal.com
  • http://dnn.asphostportal.com


Child Portal (example):

http://www.asphostportal.com
http://asphostportal.com/dnn (As we have utilized "/" after area name, its called child portal)

Sometimes we have to create custom modules where we have to programmatically create portals. In this article we will plot how to make a a child portal programmatically. The technique needs few parameters to be passed which will be obliged to make the child portal. All these parameters have some settled reason. The part of individual parameters are unmistakably clarified in this technique.

/// <summary>
/// Creates new child portal
/// </summary>
protected void CreateNewPortal(string strPortalName, string strPassword, string strConfirmPassword,
 string strFirstName, string strLastName, string strUserName,
 string strQuestion, string strAnswer, string strEmail)
{
 
try
{
PortalController.PortalTemplateInfo template = LoadPortalTemplateInfoForSelectedItem();
 
bool blnChild;
string strPortalAlias;
string strChildPath = string.Empty;
var closePopUpStr = string.Empty;
 
var objPortalController = new PortalController();
 
//Set Portal Name
strPortalName = strPortalName.ToLowerInvariant();
strPortalName  = strPortalName.Text.Replace("http://", "");
 
//Validate Portal Name
if (!Globals.IsHostTab(PortalSettings.ActiveTab.TabID))
{
blnChild = true;
strPortalAlias = strPortalName;
}
else
{
blnChild = true;
 
strPortalAlias = blnChild ? strPortalName.Substring(strPortalName.LastIndexOf("/") + 1) : strPortalName;
}
 
string message = String.Empty;
ModuleMessage.ModuleMessageType messageType = ModuleMessage.ModuleMessageType.RedError;
if (!PortalAliasController.ValidateAlias(strPortalAlias, blnChild))
{
message = Localization.GetString("InvalidName", LocalResourceFile);
}
 
//Validate Password
if (strPassword != strConfirmPassword)
{
if (!String.IsNullOrEmpty(message)) message += "<br/>";
message += Localization.GetString("InvalidPassword", LocalResourceFile);
}
string strServerPath = Globals.GetAbsoluteServerPath(Request);
 
//Set Portal Alias for Child Portals
if (String.IsNullOrEmpty(message))
{
if (blnChild)
{
strChildPath = strServerPath + strPortalAlias;
 
if (Directory.Exists(strChildPath))
{
message = Localization.GetString("ChildExists", LocalResourceFile);
}
else
{
if (!Globals.IsHostTab(PortalSettings.ActiveTab.TabID))
{
strPortalAlias = Globals.GetDomainName(Request, true) + "/" + strPortalAlias;
}
else
{
strPortalAlias = strPortalName;
}
}
}
}
 
//Get Home Directory
string homeDir = "";
 
//Validate Home Folder
if (!string.IsNullOrEmpty(homeDir))
{
if (string.IsNullOrEmpty(String.Format("{0}\\{1}\\", Globals.ApplicationMapPath, homeDir).Replace("/", "\\")))
{
message = Localization.GetString("InvalidHomeFolder", LocalResourceFile);
}
if (homeDir.Contains("admin") || homeDir.Contains("DesktopModules") || homeDir.ToLowerInvariant() == "portals/")
{
message = Localization.GetString("InvalidHomeFolder", LocalResourceFile);
}
}
 
//Validate Portal Alias
if (!string.IsNullOrEmpty(strPortalAlias))
{
PortalAliasInfo portalAlias = PortalAliasController.GetPortalAliasLookup(strPortalAlias.ToLower());
if (portalAlias != null)
{
message = Localization.GetString("DuplicatePortalAlias", LocalResourceFile);
}
}
 
//Create Portal
if (String.IsNullOrEmpty(message))
{
//Attempt to create the portal
var objAdminUser = new UserInfo();
int intPortalId;
try
{
                            // These parameters are required to assign admin to the portal
objAdminUser.FirstName = strFirstName;
objAdminUser.LastName = strLastName;
objAdminUser.Username = strUsername;
objAdminUser.DisplayName = strFirstName + " " + strLastName;
objAdminUser.Email = strEmail;
objAdminUser.IsSuperUser = false;
 
objAdminUser.Membership.Approved = true;
objAdminUser.Membership.Password = strPassword;
objAdminUser.Membership.PasswordQuestion = strQuestion;
objAdminUser.Membership.PasswordAnswer = strAnswer;
 
objAdminUser.Profile.FirstName = strFirstName;
objAdminUser.Profile.LastName = strLastName;
 
intPortalId = objPortalController.CreatePortal(tbTitle.Text,
objAdminUser,
tbDescription.Text,
"",
template,
homeDir,
strPortalAlias,
strServerPath,
strChildPath,
blnChild);
 
//Clears the cache
DotNetNuke.Common.Utilities.DataCache.ClearPortalCache(PortalId, false);
}
catch (Exception ex)
{
intPortalId = Null.NullInteger;
message = ex.Message;
}
                        // Sends email on portal creation
SendMailOnPortalCreation(intPortalID, strEmail, strPortalAlias, objAdminUser);
}
 
DotNetNuke.UI.Skins.Skin.AddModuleMessage(this, "", message, messageType);
 
}
catch (Exception exc) //Module failed to load
{
Exceptions.ProcessModuleLoadException(this, exc);
}
}

The motivation behind this technique to send email on effective creation of child portal. The sending of email obliges legitimate SMTP settings in the DNN site.

private void SendMailOnPortalCreation(int intPortalID, string strEmail, string strPortalAlias, UserInfo objAdminUser)
{
try
{
if (intPortalId != -1)
{
//Create a Portal Settings object for the new Portal
PortalInfo objPortal = objPortalController.GetPortal(intPortalId);
var newSettings = new PortalSettings { PortalAlias = new PortalAliasInfo { HTTPAlias = strPortalAlias }, PortalId = intPortalId, DefaultLanguage = objPortal.DefaultLanguage };
string webUrl = Globals.AddHTTP(strPortalAlias);
try
{
if (!Globals.IsHostTab(PortalSettings.ActiveTab.TabID))
{
message = Mail.SendMail(PortalSettings.Email,
strEmail,
PortalSettings.Email + ";" + Host.HostEmail,
Localization.GetSystemMessage(newSettings, "EMAIL_PORTAL_SIGNUP_SUBJECT", objAdminUser),
Localization.GetSystemMessage(newSettings, "EMAIL_PORTAL_SIGNUP_BODY", objAdminUser),
"",
"",
"",
"",
"",
"");
}
else
{
message = Mail.SendMail(Host.HostEmail,
strEmail,
Host.HostEmail,
Localization.GetSystemMessage(newSettings, "EMAIL_PORTAL_SIGNUP_SUBJECT", objAdminUser),
Localization.GetSystemMessage(newSettings, "EMAIL_PORTAL_SIGNUP_BODY", objAdminUser),
"",
"",
"",
"",
"",
"");
}
}
catch (Exception exc)
{
Exceptions.ProcessModuleLoadException(this, exc);
 
closePopUpStr = (PortalSettings.EnablePopUps) ? "onclick=\"return " + UrlUtils.ClosePopUp(true, webUrl, true) + "\"" : "";
message = string.Format(Localization.GetString("UnknownSendMail.Error", LocalResourceFile), webUrl, closePopUpStr);
}
var objEventLog = new EventLogController();
objEventLog.AddLog(objPortalController.GetPortal(intPortalId), PortalSettings, UserId, "", EventLogController.EventLogType.PORTAL_CREATED);
 
//Redirect to this new site
if (message == Null.NullString)
{
 
//webUrl = (PortalSettings.EnablePopUps) ? UrlUtils.ClosePopUp(true, webUrl, false) : webUrl;
Response.Redirect(webUrl, true);
}
else
{
closePopUpStr = (PortalSettings.EnablePopUps) ? "onclick=\"return " + UrlUtils.ClosePopUp(true, webUrl, true) + "\"" : "";
message = string.Format(Localization.GetString("SendMail.Error", LocalResourceFile), message, webUrl, closePopUpStr);
messageType = ModuleMessage.ModuleMessageType.YellowWarning;
}
}
}
catch (Exception exc) //Module failed to load
{
Exceptions.ProcessModuleLoadException(this, exc);
}
}

Conclusion:

By utilizing the above procedure simply make the child portals in DNN. Assuredly, this post describes the procedure clearly and and useful for you

 

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability



DotNetNuke - ASPHostPortal.com :: Install module extension in DotNetNuke

clock September 1, 2016 18:46 by author Armend

How to Install module extension in DotNetNuke ?

What is actually a module extension in DNN? A module extension can be considered as plugin program that you can install on your site. Just imagine you have a car and you want to add a new sound system to your car, this new sound system can be considered as a plugin module to enhance your car looks and feeling.
To install a module extension in DNN, you will need to use a host account known super user account. Once login on the site, you will have a menu called host. Under this menu, you will find a menu called Extensions. Please click this menu.

A page contains extension modules list will appear.

Click the browse button to select the installation file. The installation file in DNN must in .zip format.

Click the Next button and you will be able to see the details of the extension specification.

If there is a release note, you will be able to see the what updates or changes that have been made.

If there is a license note, you will be able to review it as well. Tick the checkbox and click Next button to accept the license.

The installation will be fully completed if you do not see any warning or red text in the scrolling installation summary process

 

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.



DotNetNuke - ASPHostPortal.com :: Registered Script Control Error in DotNetNuke 8

clock Augustus 25, 2016 19:08 by author Armend

If you’ve made the transition from DotNetNuke 7 to DotNetNuke 8 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 8.  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.

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.



DotNetNuke - ASPHostPortal.com :: Tips To Setting up your DotNetNuke MDE

clock Augustus 18, 2016 20:09 by author Armend

In this post I will explains about how setting up your DotNetNuke module development environment. Setting up your development environment can vary based on what your end goal is. If you are doing module development for your own use, and within your own DNN environments, you can ignore a few of the settings below. If you are doing module development with the idea that you might turn around and give the modules away, or sell them, then you will likely want to follow the guidelines set forth below to support the widest array of DNN installation environments.
I recommend that each developer have their own local development environment, with a local IIS website running DotNetNuke, and a SQL Server 2008/2012 (not express, though you can use it) database for the website. Having an individual development environment makes group module development far easier than if you share environments/databases.

 

Choosing a DotNetNuke Version

Choosing a version of DotNetNuke is important when you start your development for couple of reasons. For modules that you are developing for yourself, you need to ask, what is the minimum version of DotNetNuke that you have in production. Are you running DNN 5.6.1? Are you running 6.2.6, 7.0.0, 7.0.6? Based on the answer you can determine what version of DNN you should setup as your development environment. You shouldn't be developing on a newer version of DNN than what you have running in production. As with everything there are ways around this, but I am not going to go into the details on that in this tutorial.

As a developer working to create modules and release those, you might have production sites that are running on the latest and greatest version of DNN, but what about your customers? Or your potential customers? You have to ask yourself, do you want to provide support for really old versions of DotNetNuke? From a development perspective you will probably say no, but from a business perspective, you might say yes, and here’s why. Not everyone upgrades DotNetNuke websites as they should, and often times you will find that some people never upgrade. While I don’t advise taking that approach to managing a DotNetNuke website, it is a fact of life that people don’t always upgrade and there are thousands of people, if not tens of thousands, that have sites that aren’t running on the latest version of DNN. You should take that into account when you are doing your module development, if you compile your module against an older version of DNN then your module should run on newer versions of as well, for example. If you compile your module against DotNetNuke 6.2.6 it will likely run on every version of DNN released since then. Though there are extended cases where this won’t always work, DNN strives to maintain backwards compatibility, this isn't always possible.

You might also want to use features that are only available starting with a specific version of DotNetNuke, such as the workflow functionality found starting in DNN 5.1, in that case you may choose not to support older versions of the platform out of necessity. This will minimize the market in which you can sell your modules, but also can make for less support and an easier development cycle due to the features that DNN provides.

Choosing a Package

Now here’s one that may baffle you a bit. I’m going to recommend that you use the INSTALL package for whatever version of DotNetNuke that you download. What? The INSTALL package? What about the SOURCE package? Well you can use the source, but you don’t need it. The module development that I’m setting you up for doesn't require the DNN source, and using the INSTALL package makes your development environment cleaner. We aren't going to be opening the DotNetNuke project when we do our module development, so why have the files sitting around for nothing? Also, if you've ever tried to use the SOURCE package for anything, you'll know it isn't easy.
The steps for setting up your development environment will apply to both the Community and Professional editions of DotNetNuke.

Installation Configuration

Once you have the version selection out of the way you can go through the installation process. While I’m not going to walk you through the minutest of details of each step of installing DotNetNuke in this post, I will at least try to point you in the right direction for each step.

Download the INSTALL package of the version of DotNetNuke you want to use in your development environment.

Extract the files in the INSTALL package to a location of your choosing, this location is where you will point IIS (the web server) when we can configure the website. In my environment I typically use c:\websites\dnnxxx.me\ (One item of note: you may need to right click on the ZIP file and choose Properties before extracting, on the properties window if you have an UNBLOCK option, click that. Some versions of Windows have started blocking files within the DotNetNuke ZIP files, which will cause you problems later during the actual install.)

Setup IIS

IIS is the web server that comes with Windows computers. DNN 7 requires IIS 7 or later (7,7.5,8.0), so you will need at least Windows Vista, Windows 7, Windows 8, or Windows Server 2008 R2, Windows Server 2012.

In IIS you should create a new website (Note: If you use an existing website in IIS be sure to add the HOST binding for DNNxxx.ME), and point to the folder where you extracted the INSTALL package.

Note: With DotNetNuke 7.0+, .NET Framework 4.0 is required, so be sure that your application pool is configured to run under 4.0, and not 2.0.

Set File Permissions

Setting up the file permissions for your DNN install is often the step that causes the most trouble. You should right click on the FOLDER in which you extracted DNN (c:\websites\dnnxxx.me\) and choose properties. Choose the Security tab. You need to add permissions for the account in which your website's application pool is running under. You will want to setup the permissions to give the account Full or Modify permissions for the DNNxxx.ME folder. Which account you will use will vary based on your version of IIS, here’s a simple list of some of the default accounts based on the version of IIS.

IIS Version Operating System Account

  • IIS 7 Windows Vista, Windows Server 2008 localmachine\Network Service
  • IIS 7.5 Windows 2008 R2, Windows 7 IIS AppPool\APPPOOLNAME
  • IIS 8 Windows 2012, Windows 8 IIS AppPool\APPPOOLNAME

Note: If you are using IIS7.5/8.0 you’ll notice in the above table that we have APPPOOLNAME in the identity, this is because when you setup a new website in IIS a new application pool is created. In place of you should type in the name of the application pool that was created. You can also bypass this and configure your application pool to use the Network Service account instead of a dynamic account if you would like.

Database Configuration

In SQL Server you should go through and create a new database. I always create a database with the same name as the website, so in this case DNNxxx.ME. Once you have created the database, create a user that can access that database. I always use SQL authentication, turn off the enforce password requirements, and give the user DB Owner and Public access to the DNNxxx.ME database. Remember the username and password you create here as you will need them when you walk through the Installation screen for DotNetNuke.

DotNetNuke Installation Screen

Populate the installation screen with the standard DNN information, Host username, password, etc. For the Database option, choose Custom and configure your database connection, providing the Server IP/Name, the Database name (dnnxxx.me). For the database authentication you'll want to choose the option that allows you to enter the username/password for the database user that you created previously.

Now there are two additional options you can configure, normally I would tell you not to modify these, but from a development environment perspective I do recommend that you change the objectQualifier setting. It should be blank by default, you should type in “dnn” (without quotes), this will prepend “dnn_” to all of the objects that get created by DNN such as Tables and Stored Procedures. This is not something I recommend from a production stand point, but if you are developing modules for sale, then supporting objectQualifier in your development is recommended. It will save you time down the road if you have a customer who has an objectQualifier defined on their production databases.

Best Recommended DotNetNuke Hosting

ASPHostPortal.com is the leading provider of Windows hosting and affordable DotNetNuke Hosting. DotNetNuke Hosting from ASPHostPortal.com provides a safe, reliable and performance-driven foundation for your DotNetNuke website. DotNetNuke is the perfect Content Management System for managing and developing your website with one of ASPHostPortal’s Hosting plans. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability.



DotNetNuke - ASPHostPortal.com :: Enable Google Analytics on a DotNetNuke Website

clock Augustus 11, 2016 20:15 by author Armend

In this post we will show you how to enable google Analytics on a DNN website. Google Analytics is one of those must-have tools when running a website.  The tasks of tracking traffic sources, browser versions, search terms, etc. are all made easy.  The developers of DotNetNuke have also made using Google Analytics on a DotNetNuke website simple.

 

Installing Google Analytics in DotNetNuke is a fairly common request from many individuals and I know it can be a quite troubling question for most. The primary questions are how and where can I put the javascript code provided by Google. Well you have a few options. First you could put the code directly in the skin for the site, the advantages to that would be that you will automatically have the code on all pages, however, the disadvantage is that you cannot use that skin as is on another portal due to the site specific Google information. I personally go the route of adding a text/html module to my site and set it to show on every page and insert the script in a very specific location which I will discuss below. There are a few drawbacks to this method. First you will not get any statistics information on traffic to "edit pages" where other modules are not displayed and you also will not receive information regarding administration modules. However, in most circumstances this shouldn't be an issue.

The best way to include this information is to include the information in the Module header of the text/html module. This is to prevent the accidental removal of the script code if you happen to click inside the module as an admin to enter in-line edit mode. Below I will walk you through the steps needed to implement Google Analytics using this method. (NOTE: you can extend this for other javascript integrations if needed).

Step By Step

  • Add a new Text/HTML module to a page of your site, you can position it anywhere, but I recommend the bottom of the page as administrative users will still see the module when they are logged in
  • Edit the text of the module to contain no text
  • Enter the module settings from the SolPart Action Menu
  • Expand the "Advanced Settings" section
  • Check the box next to "Display Module On All Pages?"
  • Insert your Javascript code in the "Header" box. This will ensure that the data is always retained
  • Now under "Page Settings" -> "Basic Settings" un-check the following boxes
    • Display Container
    • Allow Print
    • Allow Syndicate
  • Ensure that the "Cache Time" is set to 0 (Caching appeared to cause issues with this implementation in my testing)
  • Click "Update" to save your changes

This should complete the setup. You may now test to ensure everything is functioning correctly. You can log out as an administrator and view your site and no extra content should be displayed however if you look at the generated source you should see your javacript listed. Google Analytics should update within about 15 minutes to show that they are receiving your data.

Best DotNetNuke Hosting Recommendation

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

 



DotNetNuke - ASPHostPortal.com :: How To Customizing Page Titles and Meta Data in DNN

clock Augustus 4, 2016 20:23 by author Armend

How To  Customizing Page Titles and Meta Data in DNN

There are several key fields that search engines use in their ranking algorithms: page title (that’s the text you see in the title bar of the browser), meta description (that’s text describing your page to search engines, which your visitors don’t normally see) and ‘H’ tags, which are your H1/H2/H3 tags denoting which are the headers in your content.

How you do this in DNN:

The page title and description are stored in the Page Settings. Simply open up the page settings for the current page, and you can edit these directly. Here’s the steps:

  • Login as an Administrator, then go to the ‘Edit Page’ drop down on the top right hand side of the screen.
  • Choose ‘Page Settings’ from that menu, and it will load up the settings for the page you’re currently browsing.
  • To modify the page title, edit the value in the ‘Page Title’ field. In my example below, I’ve chosen some words that we can assume match the keywords/phrases that our fictitious bike company uses. Try and keep the length below about 70 characters so that, when it gets displayed in a Search Engine Results Page (SERP), you can see the whole title.
  • To change the Page Description, type into the ‘Description’ box. Remember that your visitors won’t see this on your site. The key to a good description is again hitting your keywords, but doing so in a way that actually reads well. If your page gets included in a SERP, it’s likely that the search engine will use the Page Description as the two or three line description for your page. Try and keep it to under 150 characters so that it stands a good chance of displaying nicely in a SERP listing, and the ratio of your keywords to the rest of the text is not too diluted.
  • When you’re finished, click ‘Update Page’ – the settings screen will close and you’re finished. (You’ll note on my example I didn’t bother with the Meta Tags at all)

Overview: H Tags

DNN doesn’t enforce the use of any particular H tag, so you’re free to edit one into your content however you like. It’s also possible to define a custom skin for your DNN site that shows a H1 for a specific page value (such as the module title for a piece of content).

I’d recommend leaving any ‘H’ tags out of your skin and just making sure that you define a H1 tag for each separate piece of content that you write (like a blog post title, for example). But others may disagree with me and just be happy to define a H1 tag using the page name of each page. I prefer to customize every bit of content for maximum impact – but this does take much, much longer.

To make something a ‘H1’ in DNN, here’s how you do it:
Use the ‘Edit this Page’ button in the ‘Edit Page’ dropdown to enter edit mode for the current page.

  1. Hover over the ‘Pencil’ edit icon and click on ‘Edit Content’
  2. Type in your header (or select an existing header with your mouse)
  3. Use the style drop down to select ‘Heading 1’

 

 

About ASPHostPortal.com:

ASPHostPortal.com is The Best, Cheap and Recommended ASP.NET & Linux Hosting. ASPHostPortal.com has ability to support the latest Microsoft, ASP.NET, and Linux technology, such as: such as: WebMatrix, Web Deploy, Visual Studio, Latest ASP.NET Version, Latest ASP.NET MVC Version, Silverlight and Visual Studio Light Switch, Latest MySql version, Latest PHPMyAdmin, Support PHP, etc. Their service includes shared hosting, reseller hosting, and Sharepoint hosting, with speciality in ASP.NET, SQL Server, and Linux solutions. Protection, trustworthiness, and performance are at the core of hosting operations to make certain every website and software hosted is so secured and performs at the best possible level.



About ASPHostPortal.com

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)

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

Tag cloud

Sign in