Why does my module default to back to DNN-Blue when I click the edit button? I have never seen DNN do this before...

Anyway, I am running DNN 4.7.0 (upgraded from 3.0.13) on IIS6/ Windows Server 2003 with SQL Server 2000. The skin is a custom skin that works on the old version of the site (DNN 3.0.13). I am on sort of a tight deadline to get this upgrade rolled out on my corporate intranet. If anyone has any idea's please let me know asap.

Thanks!

Hey Lan,

Thanks for the reply. I changed the admin skin and it worked like a charm. Yeah, I am referring to both the add new item button and the edit pencil from the lister. While this fits the criteria for the edit pencil I am not passing any URL variables from the add new item button beyond the control name and moduleid (which are required). So, I am afraid that I still don't quite understand what you mean.

Two questions:

First -  How do I load the edit control with record data without passing ItemId (or some derivitive thereof) in the URL?

Second - Why does DNN use the admin skin for non-admin pages? That is to say these controls do not reside in the admin or host menus so why are they treated as "administrative" controls?

Thanks in advance for your help and clarification.