Monday, March 28, 2011

Hiding a DotNetNuke site or Page from Search Engines

You can hide a page from Search Engines by adding a ROBOTS meta tag to a DotNetNuke page, the meta tag you use will depend on your circumstances, click here to see the possible options for this tag. To add a meta tag for a DotNetNuke page select:

Page Settings > Advanced Settings >Page Header Tags

Adding a Custom Meta Tag to a DotNetNuke Page

Here is a quick tip, you can add a custom meta tag to a page in DotNetNuke by selecting:

Page Settings > Advanced Settings >Page Header Tags

Friday, February 11, 2011

DotNetNuke - Add a splash page or change the home page

Need to develop a new home page for your DotNetNuke website? Want to keep the old one in place until the new one is completed and ready to be displayed?

Or want to create a temporary splash page for a promotion on your site?

First create the new page on your DotNetNuke site. You can uncheck "display in menu" or uncheck "All users" from the "View" permission if you want to keep the page private for now. Once your page is ready to launch, under Admin > Site Settings > Advanced Settings select your new page in the drop down list for either the home page or the splash page (depending on which you would like to use). Keep in mind that if you add a splash page, the existing home page will remain the same and be displayed after the splash page. Also, don't forget to change the page permissions so that users can now view the page!

Thursday, January 27, 2011

Preventing Login and Content Changes

Need to temporarily block users from logging into to a DotNetNuke website? Prevent content from changing on a site? All of this can be done through the web.config file. Simply create a temporary page that will notify the users why they are not able to login, then create a redirect that from ~/login.aspx to your page by placing this tag within <system.web>:

<urlMappings enabled="true">
<add url="~/Login.aspx" mappedUrl="~/YourNotificationPage.htm"/>

To log out all users that are currently logged in, comment out your current forms authentication tag and add this:

<forms name=".DOTNETNUKE" protection="All" timeout="1" cookieless="UseUri"/>

You can find this tag in the web.config by searching for "<forms".

This trick is supported in all versions and editions of DotNetNuke at the time of writing (current version at the time of writing is 5.6)

Tuesday, December 14, 2010

DotNetNuke 5 and AJAX for .NET 3.5

Having problems with AJAX not working with your DNN Modules? Receiving an "Object reference not set to an instance of an object" error when you try to register the toolkit? There have been a few issues with trying to run the latest version of the AJAX toolkit with DotNetNuke 5, try running build 3.0.30930.28736 instead of the latest build. It doesn't require you to register the toolkit and, it is available for download here

Just place the DLL in your DNN bin folder, add register the assembly at the top of which ever control (in the module) needs AJAX and you are ready to go.

<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="AjaxToolkit" %>

Wednesday, November 17, 2010

DotNetNuke 5.6.0 Released

DotNetNuke 5.6.0 was released today, its most notable features include:

  • Improved Search: 5.6.0 includes an enhanced indexing capability which allows the standard core search feature to index page names, tag attributes and other metadata for improved search results 
  • Performance Enhancements: Optimizations to the database architecture and handling of web analytics tracking codes which will result in faster performance for all Editions of the product 
  • Configuration Manager:  A new configuration manager provides DotNetNuke administrators with greater access and control over their website configuration files without requiring the user to have direct file access. 

They have also introduced a perpetual license and enhancements to analytics, and content approval workflows. Find out more by reviewing the changelog.

Wednesday, November 3, 2010

Determining a DotNetNuke Websites Version without a Host Login

Ever need to check the version of a DNN site but do not have access to a host account? You can find this information out by checking the version of the DotNetNuke.dll file in the bin folder, or by running: