Securing the login of your DotNetNuke site is very important, but often neglected for the wrong reasons. It shouldn’t be because SSL adds a performance overhead to your site. It shouldn’t be because SSL certificates are expensive either. But most of all, it should not be because it is hard!
[Read the rest of this article...]
Sometimes it is very hard to troubleshoot SMTP issues that occur with your DotNetNuke application. Sure, you can view the SMTP log of your mail server, but that may be either misconfigured, or not even accessible at all (this is especially true in a shared hosting environment).
Luckily, there is a very simple way to enable logging for all network traffic DotNetNuke is generating, which includes SMTP traffic.
I feel pretty bad when I look at the last release date of the module though. May 15, 2009. More than 3 and a half years ago. The module might have been a good module back than, but it certainly is not anymore right now. What was regarded as using best practices back then, is currently not much more than using legacy code.
A long time ago I blogged about the caching enhancements in DotNetNuke 5, and a recent blog post by Mitchel Sellers about using DotNetNuke Caching in Custom Modules triggered me into revisiting my old post.
In his excellent post, Mitchel describes a way to abstract from some of the available methods in the DotNetNuke .Common.Utilities.Datacache class. This is indeed a great way to simplify using the DotNetNuke entity cache in your own modules.
I am Erik van Ballegoij. I work for DotNetNuke corporation as Technical Lead and Evangelist. On this blog I blog about DotNetNuke tips and tricks and whatever else comes to mind