If you have specified a skin in Page Settings for the CMS page that has your feature, and you are passing the pageid param to your supporting page, just do this:

protected override void OnPreInit(EventArgs e)
{
AllowSkinOverride = true;
base.OnPreInit(e);
}

that tells the base page that the page specific skin should be allowed.

Hope that helps,

Joe

Maybe you are not really implementing a feature like the existing features are implemented. Existing features support page skins exactly as I have told you.

For example:

1. In Site Settings check the box to allow per page skins
2. Create a page and put an instance of Forums on the page
3. In Page Settings for the page that has the forums select a different skin
4. The skin will be used on the page and in the supporting pages of the forum ie ForumView.aspx and Thread.aspx
5. The reason it works is because it uses the same code I showed you in those pages

protected override void OnPreInit(EventArgs e)
{
AllowSkinOverride = true;
base.OnPreInit(e);
}

For it to work the ModuleControl (ForumModule.ascx) for the forums must pass the pageid parameter in its links to ForumView.aspx and ForumsView.aspx passes the pageid param to Thread.aspx

You can study example code for existing features and step through it and see that it works.

Hope that helps,

Joe

You are working against the grain of the system by not building features the recommended way.

Instead of HumanResources.aspx why not make HumanResourcesModule.ascx as a feature that plugs into a cms page, this is how the entry point of a feature should be implemented, then if you need additional supporting pages for the feature you link from the .ascx to .aspx page and pass the pageid and module id

The problem with the way you are doing it is that since no page id is passed in no page specifc skin can be applied and without a pageid is the same as if passing in the home page page id, that is what makes it the default page.

You could solve it from your own code without follwoing this recommendation but you make more work for yourself.

You will have to so it in OnPreInit but after OnPreInit completes in mojoBasePage so that you change it after mojoBasePage

protected override void OnPreInit(EventArgs e)
{
// let mojoBasePage do its thing
base.OnPreInit(e);

// write your own code here to set it as you wish but you'll have to figure out how to do that from code in mojoBasePage
}

I think it is better work with the grain of the wood not against the grain of the wood by implementing it in the recommended way as an .ascx you will have less work to do, by going against the grain you have to do more work.

Hope that helps,

Joe

I think it would not be so difficult to copy the code and logic from a .aspx page into a .ascx user control that can then be loaded on a cms page like any other feature, but its up to you of course.

Best,

Joe