Just finished reviewing all of the videos on how to build a skin for DNN 6.x. Outstanding information. However, for the sake of time, if I purchase a skin from the Store.DotNetNuke.com, how can I modify the elements using the information learned from the tutorial? I guess what I am asking, can I customize a pre-packed skin?

For example, one of the packages under consideration doesn't have a header pane. Can I modify the Skin.css and develop a header pane?

Thanks.

PS. Just subscribed to view all of the videos! Great source of information.

Yes, you will be able to modify the skin by modifying any of its components.

To add a pane, you would add this in either the HTML or ASCX file. You would add styles for the pane in the CSS file.

If you are comfortable doing so, I would delete all of the HTML files and work directly with the ASCX files. If not, modify the HTML files.

Appreciate the information. Now the other question I have is how to handle the page background color and/or image. Using using the PSD Skin developed in the tutorial, how would I have the border around the skin be a light blue? Or how would I add an image like a website that I recently came accross: http://funoutdoorliving.com/

Thanks.

You should be able to add an image like that using attributes in CSS for the appropriate element. That could be same element to which you have give a background color.

I see the files under the video 1, but is there anywhere where the complete files are? I have gone through all the videos but would like to start with the final files and modify it from there. Is this possible? thks.

Phil,

On this page: http://www.dnncreative.com/Home/tab...fault.aspx

I think that the final files are in the downloadable file.

I don't see them, only the initial ones, as part of tutorial 1, are listed in the downloads. I don't see complete ones anywhere. Could really use them. thks.

I am unable to access the videos. There is no hyperlink. Please advise.

Gail,

Unless you have subscribed to DNN Creative, the number of videos available is quite restricted.

Any chance of getting the final files uploaded. it would be very useful to start from that point instead of having to type in all the changes made throughout the tutorial. thks.

Although I'm a somewhat recent subscriber, I've watched a few video series and this is easily my favorite. The series covered all aspects for this skin including a little time on the menu. It wasn't a lot but enough to understand the CSS that it uses.

I'm actually watching it for the second time and I may have missed this but I needed to link to the PIE.htc file by navigating up one level, like this:

behavior: url(../PIE.htc);

Great work on the videos. Please keep stuff like this coming. You're easily one of the best resources available for DNN.

Mark

I have the following erorr after adding new page to dnn

Unhandled error loading module. DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot locate ContentPane for Skin
Unhandled error loading module. DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot locate ContentPane for Skin

any idea what is causing this

thanks

Are you using a custom skin? The message indicates that you do not have a pane named ContentPane. That is one of the few requirements for a skin file.

I have tried to align the menu to the right but I don't succeed.
Does anyone know how to do this?

Yes, it's a matter of getting the HTML and the associated CSS done correctly. Without seeing what you are doing, it's difficult to give a more specific answer.

Hi great tutorial, I am a little stuck with the lower panels this is my css

'/* Lower panes */
#lowerpanes {
width: 960px;
margin: auto;
margin-bottom: 16px;
}

#LowerLeftAndMiddile {
width: 635px;
float: left;
}
#LowerLeft {
width: 310px;
float: left;
}
#LowerMiddle {
width: 310px;
float: right;
}
#LowerRight {
width: 310px;
float: right;
}

.clear{clear:both;}
'

this is the div structure

see attached

however my panels line up wrong see image attached any idea what I have missed



thanks

M

If you want the three panes to line up side-by-side and with no space between them, remove the LowerLeftAndMiddle div and replace the two float:right with two float:left.

If you want some space between the panes, add a margin-right to the left and middle lower panes.

thank you very much for the tutorial.
first question: Can I create the package in DNN6 with usability in DNN 5.6.2
In the organization where I am working, the DNN 5.6.2 is installed and many sub portals designed before .Now the organization is planning to create some new sub portals with new skins for the other parts of the organization.
Can I install and use this skin (which I created in DNN6 as is taught in the tutorial) on DNN 5.6.2?
3)If the IT dep. decides to upgrade the DNN 5.6.2 to DNN 6, the modules that were compatible with 5.6.2 will work correctly?or we should buy them again? what about skins which were designed two years ago and compatible with DNN 5.6.2?
Thank you very much for your attention and help.
Pouya

Dear Mr. Craig
thank you for your answers.
I was faced with an error due to mistakenly installing razor host that was in DNN extension section, Then I couldnot see my portal anymore.I couldnot remove it too.I searched about razor and the error but by just deleting the razor host dll I couldnot remove it. I installed another DNN 6 on my local computer and copied the newly designed skin and container to the correct path Portals-> _default-> skin & container folders and also PIE.htc file in root
Now I don't have the box shadows and border radius in my IE6.
In mozilla is shown correctly but I have problem in IE6 which yesterday was correct on the previous installaton of DNN6.
would you please tell me what should I do now? I havenot changed any code
I just copied from old installation to the new one.

Razor Host Module: this requires that your website run under ASP.NET 4. That should be an easy change to the AppPool configuration.

Is the PIE.htc file supposed to add support for box shadows and rounded corners for IE6. If you've installed that correctly, I don't know why it's not working.