I am currently designing some page tempates.

What I notice is that my skin settings in the template (see below) aren't being used or are being overwritten by the default skin settings of the portal. Thus adding the following to the xxx.page.template does not result in the specifc skin being selected if the default portal skin is a different one.

<tabs>
<tab>
<skinsrc>[G]Skins/myskin2/DefaultNoImage.ascx</skinsrc>
<containersrc />
...

IMHO This behavior takes a lot of fun out the use of page templates, my client still has to manually select the skin while adding a page.

So my kind question is, how do you think about it? What should be the default behavior?

Peter

Not quite sure what you mean, but to answer your question: the skin is not added to the page record in tabs table (value is still NULL) so not a formatting problem I suppose.

Peter

This still apears to be an issue in 4.8 - any thoughts on when this will be resolved or has it been with 4.9 or 5? It certainly reduces the usefulness of page templates...