Hi, I'm struggling to figure out what I did to cause my Settings menu pick to disappear from my module's context action menu.

I am developing using VS 2008, SqlServer 2005 and DNN 5.0.0.

Presently I only see an edit (pencil) icon with no associated text and the Help menu pick.

Here is the code in my Viewxxx.ascx module:

''' -----------------------------------------------------------------------------
Partial Class ViewLadder
    Inherits Entities.Modules.PortalModuleBase
    Implements Entities.Modules.IActionable
....

    Public ReadOnly Property ModuleActions() As Entities.Modules.Actions.ModuleActionCollection Implements Entities.Modules.IActionable.ModuleActions
        Get
            Dim Actions As New Entities.Modules.Actions.ModuleActionCollection
            Actions.Add(GetNextActionID, Localization.GetString(Entities.Modules.Actions.ModuleActionType.AddContent, LocalResourceFile), Entities.Modules.Actions.ModuleActionType.AddContent, "", "", EditUrl(), False, Security.SecurityAccessLevel.Edit, True, False)
            Return Actions
        End Get
    End Property
....

I have a Settings.ascx user control that is registered with a Key of Settings and the Type set to Edit.

Any help is greatly appreciated.

Jon,

Thanks for the helpful reply.

My Settings usercontrol does inherit the ModuleSettingsBase and I have the control registered with the type "Edit" and the key "Settings". So I do believe that I have the Settings control configured properly. I to have another control that I use for module settings (I needed finer control over permissions for some settings). But I have set the key for the 'other' settings control to be "qlSettings" and it's type is "View".

So still a conundrum ;) Is there is any manifestation fo that "behind-the-scenes" crash that you mentioned?

Thanks!

Allen

That's a rough one.  I think the settings menu is only ever available during the default "View" mode so the behavior you're describing makes sense.

I see two ways out of it:

1) Dynamically load the appropriate user control into your base View control into a PlaceHolder control.  The caveat here is that you have to reload it on each postback.  See Michael Washington's write-up about this.

2) Have your settings be a standard Edit control but not a "Settings" key.  It won't show up as part of the "Settings" area anymore but you'd be able to load it into your ActionMenu at any time. 

I played around with trying to get the settings item to show up in something other than the view mode but I had to manually add it to get it to show (and then it doesn't have the "Update" item, it only loads up that portion of the settings so it is pretty useless).

Depending on how complicated my Settings are I actually pull it out of the Settings area and create my own standalone Settings control instead.