After one makes a module for the guts of a page as described here, one may give the web user control a separate web user control to drive its settings. While logged in as "host" one may see the settings for any one page by picking "Settings" from that menu which expands from the arrow at the upper left of any page. To make a "Settings" just make a new .ascx and then add a new moduleControl at the appropriate package at the .dnn file. This time the controlKey should contain "Settings" and the controlType should be "Edit" however. In the .ascx you may place controls and these controls may be interpreted at the other module. In the app I am looking at now we have some inheritance magic going on beyond the norm of DotNetNuke so a code snippet wouldn't really make sense assuming the default DotNetNuke wire-up. (sorry)
No comments:
Post a Comment