New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Deleting broken modules

DotNetNuke generally does a good job of trying to protect the user from errors.  Occasionally, errors can occur that prevents a module from rendering, and may even interfere with container or page rendering as well.  When this occurs, the Action Menu which provides access to the delete action cannot be rendered and thus the module cannot easily be deleted from the page.

So how do we solve this problem?  The answer is a little counter-intuitive for the new DotNetNuke user.  The answer lies hidden in the Admin ControlPanel that appears at the top of the page when an admin is logged on.  The standard controlpanel in Figure 1 does not allow us to resolve this problem.

IconBar Control Panel
Figure 1:  IconBar Control Panel

This control panel was created for the DotNetNuke 3.0 release.  However the control panel from DotNetNuke 2, shown in Figure 2, had a method that allowed the admin to hide the rendering of content on the page.

Classic Control Panel
Figure 2:  Classic Control Panel

The DotNetNuke 2 control panel is still available in the DotNetNuke 3/4 installation, but it is buried in the Host Settings under the Advanced Settings section.  As shown in Figure 3, the control panel can be changed through a dropdown list in the Host/Advanced/Other Settings section.  By default this is set for the IconBar in DotNetNuke 3.  Change this setting to Classic and you will get the DotNetNuke 2 version of the control panel.

Host Settings
Figure 3:  Host Settings for the Control Panel

Now that we have the old control panel visible we can uncheck the Content checkbox shown in Figure 4.  Since the page containing our module may not render correctly make sure you change this setting on an admin page before navigating to the page with the problematic module.

Figure 4:  Use the Content checkbox to hide the page content.

Figure 5 and 6 show the before and after view of a module in standard mode and when the content is hidden.  Notice that although the module content is hidden, the container with the action menu is still visible and thus you can still delete the module.

Module Before
Figure 5:  Module with content showing

Module After
Figure 6:  Module with the content hidden

Sometimes you may not know which module on a page is causing the problem.  Just delete all of them while the content is hidden, then go back to the normal mode and restore the modules one at a time from the Recycle Bin.  When you find the module that is causing the problem just hide the content again and delete the single module.

The only downside to this approach is that it requires you to login before you may access the hostsettings.  If the problem is on the home page then logging in can be problematic.  I recommend that you keep a 'favorites' link to the HostSettings page.  This way you will always be able to login to the site, even when the homepage won't render correctly.


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out