Installing the Module–Mushroom Image

DotNetNuke 5 refers to modules as extensions. There are two types of module extensions:

  1. Pre-installed Modules – modules included in DNN that have not been included in the build.
  2. Third Party Modules – modules built or bought and added to DNN to extend DNN’s core functionality.

We will look at third party installs only here.

Adding third Party Modules

  1. Log into your DNN instances using a Host account.

  2. From the HOST drop down menu select Module Definitions.

  3. On the Module Definitions page, select Install Module from the Module Definitions’ module options drop down.

  4. You will be taken to the Install Package wizard. Browse to the module package you would like to install. Of course, in this example I am installing Open Web Studio. After you have browsed, select Next.

  5. Information about the select module will display. Select Next.


  6. If available, release note information will display. Select Next.


  7. If License information exists for this module you will need to accept the terms of the license.


  8. When the install process is finished you will see a list of actions taken. ‘EndJob Installation successful .’ will display at the bottom when complete.


  9. There is a great video here that explains it:

New DotNetNuke Module–Mushroom Image

imageThis week we are releasing the first of our Integration module suite. The suite called Mushroom is designed to allow integration between WordPress, DotNetNuke, Social Media, and iPhone App.

The first module we are publically releasing is called “Mushroom Image” and is an image rotator style module that allows feeds from WordPress to run images directly into your DotNetNuke website.

Like our other recent module releases, we have designed the backend for easy and fast configuration using JS as the basis of the User Interface.


With all our recent dnn modules, we have used a template CSS / HTML system to allow the end users interface to be customized.

Here are some examples of the UI:








While we are still working on the website to support the sale of the module, you can see some of the demo templates on display here:






There is more to come, so stay tuned.

Changing the Look and Feel

Main Menu
1. From the module Main Menu, select MODIFY LOOK AND FEEL

2. Use the Text HTML editor to Modify the Introduction text that appears at the top of the public side of the Feedback module. This is uses standard DNN Text HTML editing.

Form Item Layout Text/HTML

3. Here you will find the html code that lays out the form items in the public view. Using the HTML editor, select HTML view mode, and edit the HTML code directly to get the best results.

The most common change it to edit the width of the table that displays all the form items to the public.

To make the form wide and prevent items from spanning two lines. Modify the HTML code in the top line: " ". Change the 250 to something wider like 500

Remember though that your web page, width of the site and container will effect this.

Message Sent HTML

4. This text HTML box can be edited to display a message to the user of your form. When a usre submits a form, the text here will be displayed in the module space.

Form Item Height Width

5. Enter the width that the form Item in this box.


Gives this result

And a width of 100 gives this result. Note the small width of each item.

Changing the email address the form is sent to

From the module menu (see the above help selection for installing the module to a page).



3. Select EDIT (just after the arrows) to edit the email address and name of the form.

4. Change the form name and email address as desired. Click UPDATE when done.



Adding a Feedback Designer module to the page

Having installed the Module to your DNN site.

1. Login to your site with Host or Admin permissions.

2. Navigate to the page you wish to add a form to.

3. From the DNN module menu select FEEDBACK DESIGNER and the Pane Location.

4. Select ADD to add the module to the seelcted pane.

5. You will see a warning message advising that the module has yet to be configured. This message will only be seen one time.

6. From the Complete Feedback Designer menu on the module, select CONFIGURE MODULE.

7. You are now presented with the Module Menu. From her select the options you wish to edit by clicking the corresponding CLICK HERE.

A Common SMTP Error in DotNetNuke

We get help requests, and we really do love to help you! Really! but please make sure you have a DNN host SMTP server configured that works before you ask us for help!
This module requires the SMTP server settings to be configure in DNN. This is because it uses the DNN SMTP server settings to send email. To configure…

1) Login as host user
2) Under "Host" menu select "Host Settings"
3) Scroll down and expand "Advanced Settings"
4) Expand "SMTP Server Settings"
5) In the SMTP Server text box type in where is the actual domain name of your site (this same exact host name for smtp, pop3, imap4, and web mail)

You can use authentication for the SMTP server if required. The DNN site will require Relay permissions that are often set to require authentication.

An example of the error you see when you do not have this configured correctly is.

Error: Email Enquiry is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. —> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Mail.Mail.SendMail(String MailFrom, String MailTo, String Cc, String Bcc, MailPriority Priority, String Subject, MailFormat BodyFormat, Encoding BodyEncoding, String Body, String Attachment, String SMTPServer, String SMTPAuthentication, String SMTPUsername, String SMTPPassword, Boolean SMTPEnableSSL) at DotNetNuke.Services.Mail.Mail.SendMail(String MailFrom, String MailTo, String Cc, String Bcc, MailPriority Priority, String Subject, MailFormat BodyFormat, Encoding BodyEncoding, String Body, String Attachment, String SMTPServer, String SMTPAuthentication, String SMTPUsername, String SMTPPassword) at iwebs.Modules.CFD.CFD.doSend() — End of inner exception stack trace —

We have created a movie file here to assist:

Understanding SMTP in DotNetNuke

DNN SMTP Settings

DNN Websites have the ability to configure in the host settings an SMTP server. When a DNN email is generated from the DNN website, it will attempt to send mail through this SMTP server.

In order that your DNN website can successfully send the email, the SMTP server must allow the email message to be received. Typically this is done in one of four ways.

  1. The SMTP server is configured for Open Relay (This should NEVER be done unless you have an external firewall blocking all external SMTP connections. Otherwise your mail server will become a spam server within hours)
  2. SMTP Authentication – Typically SMTP servers are configured to allow users with a valid username and password to authenticate themselves. Once they have been authenticated, they can communicate email messages through the SMTP server. This is the same way most ISP’s work their mail servers. The idea is that only users who are customers of the ISP will allow email to be sent from their SMTP servers.
  3. Selective Open Relay. The administrator of the SMTP server can also allow Open Relay (same as 1 above) from selective IP addresses. Any communication from an IP address that is configured to allow open relay will be accepted by the SMTP server.
  4. Local Host – If your website has it’s own SMTP server configured, typically it will allow email message to be sent form it’s self.

To correctly configure your DNN SMTP settings, you need to understand what method of communication has been configured in the SMTP server you are trying to set DNN to access.

Here is the process you would configure from above.

  1. Enter the IP address or valid domain name for the SMTP server, nothing more to do if open relay is allowed. (Still not recommended)
  2. Enter the IP address or valid domain name for the SMTP server, and the valid user name and password as would be used to communicate with the SMTP server. This is where you get to use the user name and password setting in DNN.
  3. Ensure that the SMTP administrator has allowed the IP address your DNN website uses to have open relay status. Then just enter the IP address or domain name of the SMTP server in your DNN host settings.
  4. Configure your DNN host settings to have “localhost” in the DNN SMTP server settings are.

There can be some issues that get confusing with the different methods.

  1. Open relay mail servers will be attacked by spammers very quickly. They are always on the lookout for mail servers that they can abuse. It is never recommended to have your mail server on the internet and in open relay. Additionally your mail server will be blacklisted by other mail servers if found to be in open relay.
  2. SMTP Authentication  can still be restricted to certain IP addresses. Many ISP’s will allow you only to use their mail servers while you are a client of their AND connecting to their mail server from an IP address they own. So thing will work in your Email applications while you are connecting to the internet via their dialup or high speed connection, but as soon as you move away from a connection provided by them, you will not be allows to connect to their servers, let alone Authenticate.
  3. Even if your ISP has allowed relay from the address that your mail server is run form, there may be a firewall or block on the normal port that the SMTP servers are typically configured to use. Port 25. If a firewall exists between your web server and the mail server, it must be configured to allow traffic over port 25.
  4. You may have web server configured with an SMTP server on the same system. Yet have it be blocked over port 25 for outbound communications. Some ISP’s block port 25 to curb the flow of virus email messages. You need to be sure that your ISP that provides connection to the internet for your web and SMTP server is not blocking port 25.

How to get really confused.
Often mail servers will allow you to send email messages to email addresses on that SMTP server, even though they do not allow you to send mail out. So if you have a web application configured to send email to yourself, and the SMTP settings you use in the DNN host settings are for the SMTP server that runs the same email address you will have success.
Yet when you change the email address in the web application, you can no longer send email, and the web application appears to fail. This is still an SMTP configuration error on your website. You will need to find a method above to solve the issue.

Podcast Discussing This:

Installing The Module

Note: Your Download Package Needs to be unziped before you start the install process. The file that is installed to the DNN site as a module is named with a "xxx"

Motion Demo Here

1. Login to your DNN site as a system HOST

2. Under the host menu, select MODULE DEFINITIONS

3. From the Module Definitions menu, select INSTALL NEW MODULE

4. BROWSE and select the Feedback Designer xx.xx.xx PA.ZIP file for uplad. Then select SAVE FILE.  Note that in some cases you may need to extract this PA files from a password encripted package zip.

5. Check the list of processes that follows for RED warnings and errors.

6. Your module is ready to be access and used on any DNN page in your site or child portals.


Installing a Module in DotNetNuke 5

DotNetNuke Modules–Under the hood UI and jQuery

We have been working to improve the UI of our dnn modules in recent times. This has included extensive updates to the backend administrator management. We have struggled for a long time to find a solution that actually works well for us and well for our clients.

The problem has always been the fragmentation of web technologies and browsers. Browser brands, versions, libraries, server technologies, uptake of new technologies like Silverlight etc has all been issues for us.

It’s one thing for us to develop a great solution, only to find that others struggle to have it implemented correctly. Silverlight is a classic example of this. Versions of SL and operating systems like mac vs pc really make a difference.

What we came up with

JQuery was the solution. Now that DotNetNuke had the core library built into the CMS, we are able to use it and find that most people have little or no trouble with it. We even managed to upgrade or template management system to use the new JQuery based UI. This makes the loading of the template management pages very fast.

image  imageimage

DotNetNuke Module Update News

Today we have release a range of new module updates for DotNetNuke. These include improved support four many of the modules in a partial trust IIS server environment.

All of the module can be Downloaded Free from our DNN Module Download page here.

Description: Description: Description: Description: Description: Link Builder 55.01.13
Automatically create and mange backlinks into and out of your websites to help improve SEO effectiveness of your site.


Description: My Friend 45.05.33
Add a "Tell A Friend" jQuery popup module to your site to allow visitors to spread the word of your great website. Add a "Tell A Friend" link to every page of your site in minutes.


Description: Description: dnn subscription module

Subscriptions Module 45.02.02
Subscriptions and advanced PayPal auto recurring subscriptions module with tax zones.


Bulk Emailer Download 45.05.96
Bulk Email for DNN with reliable campaign management and advanced tracking features, link tracking, recurring campaign and opt-in module.



Description: Report 45.01.17
Display your Google Analytics data directly to your DotNetNuke website.