Will Strohl's Blog

I received this error while installing a customized version of the DNN install package. Here is what happened...

Sometimes, you are experiencing an error on your DotNetNuke web site, but the error will not even let the page load, or the error load. Well, here is a way to find the offending error.

I see a question in the DotNetNuke® (DNN) forums a lot. It is often phrased something like "I deleted my login page. How can I login now?" Here is how you can get to your login page even when the Account Login module is not on the page, or the login page you specified in Site Settings is not accessible.

As of version 4.06.02, DotNetNuke (DNN) has the built-in capability of providing a Secure Socket Layer (SSL) connection for any page on the web site. Some of you may notice such a page when the little lock appears on your web browser, and the prefix for the URL is "HTTPS" instead of "HTTP". Doing this for your DNN web site is pretty simple.

I have been using the minimum DotNetNuke® version feature in my modules for some time now. It is a great feature in your DNN manifest file that prevents your modules from being installed on unsupported versions. However, when I upgraded from v4.05.03, it didn't work anymore.

Believe it or not, there are quite a few people out there running on versions of DotNetNuke, and haven't upgraded in quite a long time.  This could happen for any number of reasons.  But it's important to know that upgrading is not always as easy as just dowloading and upgrading to the most recent version.  Due to feature inclusion/exclusion, database schema changes, and more, there may be stops you have to make in the upgrade process.

The DotNetNuke (DNN) CMS has a great Blog Module that allows you to have your very own blog on your web site. That's no secret. However, some people do not blog chronologically and/or update their blogs - in turn changing the publish date. Well, the current version doesn't allow you to change that date manually. Here is how you can....

I haven't tried it yet, but I found a tool that is supposed to make the module creation process easier. This is thanks to a Blog by Jon Henning.

I recently had to update one of my DotNetNuke (DNN) sites from version 4.05.03 to 4.06.02. I chose to do this to take advantage of the new SSL support. However, upgrading for me was not as straight forward as it normally is.

For those of you that are familiar with DotNetNuke (DNN), you know that although it is not a "slow" application, it has its moments. Also, ANY application can benefit from performance enhancements. I just sent a few to the DotNetNuke team.