We have inherited a module from another developer that has multiple control files:

• Landing.ascx
• Profile.ascx
• Groups.ascx
• Events.ascx
• Settings.ascx
• etc...

The problem is that when the user browses to anything besides Landing.ascx, the page loads the Site Setting's Edit skin instead of the skin that's set in the Page Settings > Appearance.

We want all of these controls (except Settings of course) to use the skin that we define in Page Settings. All of these controls already use the 'view' setting in the module definition but it still goes to the edit skin.

Typically, when we build modules, we have one View.ascx that has a multiview. In this case, the module we inherited has 23 controls so we can't easily convert these controls into a multiview.

How do we force the module to use the page skin instead of the edit skin? Is it possible?