Will Strohl's Blog

I blogged earlier today on a new piece of software that I ran across on the DotNetNuke® DNN web site. It is called the "Basic Skin Creator", and its intent is to make the job of creating skins easier.

If you're even a fraction as much of a fan of DotNetNuke (DNN) as I am, this news will certainly excite you... Michael Washington just blogged about software that he found that is tailored to aid folks in creating DotNetNuke skins!

Not that is matters at all, or even that anyone out there cares a whole lot, but I wanted to pat myself on the back for reaching 500 posts on the DNN Forums today at 10:22 AM (EST).

A recent blog post on the DotNetNuke web site prompted me to investigate in a bit more detail...

Although we would never want it to happen, we occasionally need to update the Module Settings for all instances of a specific module throughout a DotNetNuke (DNN) portal. There are times when a DNN web site grows to be so large that there are modules and pages all over the place, and the prospect of updating every single instance of a module is just not realistic. That all changes with a simple SQL Query!

Although for many of you, it may be very elementary as to how you would clear the cache in DotNetNuke (DNN), this is simply not the case for everyone out there. It is for this reason that I thought it would be a good idea to blog about it.

User Groups often have a bad stigma of not being productive and just being a "geek" meeting. Well, this doesn't have to be true. Such organizations can often be very productive and conducive to an entire industry, and your career.

I don't know about you, but I am an avid user of the Google Toolbar buttons, as well as the DotNetNuke web site. Well, if you use the DNN web site as much as I do, you either have the addresses in memory on your address bar, quick link or short cut buttons, bookmark links, etc. Well, I came up with another way...

A while ago, I tested the popularity and name recognition of DotNetNuke against some of the other CMS products out there. Being a fan and loyal user/developer of DotNetNuke projects (not the Core projects), I was quite disappointed.

I had an instance recently where the FCKeditor would not display in any browser. Instead, I was greeted with nothing in non-IE browsers, and in IE I was greeted with the unwanted "Internet Explorer cannot display this webpage" page.