The control panel is showing for anonymous users.  It is not expanded, and cannot be expanded, but it is showing a narrow strip with the edit and view buttons.  It will not allow the edit button to be selected.  I'm at wits end as to why it is showing.  The page is set to allow edits only for administrators - I did see that post in the forum and double checked.

I set the skin back to the default dnn skin, and the control panel does not show up, so it's definitely something in my skin.  I've used the red leaf skin as the basis of my skin.  I've altered it quite a bit and used some negative margins to move my logo over a div to do some overlapping.

Anyone have an idea as to what might cause the control panel to appear unexpectedly?


Karen

I think I have it narrowed down to
<%@ Control language="vb" CodeBehind="~/admin/Skins/skin.vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Skins.Skin" %>

Visual Studion shows a warning that the admin/Skins/skin.vb does not exist. The red leaf skin is doing the same thing as my skin... the control panel displaying for anonymous users... the red leaf skin also shows a warning that iskin.vb does not exist. However, dnn blue shows that the file exists and runs okay.

I've copied the line from dnn blue - which is fine - but it still warns that the file does not exist. I have checked for a skin.vb in admin/Skins, and I do not see it... in any of the dnn test sites I have.

So... maybe this is something that someone can enlighten me on a little better.

If you have double checked the security permissions are correct for the page, perhaps check the code for the control panel in your skin:

< div id="ControlPanel" runat="server" >< / div >

Is runat="server" included?

Thanks Lee for responding... your site is absolutely awesome and helpful.

The permissions are correct, and the control panel is set to runat="server".  I'm wondering if it is related to how the skin files were brought into DNN.  I simply added the files to the Portals/_default/Skins, and I'm wondering if DNN is not recognizing the skin.vb file because it is somehow not logically connected within DNN because it was not brought in using the web interface in DNN or by using the install folder.  I just haven't had time to try this out yet. 

Interestingly, the redleaf skin has the same behavior, and I have not modified that skin.  I did however, just copy the skin files from another DNN test site into the site I'm having problems with instead of using DNN install.

Also interesting is that I have tried to find the skin.vb file, and I cannot find it on my entire computer system.  I do have 'show hidden files' turned on.  I'm a little baffled by that one.

You need to install the skin files rather than copy them across, for instance the simple red leaf skin comes with a htm and a skin.xml file, when you install them, DNN combines them together to create an ascx file and then registers the skin in it's settings.

You may be seeing this behavior if a module on the page is set for edit by regular users.