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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Action Menu ProblemModule Action Menu Problem
Previous
 
Next
New Post
5/13/2007 4:36 PM
 

Hi,

I have a user control as part of a module that I navigate to using NavigateURL from another user control. However when the second control replaces the first one the module container does not have the same action menu. Things like Settings, Delete, Print, etc. are gone. All that I see are Help and Online Help. I thought IActionable might have something to do with the problem. However, that doesn’t appear to be the case. I can actually add custom actions. It’s the “standard” stuff that is gone. Are not the above mentioned action menu items like Delete the default set that is inherited from PortalModuleBase? What could I be doing wrong? I guess I don’t understand why my first control has the default menu actions but the one I navigate to does not. Any suggestions or documentation references would be appreciated.

Thanks,
G. M.

 
New Post
5/14/2007 9:42 AM
 

I beleive it is standard DNN functionality for the Delete, Move, Settings, and other menu items to ONLY dispaly on the default view control of a module.  I tested this with a module on my site and it functions in the same manner.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
5/14/2007 11:02 AM
 

Thanks for the quick reply Mitchel. Is that because the Delete, Move, etc. apply to the module as a whole and not just to individual controls? If you did want these items displayed, could you add them as custom actions or is there a better way to make DNN add the default menu behavior to a control?

Thanks,

G. M.

 
New Post
5/14/2007 11:38 AM
 

These items are only applicable to the main view as Mitchel described.  When you are on an edit screen, many of these menu items no longer make sense because you are in an "admin" mode that uses an alternate skin.  So actions like moving or printing a module in this context would not make sense. For example, if a user sees an admin skin with a single content column, then showing a menu that allowed the user to move a module to the left or right panes would be confusing since those panes would not exist on the page the user was viewing.

It sounds like what you want is to have multiple "view" pages for your module.  This allows each view control to exist in the main skin rather than the admin skin, and therefore all of the standard menu items will be shown.  It will be up to you to handle rendering the appropriate menu items for your module based on the current view page being displayed. This overall approach requires you to create a multipage module


Joe Brinkman
DNN Corp.
 
New Post
5/14/2007 11:50 AM
 

Thanks I have a better understanding now. I'll review the link on multipage modules.

G. M.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Action Menu ProblemModule Action Menu Problem


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