Last post Feb 01, 2006 05:10 PM by RLyda
Nov 22, 2005 04:57 AM|jm4151|LINK
Jan 31, 2006 09:30 AM|raldo|LINK
I have the same problem. My experience so far with DNN 3 is that you can only have one settings control per module. Does anybody know if this is the case?
My problem is that I have a few controls that do different things and at least two of them need their own settings control. Another issue I have found is the disappeance of the print icon on controls other than the main module control (the one without a
key). Does anybody know why this happens?
Jan 31, 2006 10:25 PM|imagemaker|LINK
In the process of writing classes inheriting from PortalModuleBase and ModuleSettingsBase to implement "global" settings at the ModuleDefinition (rather than Module or TabModule) level, I spent a good part of today tracing core code flow for displaying the
Module Settings page and particularly how a module's Settings.ascx control is loaded and and populated with (limited) module configuration information. This happens via a LoadControl in the Page_Init event handler of ModuleSettings.ascx.vb (class DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage).
The one and only settings control that can be loaded without making a core change is the one defined with the "settings" key.
Your module's Settings.ascx control itself could use LoadControl to load as many child setting controls that you might wish to design. These could easily be selected depening on user role, module settings, etc.
Feb 01, 2006 05:10 PM|RLyda|LINK