DotNetNuke Administration

Controlling DotNetNuke Static Logs

Posted by Mitchel on Sunday, January 20, 2013 Permalink

In the past I have blogged about various DotNetNuke performance and management issues, focusing on how to keep the Site Log, Event Log, and other database related functions in place. In this post, I'm going to take a look at a few other aspects, not all 100% DotNetNuke based, that should be closely monitored and addressed as well. For those of you that follow me on Twitter, my recent posting about clearing almost 40Gb of rogue data across servers is all part of what lead me to this posting.

Creating Custom DotNetNuke Module Categories

Posted by Mitchel on Monday, September 24, 2012 Permalink

As part of one of the recent overhauls of the DotNetNuke interface the control panel was updated to include a "Category" selection that allows modules to be grouped logically into categories. Out of the box a total of two categories are created "Admin" and "Common" with only the Text/HTML module included in the "Common" category. In this posting I'll take a deeper look into this functionality and how you can create your own categories, and how to move modules around between categories to make administration even easier!

Security Exceptions After Moving .NET 2.0 DNN Site?

Posted by Mitchel on Thursday, July 05, 2012 Permalink

Over the past few weeks it seems that I have been doing more DotNetNuke site shuffles than I have in a long time. From local -> production, from hosting provider a -> hosting provider b, and any combination therein. This process is practically second nature for me as I've done it so many times. However I had two sties that proved to be really troublesome so I though I'd share the root causes here in hopes that it might help someone!

Taking Control of the DotNetNuke WYSIWYG Editor

Posted by Mitchel on Tuesday, June 26, 2012 Permalink

DotNetNuke by default uses the Telerik RadEditor as the rich text editor. It is a truly amazing product and one of the better WYSIWYG editors. Just like any editor though it does have some mannerisms that are not so welcomed by users. A little known fact within DotNetNuke is that you have a number of configuration elements available to help not only make the editor easier to use by removing un-needed items, but you can drastically improve functionality for super-users if so inclined and prevent issues when staging content etc. In this post I'll dive into a few of the key configuration items that I make to all new sites.

Segregation of Duties: DNS, Domain Registration & Hosting

Posted by Mitchel on Wednesday, May 09, 2012 Permalink

This blog focuses a lot of development and management of web applications in a secure manner. In this posting I'm going to introduce a common principal of computer science, Separation of Concerns, and how a focus on separation is critical to the long term success and stability of your hosting environment.

Development and Test DotNetNuke Installations and Search Engines

Posted by Mitchel on Monday, May 07, 2012 Permalink

It is quite often that when working on a new version of a site that you will have a development, test, upgrade copy of the site that might be around for a while. It is also possible that if you are working for a third-party that you might stage client sites on your server for a period of time before go-live. At first glance this all seems common place and not something that you would be concerned about. However, that is not the case. Search engines have become overly aggressive in indexing sites, including those that have no direct back links but have been e-mailed to individuals or similar processes. In this post I'll discuss some important considerations when working with these "non-production" installations to help you ensure that search engines will NOT index the content and cause confusion.