Removing Roadblocks to Upgrading By Reviving the Old Core Modules

Jun 25 2018
Removing Roadblocks to Upgrading By Reviving the Old Core Modules

In the recent months I have noticed a increase in the number of clients that want to upgrade Dnn, they are often faced with modules that break due to breaking changes in the platform. And the older the module, the more chances it has of being affected. Unfortunately, we cannot do much for third party modules, but I feel nobody should be blocked from upgrading because of a module that was formerly included with Dnn. After thinking about it, I decided to take initiative and made it my goal to make all the old “core” modules work on DNN v9.2. As you would imagine this is not a task that is achieved overnight, but I’ve made good progress. Several modules are already current and in doing so, I think it fired up a new wave of motivation within the Dnn Community Developers!

Fixing duplicate Display Names in DotNetNuke

Oct 19 2014

Since DotNetNuke 6, it is possible to require unique display names. This allows social modules to display a name for a user without exposing the login UserName or the real person first and last names. If you site uses social features, it is important that those display names be unique to prevent a user to post content in the name of another user.

By activating this feature, users are no longer able to register with a Display Name already in use. However, there are 2 oversights. First, the user or an admin can change the Display Name after registration to anything else (including a Display Name already in use). Secondly, you may already have duplicates before you activate this feature, and they don't get automatically changed. In this blog post, I provide you with both solutions the these problems.

Creating a webservice in DotNetNuke 7

Jun 11 2014

I have recently been assigned to built a DotNetNuke web service to allow a windows application (or any type of web client for that matter) the ability to manage DotNetNuke user accounts (create, change roles, delete, retrieve email address, etc.).

Since I had a hard time finding a correct code sample or documentation that actually applies to DotNetNuke 7 and accessing it without being previously logged in to DotNetNuke, it was difficult to built anything. I finally found out how to do it correctly so I tough I would put my efforts to some use and write a blog post explaining how to do it step by step.

World Backup Day

Mar 31 2012

March 31st is World Backup Day. Just as we must remember to change batteries in smoke detectors when we change time, we must all remember to have a backup and restore strategy on the 31st of March. The date is pretty easy to remember because it is the eve of April Fools day surprises. This does not mean that you should make a backup only once a year, but it is a good time to check that we have an effective solution.


Daniel Valadas 10354 9


2018 Jul 5 1
2018 Jun 15 1
2018 May 33 1
2014 Oct 670 3
2014 Jun 4819 1
2014 Feb 3335 1
2012 Mar 1477 1

Recent Posts

Removing Roadblocks to Upgrading By Reviving the Old Core Modules
2018-06-25 4:23 PM | Daniel Valadas
How to secure a whole Dnn site with an SSL certificate
2018-05-08 4:51 PM | Daniel Valadas
Take a list of emails and separate them with a semi-colon (;)
2014-10-24 5:14 AM | Daniel Valadas
Fix: DotNetNuke users can't reset their password
2014-10-24 3:21 AM | Daniel Valadas
Fixing duplicate Display Names in DotNetNuke
2014-10-19 11:17 PM | Daniel Valadas
Creating a webservice in DotNetNuke 7
2014-06-11 1:02 PM | Daniel Valadas
How to move a DotNetNuke Website to another server
2014-02-10 10:51 AM | Daniel Valadas
World Backup Day
2012-03-31 1:28 PM | Daniel Valadas