1Pane_main.ascx  I have viewed video 4 twice now. I have not done the tutorial yet so that may answer my question.

How does 1pane_main.ascx know that it is hooked up to 1pane_main.css? Is it the naming convention

Thanks
Dennis

Hello,

Yes that is correct, if you add in a CSS file that is the same name as the skin.ascx or skin.htm file, DotNetNuke will then call in that CSS file only for that skin.

We covered how to do this in an earlier tutorial here:
Multiple skin layouts using skinname.css

Thanks,

wow, please don't go back to 1 video per zip.  It is so much easier to download once.  I suppose if one had a very slow connection it might be a problem but down loading each file independently is exceptionally time consuming and labor intensive.

BTW - I loved this issue.

Thanks for the feedback Rick,

Hi Lee, Im trying to work out how to change the color of the background down the left & right sides of the 1024 width skin? Am using 05.01.00 (773)Community Edition. Is this covered in one of your tutorials? Keep up the great work!

Do you want to change the background color outside of the content panes, or in them?  Which skin?

Basically, you'll want to locate the object, and then change it's color in the CSS.  Have you taken a look at Troubleshooting DotNetNuke Skins?  The Web Developer's Toolbar is a handy tool you can use to identify parts of the page.

Hi & Thanks for your post. Outside the contents panes. Im using dnn 5 & the 1024 standard skin that I have modified.

Hi, Turns out is #Body { background: #cad2d4 repeat-x top left; height: 100%; margin: 0; padding: 0; } in the skin.css file. in my case i removed the url link to the image & chnaged the color & BINGO !! I wouldnt have been able to go close to working this out had it not been for Lee's skinning & nav menu tutorials. Thanks so much DNN Creative

Hi,

I am also having trouble using the pop-up feature only with Visual Web Developer 2008 Express Edition. This feature works on the HTML tags but not on the skin objects.

Folders such as Admin and Portal are at the first level in the VWD explorer, so I must have opened up the web at the DNN root. I am using standard IIS 5.1.

Where does VWD find the references to the skin object attributes?

By the way, I love your videos! Thanks.

Could you ask the question differently?  I'm not sure what the pop-up feature you are asking about is.

<!--[if gte mso 9]> fficeDocumentSettings> oNotRelyOnCSS/> ixelsPerInch>72ixelsPerInch> 1920x1200 fficeDocumentSettings> <!--[if gte mso 9]> Normal 0 unctuationKerning/> false false false oNotPromoteQF/> EN-US X-NONE X-NONE ontGrowAutofit/> ontVertAlignCellWithSp/> ontBreakConstrainedForcedTables/> ontVertAlignInTxbx/> oNotOptimizeForBrowser/> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} span.EmailStyle15 {mso-style-type:personal; mso-style-noshow:yes; mso-style-unhide:no; mso-ansi-font-size:11.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> <!--[if gte mso 10]> Joseph,

I guess I wasn't that clear.  I'll start over:

I generally use Dreamweaver to create my skins but based on Lee's video, I decided to try Visual Web Developer Express 2008. I did this because of its Intellisense feature that supports skin objects. I followed his instructions and opened a web site at my local DNN root.

 

The problem is that even though I have Intellisense for the html tags, I have no Intellisense for the skin objects.

 

I can’t remember where VWD references the Intellisense data to support the skin objects. Do I have to install the source version of DotNetNuke for this feature to work or are the references at the top of the skin page all that is needed? I used the install version of DotNetNuke. Thanks.

 

Regards,

Fred

Hello,

I used an install version of DotNetNuke for the tutorial, not the source version, so it should work.

As long as you open the website at the root of your installation and then open the .ascx skin files intellisense should work.

Thanks,