I know this is a really old thread, but as of DNN 6.1, this is still an issue, and it does not look very professional to the outside world to have the skin change when a user goes to edit a Form and List item. We have come up with a very simple work around that someone might find beneficial.

DNN is programmed to look for a skin in a cookie named _SkinSrc{portalID} where {portalID} is your actual portal ID. If is finds this cookie with a skin defined, it will use that skin every time a page is loaded overriding the skin you set at the page level.

By setting a skin in a cookie, DNN effectively does the same thing as setting a skin via a query string. As many of you already know, you can override a page's skin by adding a query string parameter to the end of a DNN URL such as this:
&SkinSrc=Portals\_default\Skins\MySkin


To set the cookie, add this to the Header of the Form and List module (Manage/Settings/Module Settings/Advanced Settings):



There are several placeholders in the code above where you need to substitute your own values as explained below:

{portalID} is the ID of your portal. Which you can find by going to Host,Site Management and looking at the Site ID for the given portal.

{skinPath} is the path to the Skin your want to reference

{pagePath} is the path to the page where your Form and List is.

Here is an example with real values filled in


This effectively does the same thing that would have been accomplished had you added the following query string parameter to the URL:
&SkinSrc=Portals\_default\Skins\MyFolder\MySkin

There is one caveat. The skin will be applied to the page represented by the "Path" defined in the cookie AND TO ALL child pages under that page. This includes the Form and List's "Edit" page, but, it also includes all admin pages for that page, such as the "Page Settings" page.

To minimize the effect, just don't create any child pages under any page where you use this method.

We came up with a slightly more elegant method by wrapping this functionality into a module which figures out all the parameters for the cookie so that we just add to the page whenever we add an Form and List module that will allow editing

Unfortunately, that would be too much to explain here.

Hope this helps someone.