Perhaps I am missing something elementary.

I borrowed the skeleton of an andreas css skin and customized it for my site, I'm still working on it.

I set up a 2 column layout that works well, then I created a 3 column layout that needs more work.

I applied the 3 column layout to the home page in the Page Settings, and now all the other pages are showing three columns, including Terms and Privacy, which I would like to use the 2 column skin.

Have I done something incorrectly??

Also is it possible for me to tell DNN which skin ascx layout to use for the Terms and Privacy pages??

Home is the only page I want to use the 3 column layout.

Thank you, Tom


P.S. I am getting faster and better responses here than on the DNN forums, which are so broken that I can't post...forums is not a module I would recommend seeing it not work very well on the DNN site.

If you set the 3-column page to the home page, and didn't apply it to other pages, then the other pages should be ok. I'd suggest that you visit the other pages, look at their "Settings" and see which skin is applied.

If you want the 2-column layout to apply to every page but the home page, make that the default skin on the admin page, and make no selection on most pages. Apply the 3-column to just the home page.

As for the Privacy and Terms pages, many people create their own pages to avoid the issue that you have mentioned.

As for the DNN forums, I've been trying to ask a question over there since yesterday, and all that I get is errors. So, yes, something is broken ... yet I see new posts.

Hello,
Thanks for responding, I think I have it working now with 3 vs. 2, fingers crossed, etc.
Thanks also for the suggestion about Privacy and Terms, I will do that.

Is there anything specific about specifying links to Terms and Privacy in the footer per se?? -- since I won't include them in the menu??

Thanks a lot,
Tom (still a super newbie)

Just put links to YOUR Privacy and Terms pages in the footer and don't include the DotNetNuke objects.

Hi All,

I'm running into the same issue with the privacy page.  I have changed my "default" skin in Admin but it has no effect on the privacy page.  I would like to know why this is, though, instead of trying to band-aid this.

Any suggestions as to where to look into on this?

Thanks!

Mark

Hello Mark,

It's usually much easier and faster to create new, separate privacy/TOS pages and link to those instead instead of using the DNN tokens. Upon creating these pages, you can apply whatever skin you want.

This is a standard solution to the problem of skinning the privacy/TOS pages.

HTH Tom

Thanks Tom,

I really don't want to band-aid this though.  I would like to figure this puppy out instead.

Anyone have an idea where to start?  Is it in the code-behind?  What exactly tells this privacy.ascx to use a particular skin?

Thanks,

Mark

This recommendation is not a band-aid solution.
It is a complete replacement of the DNN tokens with pages that you create.

DNN itself decides how the contents of the privacy token, stored in *.resx files, are styled.
You don't edit privacy.ascx or privacy.ascx.vb, there's nothing in them for you to edit related to styles or skins.

It depends how much time you want to put into it -- the time to quickly whip up privacy/TOS pages that suit your needs or the time to hunt down how DNN styles those pages.

However, whatever is your site skin is what privacy/TOS should style as...but there are lots of DNN style tags in those tokens' text that you will have to style on your own, whereas with your own pages, you determine styling etc.

De gustibus non disputandum est, I suppose...

There may be something else going on in your site which prevents the privacy token page from taking on the proper skin appearance.

HTH Tom

Thanks again Tom,

You're right in that you can't dispute taste.  It's how I wish to tackle this particular problem.  You have provided an excellent alternative to working with what DNN should do correctly.

I'm that kinda guy that wants to know why it is happening though.  I like to take things apart and put them back together.  When I see a problem that, by all rights, shouldn't be a problem, well then, I like to know why.

To each his own.

Mark

Help may be on the way: http://www.dotnetnuke.com/Default.a...tryID=1697