What you're seeing is normal DNN behavior. Whenever "ctl=controlkey" appears in the querystring to force the loading of a module control other than the module's default (no controlkey) view control, there will be a switch to the edit skin and an isolation of the target module on the page. There are several ways to get around this and still have multiple view controls. Here are several variations of my favorite approach:

Register one and only one view control which acts as a dispatcher to several "sub"-view controls. Display of the sub-view can be based on a querystring parameter (other than ctl=), a tabmodule setting where multiple copy modules each having a different sub-view are placed on multiple pages, selection by the user from a navigation menu/buttons/drop-down, etc. within the dispatch control, etc.

The dispatcher control will display the selected sub-view by either showing/hiding panels (divs or an ASP.Net panel control) or by using LoadControl to dynamically load the appropriate sub-view. In the latter case you will find it easiest to have the sub-views inherit from PortalModuleBase and copying the ModuleCofiguration from the dispatcher control to the sub-view control after loading it.

With a trend toward client-side technologies, you might also consider using a form of templating (for example using KnockoutJS) to display user selectable views of data obtained via a web service all within the same module control.

 

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner