DNN Articles

This tutorial article outlines the process to migrate DotNetNuke (DNN) blog entries over to the Ventrian News Articles platform.

At one point or another everyone has a need to include an HTML form within a DNN website. This might be to link to a PayPal Buy it now button or one of many other options. Well as most of us know it is not possible to simply put an HTML form into a Text/HTML module and have the form submit. This is due to the ASP.NET form that is existing in the website that is used to handle all server-side controls. However, there is a fairly simple method to allow the form to post using some simple javascript.

At one point or another, it seems that almost everyone accidentally makes a change to a DNN installation that ends up breaking things. One of these situations that I never considered in the past was the accidental application of a skin with errors. I was contacted by someone today that accidentally applied a skin that caused a null reference exception, this caused the entire site to be unavailable. They could not access any pages and could not get back to the skin admin pages. Well, this leads me to find a method of resolving the issue via the database. In this entry, I will describe the steps needed to change the skin to a default skin via the database.

The question has appeared multiple times recently regarding methods to convert a standard ASP.NET application into a DotNetNuke module as well as options to “integrate” an existing ASP.NET website into DotNetNuke. This concept is very complicated for many individuals to follow and below I will discuss the options available to those looking to either integrate solutions or to create new DotNetNuke modules from existing applications.

So you have created the nice new skin that you have been looking to use with your DNN site, but you don't know how to set it up to upload to your site. Well the process is actually very simple if you follow the steps inside this entry.

This tutorial is a followup to my DNN backup tutorial. This document will discuss how you can restore your DNN site from your database .bak file and your DotNetNuke .zip file. This could be to either restore a damaged DNN installation or to move a DNN installation to a new server.

Another very common question that I see regarding DotNetNuke is when and how should I backup my DotNetNuke site. This topic is VERY important and requires a bit of planning, especially if you do not have direct access to your database server to perform your own backups. In the following sections I will first talk about what you must backup and why some of those items are very important. I will then discuss how to perform a DNN backup and SQL Server backup, both for SQL 2000 and 2005. Finally I will discuss options available for third party modules for performing backups for individuals that do not have direct access to their servers.

This follow-up post discusses the process to change a user account to a "host" account via SQL. This is a follow-up from my previous blog regarding creating a DNN Host account via SQL.

This posting provides a guide on how to create a new host account within DotNetNuke from your SQL Database. This is very helpful if you ever get locked out of your host account for any reason or for all of the new DotNetNuke users that have been having installation problems with the host and admin accounts. NOTE: This is provided for your use at your own risk!