Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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...Building ExtensionsBuilding ExtensionsModulesModulesHanging More than one Control from the same module on the DNN Menu?Hanging More than one Control from the same module on the DNN Menu?
Previous
 
Next
New Post
11/11/2010 6:59 AM
 
I have written a DNN module with over a dozen controls.  I know that when I add the module to a page or to a menu, it will automatically load the control with a blank name in view mode.  This is fine, but how to I add the other controls to a page or a menu.  I can't seem to figure out how to pint to the other controls and hang them apart from the main one.

Thanks,
Paul
 
New Post
11/11/2010 8:37 AM
 
Inorder to display other controls on the page you have to create the Module definition for each individual control included in the module, after that when u drag the Module on the page then all the controls for which you have created the Module definition will display on the Page.

Hope it helps!!

Amrish Sharma, MCP
 
New Post
11/11/2010 9:19 AM
 
Paul,

If you have severa control that are separate - meaning they can stand alone on a page by themselves,  you can create a completely separate module definitiion for each.  The blog module is a good example to review for this type.

However, if you have several controls that you want to be able to "call"  then when defining the control you need to set the control's "key".  The view module has no key and will be called by default whenever the page is loaded.  To access the other controls, you need to define a control key  for your control.  Your view module must either provide a link to the module using the defined key as way to locate the specific control and associated ascx file.  Alternatively your view module can define links to the other controls in the action menu.   Check out the HTML module for example.

If you are still unsure, could you provide a description of how the controls are related and how you would like then to work.

Hope this helps,
Paul.
 
New Post
11/11/2010 11:35 AM
 
Paul,
  You are talking along the lines of what I want to do, so let me further explain what I did, and see if you know of a way to accomplish what I want best.

  I have a module with a View (blank key), View2 (key is View2), View3 (View3), View4.... about 15 of them. And I have about 8 Edit controls too. All are defined in DNN under the module as a different control   I have successfully managed to be able to move around the screens (controls) by calling the others using the key.  I can even put links to have my users access the other control on my View page (the one without the key).  So, all that is working fine.  What I want is on the main DNN menu, I have a page with drop down subpages (like any other base DNN menu).  In the sub Menu I have am entry for the view of the module we have been talking about.  I want 5 others to appear in the same drop down.

MENU
    VIEW
    VIEW2
    VIEW3
    .
    .
    .

I think you get the idea.  I was wondering if I can (easily) do this through a normal DNN setup, or if I can rig it by going into the DNN database and forcing the items to appear, and force the keys to be called if clicked.   Either solution will be fine, but I would prefer easy first.

Does that help to explain my need?

Thanks,
Paul
 
New Post
11/12/2010 3:32 PM
 
Paul,

I believe I understand your requirement ... you want to be able to access the other view's from the menu.  So when you go to page x you would see not the default view, but an alternate view.  Interesting idea...  might be a nice enhancement to the core to define the default key for a module instance -- just not assume its going to be the blank key.  Not sure how or where you would define it...  

My suggestion is to create a dispatch module, that you can place on a page that would then redirect to the appropriate module using the required key.   You would need to create a page for each of the sub pages you want to add to the main menu.  Each page would then have this dispatch module that would then launch the appropriate view based on the key supplied.

With a little effort you could create a generic solution that could be reused for other projects.  Also, this method would ensure you don't have to mess with core tables to "force" the solution.   An advantage going forward as the core tables may change but the interface to them should be stable.

There may be alternate solutions ... anyone??

Hope this helps
Paul.    

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesHanging More than one Control from the same module on the DNN Menu?Hanging More than one Control from the same module on the DNN Menu?


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out