Sep 22 2014

Optimizing The DotNetNuke Module Display Options

If you've worked with DotNetNuke for any length of time, I'm sure you're familiar with the very handy option of being able to display a module on every page of your website. This feature works great for sharing any type of content across every page of your website.

This feature is further enhanced by the fact that when you choose to display a module on every page, they are all linked by reference. This link means that if I update one module, every module on my site get's updated.

The current display settings for a module in DotNetNuke

However, when you decide to display the module on every page, you get just that... The module is displayed on EVERY PAGE! This includes Admin, Host, and any other unintended pages within your site. Typically, this is not the desired affect.

Furthermore, you may find yourself in a situation where you would like to copy one module to several pages on your site and a different module to several different pages on your site. (see diagram below) It doesn't make a lot of sense to display both modules on all pages as you would potentially create a ton of work for yourself in having to delete modules from unintended pages. It would also be cumbersome to add these modules via the Add Existing Module feature as it would require you to do so for each page.

A common scenario for content administrators

What I propose is an enhancement to the core DotNetNuke functionality. What if we replaced the Display Module On All Pages? check box with a Display Module On The Following Pages? Multi-select drop down list? (see screenshot below) This would allow us to copy a reference of the current module to precisely the pages we intended. Not only would this significantly increase the speed at which we could copy modules, but also reduce the number of mistakes we might make in forgetting to delete modules from unintended pages.

The proposed display settings for a module in DotNetNuke

If you like this idea and would like to see it rolled into a new version of DNN, then please head over to the DotNetNuke Voice and vote.

dnn,