Home » none » DotNetNuke – Missing Content in Modules

DotNetNuke – Missing Content in Modules

So, I ran into a problem a couple of days ago that took two days to figure out.  Since my search in Google turned up nothing, I’m posting it here just in case someone else does the same stupid thing.

A couple of days ago, a client of mine called and said he’d been working on his DotNetNuke site moving things around when suddenly he was unable to see his module content any more.  Since I’m his DNN guru, he asked me to look into it.

Now the really odd thing about this is that it was only impacting his admin account.  I have another id that has admin permissions.  It was not impacted.  His general user id (no admin privileges) worked fine.  The host account worked find.  What was it that could possibly be causing this?

The other peculiar trait was that the module containers showed up, but not the content within the modules.  So, you’d think it really has nothing to do with the roles.  Maybe some exception was being thrown?

So, I looked in the event log.  No errors.  Just application start and login events.

What COULD it possibly be?  Oh well, let’s just create a new account for him and get on with life.

About an hour after we did that, I get a message from this client.  “When I flip the admin screen into design mode, I don’t see any content, is that the way it is suppose to work?”


I should have known that.  I never use Design Mode, but I have flipped to it at least once to see what it does.

So, if you are having this problem and can’t figure out what it might be, check the upper left corner of the screen and make sure you aren’t in design mode.  Design mode will show you just the containers so that it is easier to move things around.  View Mode will show you what the screen will look like to a user who doesn’t have page edit rights, and Edit mode with allow you to see all of the content, the design panes, and let you make changes to the content.

Hope this helps someone.

Like this Article? Subscribe to get every article sent to your email.

Related Post

  • DotNetNuke Modules – Creating Base ModulesDotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it […]
  • DotNetNuke – FileUploadControl Danger!DotNetNuke – FileUploadControl Danger! A couple of days ago I was working with a client who was having trouble using the File Upload Control from within a DotNetNuke module.The problem we were seeing was that although all […]
  • DotNetNuke Panes Won’t collapse?DotNetNuke Panes Won’t collapse? Yesterday  I mentioned that I was trying to track down another issue with DotNetNuke when I discovered the FavIcon secret.The problem I was trying to track down was the issue with […]
  • DotNetNuke Modules – Module SettingsDotNetNuke Modules – Module Settings Since each instance of a module that we put on a page should be able to have it's own configuration information, it is necessary to have some place that will allow us to configure […]
  • DotNetNuke – SkinningDotNetNuke – Skinning Today I'm going to start a separate series on Skinning DotNetNuke. Don't worry, I'm still planning to continue the series on creating modules. Later on, I may start a series on something […]

About Dave Bush

Dave Bush is a Full Stack ASP.NET developer. His commitment to quality through test driven development, vast knowledge of C#, HTML, CSS and JavaScript as well as his ability to mentor younger programmers and his passion for Agile/Scrum as defined by the Agile Manifesto and the Scrum Alliance will certainly be an asset to your organization.

  • http://www.liz-online.pt Ricardo Simão

    Very helpful indeed. Unfortunately I just read this article after I removed view/edit permissions to each module this user may manage.
    Now the user sees portals content, time to reconfigure his view/edit permissions again… :)