The key is to make them use the Banner and Footer for your skin, or better yet to convert them to .ascx pages so that they truly "plug-in" to the DotNetNuke portal.
In the top of the page you will probably find a reference to the core PortalBanner:<%@ Register TagPrefix="portal" TagName="Banner" Src="~/controls/DesktopPortalBanner.ascx" %>
If you change that line to refer to your skin's DesktopPortalBanner.ascx then you will get the page to point at your new skin. Problem with this is that the skins won't be able to be changed dynamically.
If all references to the PortalBanner and PortalFooter are removed and the page is made into a user control, then it can work independently of the skins and the framework.
I have converted the Portal Store available at Snowcovered to work as user controls, and I sent that conversion to the author, so you might want to check there first. |