|
|
|
DNN Blog
Looking for a specific blog?
|
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!
Tags:
|
|
One of the lesser known, but very powerful template options of the DotNetNuke DDR Menu, originally created by Mark Allan, is Razor. A while back, Joe Brinkman had a very interesting blog post, combining razor templating with taxonomy to come to very advanced menu layouts.
Sadly, DotNetNuke 7.0 introduced a breaking change in the way Razor was supported that specifically impacted the DDR Menu implementation of it. Although the issue had been on our radar for some time, it was not a very easy one to fix… Well.. the wait is over, in DotNetNuke 7.0.4, this is finally fixed.
Tags:
|
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
Tags:
|
Creating a good module makes it sometimes very hard to improve upon that. The (still current) old release of the DotNetNuke Announcements module was such a module. Created in an era long forgotten, as a DotNetNuke 4 module, it was quite good at the time when it was released. The announcement module is a fairly simple module that is a useful tool on most websites, while at the same time showcasing important DotNetNuke API features, and thus playing also a role in helping developers understand DotNetNuke module development.
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.
Tags:
|
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.
Tags:
|
|
|
One of the hidden gems in DotNetNuke 5.0 is the new caching support in the CBO (Custom Business Objects) class. During the refactoring of DotNetNuke for the Cambrian release, caching was one of the things that was closely looked at, since caching was starting to cause major issues in the DNN 4.x branch.
|
 Today marks a big change for me. As of today I will be working for DotNetNuke Corporation. There, I’ve said it!
The past couple of weeks have been very exciting for me. Last January I was approached by DotNetNuke Corporation with the question whether or not I was interested in becoming part of a new European office, to be established in Amsterdam. I would be wearing multiple hats: helping out with both support and sales, and also doing evangelism.
|
Where it comes to using SQL Server features, I am a very late adopter. Not by choice, for all the DotNetNuke modules I create, I'd like to maintain backwards compatibility as much as possible, especially since DotNetNuke also fully supports MS SQL Server 2000.
|
This blog is long overdue. In DotNetNuke 04.06.00 the language skinobject was beefed up to be much more versatile. Apart from just a dropdown menu, it can also display links to languages. Even though Lorraine blogged about the new appearance, there is much more to the skinobject than meets the eyes!
The skinobject supports 2 display modes: dropdown menu and template based repeater (you can even use both at the same time). Apart from that, there is a common header and a common footer available (both templatable).
All templates of the skinobject use the DNN core TokenReplace functionality as template engine. This means that you can control visible appearance of the language skin object to a great extent.
|
|
Tags:
|
|
|