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!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Getting StartedGetting StartedDNN 6 Module Definitions not working correctlyDNN 6 Module Definitions not working correctly
Previous
 
Next
New Post
7/31/2011 6:27 PM
 
I created a module from the module template at http://christoctemplate.codeplex.com/

Inside my new module project added an additional view control inside it's own folder named Sample. I installed the new module and then navigated to the module definition so that I could define my additional view as a separate module. I created the new definition and then added the view control to that definition. Now when i try to add a new module to a page I do not see the module in the list. I see the main module but as far as the additional definition I do not see it.

What am I doing wrong?

And by the way, the Module Definition UI is totally broke in Chrome.
 
New Post
7/31/2011 10:21 PM
 
The "Module Definition" page is deprecated in 6, you do everything from the Extensions module (under Host) instead of the separate module (as it was in 5). That aside, it sounds to me like you are attempting to create two separate modules (not definitions) so that each one is a module that can be placed from the drop down list in the control panel. If this is your intent, you must create 2 separate modules (not module definitions). You can have both in the same folder, they just need to be considered separate 'modules'. 

Multiple definitions in a single module are used a couple different ways but this isn't one of them (blog is a good example, 1 module with multiple definitions. When you drop the module on a page, 3+ 'modules' are placed on the page at the same time (they are all the blog module, each is a different module definition though). 

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
7/31/2011 11:52 PM
 
Chris thanks for the help.. I'll admit I was a bit uncertain on what to expect when installing modules.

I looked at the Blog module as well as the NB Store module which gave me a good education on the matter. I ended up editing my .dnn manifest by hand to get the desired results. In a single module project using a single manifest I am now able to create two distinct modules during the installation. One of the modules is like the Blog set up where when you add it to a page it creates 2 modules.

The NB Store project has multiple packages defined in a single manifest so that showed how me to create multiple modules per install. So now I have the two modules available in the modules list to be placed on the page.

As far as module definitions I was using the interface in the host extensions area to create the definitions and it is very buggy and that is why I ended up doing the manifest by hand.

Thanks again.
 
New Post
2/9/2012 1:24 PM
 

If this is your intent, you must create 2 separate modules (not module definitions). You can have both in the same folder, they just need to be considered separate 'modules'.

How? How are they "considered separate 'modules'"? I've got a module with multiple components and they need to be displayed separately in the dropdown when adding modules, but everything resides in the same folder. I'm definitely missing something here. I've added the first module using "Create New Module" and selecting Control. If I try to install another module from the same folder, I get the duplicate key error. Do I have to create a manifest and use that rather than adding each of the controls?

 
New Post
2/12/2012 4:52 AM
 
  If you use "Host - Extensions - Create new module " to create different modules which in same folder, you must manually modify Packages and DesktopModules tables.

   For example, if you create first module based control and control folder name is "CrossArticle", then dnn will add  "CrossArticle" as package name in table "packages" and "CrossArticle" as module name in table "DesktopModules" , then when you try create another module definition based "CrossArticle" folder, you will get a duplicate key error.

    The solution is straightforward : change package name/module name in table to a different name after create a module definition, then you can continue to create another module definition which on same folder.

Over 20 + professional dnn modules for News Article, Store, Video Gallery, Photo Gallery, Ultra Flash Player,YouTube Video, Image Slide show, Skin Chameleon and much more from DnnModule.com
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Getting StartedGetting StartedDNN 6 Module Definitions not working correctlyDNN 6 Module Definitions not working correctly


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.