www.nazareneisrael.org. When we create a new page, or even copy a page, DNN generates 47 sets of headers, and 47 sets of modules in the Small Left Pane. Do you have any idea what could be causing this problem? And how could we solve it? Thanks for your wonderful service.

That's kind of scary!

When you create the new page, you presumably are using a template. There is a default template if you don't specify something else. Does that template have modules?

Also, any modules that have been specified to appear on all pages will be added.

Is something like this going on, or is something really out of control? Is there a site that I could look at?

Sometimes we use a template, but usually I just use the 'Add New Page' feature. We get 47 headers and modules either way. The website is www.nazareneisrael.org. A sample page with too many headers and modules is at: http://www.nazareneisrael.org/Subsc...dules.aspx Don't be surprised if it takes ten minutes to load Thanks.

When you "Add New page" there is a default template that is used.  You should also check that one.

Hey Guys,

I know this thread is kind of dated, however I'm running into a similar issue that is 'truly scary'.

Not sure if it's 47 instances, but there are a ton of modules added to any new page created. It is all of the modules that are set to display on every page, but there are probably 50 instances of each. And ALL have the setting to display on every page.

This occurs no matter what template is used, or if none is specified, or if a page is copied.
http://nationalpremium-dev.wsivirtu...fault.aspx

Specifically this started occurring during the creation of a child portal for a language variation. Not sure why or when exactly, but the production site is fine. The issue is we have this site just about ready to launch, but proving difficult to perform the final edits and new pages.

Upgraded to 5.6.1 this morning, but still no help.

Any ideas would be appreciated, and please let me know if you need any other info.

Thanks,
Ben

PS - Thanks for all the knowledge Joe. Who knows how many times you've saved my ass already.

Yikes!

I would look at the modules or tabmodules table (I'm not able to look at a database right now) to see if there are multiples of the same module marked to display on all pages. That is the only thing that would make sense.

I've come to believe that many of the features that allow you to do something to all pages are fairly dangerous, though quite useful. I try to minimize their use.

Thanks Joe. That was good enough for me. Not sure what we jacked up in the process but...

Discovered that the child portal (dutch language version) was fine when creating new pages. First attempted to create a new US portal, but kept running into timeout errors when importing the new template.

Final Solution:

Jotted down the moduleID of the 'good' modules that we were using throughout the rest of the site - that were set to display on all pages. Only a handful (header phones, call to actions, inline forms, testimonials)

Got a back up of the DB.

Went into SQL Server Management Studio and selected all modules with AllTabs set to true. Deleted them all but the previous mentioned reference numbers.

Looks good so far,

Thanks for the help.
Ben

SQL can be a very helpful, very powerful, and very dangerous tool. But, if you know how to use it, you can solve quite a number of problems. There are a couple of tutorials in our library on using SQL for page and module management. I found them to be very helpful when I was trying to master some of the DotNetNuke internals.

And ... ALWAYS make a backup of your database first!