Hi,

As I understand it I can define as many content areas as I like via in my skin simply having a div with runat="server" and a unique ID.  I can then, on a specific page using that skin, add modules to each as needed.  The one called ContentPane automatically gets a HTML module added to it when you create a new page.

My question is: is there any way I can define a skin with more two (or more) content panes which will both, automatically, get a new HTML module when a new page is created using that skin, in the way that ContentPane does today?

Adam

OK.  I created a page and exported it to the template.  If I create a new page based on that template then it has the right modules, but the Skin is always the default portal skin.  I have to then manually change the skin?  There is a line in the .template file which seems to indicate the skin, but it's ignored. (For example <skinsrc>[G]Skins/MySkin/MySkin_ThreeCol.ascx</skinsrc>).

Actually, what I have different behaviour depending on how I create the new page, but none of it works as it should, I would say.

If I create the page using the control panel (choose a name and a template and click "Add page") then the page is created with the right permissions and modules, but the default skin.  If I then edit the page and change the skin then it is right.

If I click the New button to open the create page/page properties screen directly, then changing the template updates neither the permission nor the skin.  The modules are right, but the rest must be set manually.

Is this a bug or is this really the intended behaviour?  Seems odd that the .template file has a reference to the skin which doesn't appear to do anything.  Also, I'd like to be able to say to my users "To create a page of this type, simply choose this template" and it would have the right skin, the right modules and the right permissions.

So is DNN limited in that Content Managers cannot easily create content:
create a new page, select a template and then input content?

With DNN it seems users need to:
1. create a new page,
2. select a template,
3. select a skin,
4. add modules,
5. and/or module settings, and then start inputting content.
It’s a cumbersome and impractical process for users; especially non-technical content managers who are usually responsible for creating content on CMS websites.