DotNetNuke
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.
Read more...
Posted by Mitchel on Wednesday, May 09, 2012
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.
Read more...
Posted by Mitchel on Monday, May 07, 2012
Recently I have been getting a lot of questions regarding the DotNetNuke login and why when you go to login that "auto complete" is disabled on the username/password fields. The typical follow-up question to that is "how can I change that behavior". So after answering this question individually around 5-6 times I though it would be best to get this out here, at least my opinion on the issue.
Read more...
Posted by Mitchel on Friday, May 04, 2012
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
So like many developers I have been spending some time recently updating my client, commercial, and open-source modules to support the new DotNetNuke 6 Form Pattern from a design perspective, to make my modules better integrate into the system. Looking around when I was starting there is very little "true" documentation on this concept, and for me it was a bit cumbersome pulling everything together. I started with this Wiki Article and then ended up spending a lot of time digging/inspecting lots of other modules that had been upgraded. So in this post, I'm going to take a bit more of a 'code-centric" no-nonsense approach to what your form should really look like, I hope that this helps you.
Read more...
Posted by Mitchel on Monday, December 19, 2011
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 most of you know I was at the DotNetNuke World 2011 event in Orlando Florida this past week, and I thought I would give a quick recap of my experience with the event and share how much different I felt this event was in comparison to the previous DotNetNuke Connections events. To help try and give proper justice to the topic, I'm going to break my review out in a few different categories to help make it a bit more understandable, and without further delay, here we go!
Read more...
Posted by Mitchel on Sunday, November 13, 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
It seems that the past few months have just flown by and I haven't gotten as much time to blog here as I have wanted. I hope to start changing that here in the next few weeks as I have a large number of items that I'm looking to get out here, just trying to find the time to get it done. But with DotNetNuke world just a little over a week away I wanted to post a quick note here about the event.
Read more...
Posted by Mitchel on Monday, October 31, 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
Previous Page
1 of 24
Next Page