DNN Articles

The DotNetNuke Text Editor is powerful, however, its default configuration is often unwieldy for common users, but with some simple configuration it can be made easier to use.

Often times we need to create multiple copies of a production application for testing or other purposes. When doing this, we need to take special considerations into how we can prevent Google and other search indexes from seeing these copies.

It is often said the cobblers kids have no shoes, well the same goes for IT Professionals. I finally upgraded this site, and ran into numerous issues that I thought I would share for the benefit of others.

Upgrades of any type come with some risk, how can you manage that risk when working with DotNetNuke to make upgrades as seamless as possible?

Canonical Portal Alias features were added to make life easier, however, with 5.6.2 that might not exactly be the experience at first.

DotNetNuke provides its own internal data access strategy for accessing SQL Server, this process works well for most standard situations. However, complex items such as the ability to call using Table-Valued Parameters can be less straightforward to implement.

Errors from Scheduled Tasks within DNN can be a nuisance and can even mask more critical errors, so digging into and resolving these items is important for long-term site health.

Working with custom solutions it is commonplace to need multiple extensions, it is possible with small modifications to package those extensions all at once.

Many extension developers rely on the internal DotNetNuke Text Editor to provide rich-text editing experiences to users, however, Visual Studio may not always make this process straightforward.