DotNetNuke Administration
This post will be the first of what will be many posts with regards to application performance. After giving a number of presentations over the last 1-2 years, including one this evening in the Minneapolis/St. Paul area I've decided that some of these tips/tricks that I have with regards to improving application performance should really get put out here so people can find them and make the improvements to their applications. Going forward all of these posts will be categorized with at least the "Performance" category and then others that identify what systems are benefited by the changes. The subject of this post is Static Content Caching.
Read more...
Posted by Mitchel on Thursday, January 19, 2012
With all of the recent changes that have come to the DotNetNuke product in the past few years I have been seeing more and more situations where users have older installations that want to get to DNN 6.x to take advantage of the new features that are available with the latest version. I can't say as I blame them the newest features are great and a true benefit to all that use them, however, the road to getting there isn't always as peachy as it might seem, as you often find people with upgrades that fail horribly. This has been a common trend and some of the things that DotNetNuke Corporation has done really makes this process less error prone, but a bit portion of the "getting it right" upgrade process really falls in the hands of the site administrators that are going to be doing the upgrades. That is the focus on this blog post, how can we as site administrators identify potential risks and then mitigate/resolve the issues on our own?
Read more...
Posted by Mitchel on Friday, November 18, 2011
As I'm sure that you have seen in the last day or so DotNetNuke 6.1.0 was released. Overall, this release is a major improvement for DotNetNuke with enhancements to performance, support for mobile devices and other general upgrades. However, I've already been alerted to a major, slightly hidden change that I wanted to be sure to put out here as a warning.
Read more...
Posted by Mitchel on Wednesday, November 02, 2011
A while back I released a tool called Secure My Install that was designed to help people take existing DotNetNuke sites and change the way that they store passwords to use a more secure process. Many people have used that module successfully to convert their sites, however, I never took the time to share the few small steps that are needed to simply "secure" your site as soon as you set it up so that you can avoid all of the hassle in the beginning. In this post I'll walk through the simple process of changing your configuration to go from Encrypted Passwords to Hashed passwords and a bit of detail as to "why" you want to make the change.
Read more...
Posted by Mitchel on Friday, October 07, 2011
One of the aditions to DotNetNuke 5.x (not sure when/where) was the ability for DotNetNuke to provide a Canonical url in the meta information for your page. When this all works well, things are going perfectly. You can configure the site to use the Canonical url via the "Admin Settings" page and normally all works well, but I had a very "interesting" issue with a site recently and I thought I'd share incase anyone else had a similar issue.
Read more...
Posted by Mitchel on Wednesday, September 07, 2011
Now that DotNetNuke 6.x has been out for a while and with the recent release of DotNetNuke 6.0.1 while I was on vacation I thought I'd take the time to write a must requested blog post regarding my thoughts on the DotNetNuke 6.x platform and performance. Keep in mind, these points are my own personal opinion and should be considered that only, so without further delay.
Read more...
Posted by Mitchel on Sunday, September 04, 2011
In my earlier blog post I mentioned that one of my favorite features of the new DotNetNuke 6.0 release is the ability to download and automatically install purchased extensions from SnowCovered within the installation. In this posting I'll walk through the functionality as well as give my disclaimer and recommendation in regards to using this process.
Read more...
Posted by Mitchel on Thursday, July 21, 2011
This article is being cross-posted from my business blog.
If you have been paying attention to the news in recent months you have most likely heard of a few cases where user information, such as Usernames and Passwords, have been exposed from some high visibility websites. Some of the more current leaks were with Gawker and Mozilla. For those that are unfamiliar the situation is pretty simple. These sites store user login information, usernames and passwords, that allow users access to their systems. Their systems were then breached and malicious users were able to get access to the information. Why is this something that I am blogging about in relation to DotNetNuke? Well without a bit of configuration your site could be at risk, should a malicious user get access to your system. This article will discuss a bit around how/why there is a risk and how that relates to DotNetNuke, then it will progress into an overview of the default configuration of DotNetNuke and the recommended changes to the system.
Read more...
Posted by Mitchel on Friday, December 31, 2010
For just a little over a week there has been a lot of buzz in the .NET and DotNetNuke community around the POET security vulnerability that was identified within the Microsoft ASP.NET technology stack. For those of you unaware of the true details on this vulnerability I highly recommend you read the initial announcement from Scott Guthrie from Microsoft, as well as his Frequently Asked Questions post, and lastly his secondary followup posting, with a more detailed workaround. So why do I bring this up now? Well late last week DotNetNuke corporation released DotNetNuke 5.5.1 and in the materials that went out with that release they note that it includes a workaround fix for this vulnerability, I wanted to make sure that as always people have ALL information needed before they are doing upgrades.
Read more...
Posted by Mitchel on Monday, September 27, 2010
As more and more people start working with DotNetNuke, IIS7, and .NET 4.0 it is important to note a few important potential problem areas when it comes to running DotNetNuke on the 4.0 framework. Recently I took a DNN 5.4.4 installation and tried running it under .NET 4.0 and without modifications, it was a complete failure, in this blog posting I will show you what needs to change to allow DotNetNuke to work as expected.
Read more...
Posted by Mitchel on Tuesday, July 27, 2010
Previous Page
1 of 3
Next Page