Hello There: 

In the new DNN 7 I am seeing the same issue in regards to the ditor.css file not being  recognized when editing content of a module causes an overlay effect or popup window opposed to going to a brand new page.  This issue was reported back over a year ago when both I and I believe it was Canthry a DNN employee reported this as a bug to Gemini.  They branded it as minor and so I thought by the time DNN 7 came out it would have been rectified.   I just installed DNN 7 today and went to edit an html module and got the nice overlay effect and was hoping that I would now see my custom styles I had added to my editor.css file found in the same folder my skin was.  But instead it seems like it was back to showing only what is in the default.css folder unless of course I go back to extensions click on html module, click on edit controller and than uncheck supports popups. 

 This was the way Cantry said I would have to do it to get this to work properly for the time being but that was over a year ago when DNN 6 was still young.  Is their another way to get this feature to operate properly without having to disable the ability to use popups when editing the module.  If this is still found to be the only way in which you can successfully make use of the editor.css file in your skin folder so that under apply styles you see only your custom css styles and not all the default ones could you somehow let gemini know that this is no longer a minor bug but a very urgent one.

 I know it really isn't major in the scope of everything else that goes on but given that it was reported more than a year ago and doesn't seem to have been implemented in the latest major version of DNN which is DNN 7 I think we need to perhpas get this resolved for DNN 7.1 or DNN 7.2.  If there is a cleaner work around that doesn't impact the admins ability to edit content in overlays than I would love to know the answer so I could tell my admins how they can edit in the popup and yet still have access to the styles that were created in the custom editor.css file that belongs to the given skin.

 Thanks,

Bo

 

I

This still doesn't appear to be fixed in DNN 7.2.1. Seems like a pretty basic need for editors to be able to see what's their content is actually going to look like without having to hit save.

---

David O'Leary
Efficion Consulting

This can be solved by adding a popupskin.ascx file to your skin directory with the following code:
<%@ Control Language="C#" CodeBehind="~/DesktopModules/Skins/skin.cs" AutoEventWireup="false" Inherits="DotNetNuke.UI.Skins.Skin" %>