Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Affordable ASP.NET Hosting Service
  Ads  
Webhost4Life - $4.95 Windows Hosting
 


  Sponsors  

Meet Our Sponsors

FCKeditor Project
Salaro -- Skins and more
OnyakTech
CrystalTech Web Hosting™
Webhost4life, specialists in DNN hosting
Mad Development is a full service interactive agency focusing on the merge of design, technology, e-commerce, and affiliate marketing by providing total website solutions.
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Extend It! ( Pr...  Cleaning up skinPlaceholder output
Previous Previous
 
Next Next
New Post 3/9/2006 3:26 AM
User is offline Neil Highley
3 posts
www.neilhighley.com
10th Ranked


Cleaning up skinPlaceholder output 
DNN 3.2.2

Hello,

I am trying to clean up the code generated by the skinPlaceholder (skinController).
Currently, every module item generates the following script:

<div id="dnn_contentPane" class="pad">
    <a name="393"></a>
    <span id="dnn_ctr393_ContentPane" align="left">
        <!-- Start_Module_393 -->
        <div id="dnn_ctr393_ModuleContent">
        </div>
        <!-- End_Module_393 -->
    </span>
</div>

What I would like to happen is that the span is created as a DIV as our inhouse design documents restrict the use of divs within spans.
I have stepped through the DNN source code trying to find where the span is created but cannot locate the section/class I need to edit.

I have got as far as the skinController and the skinFileProcessor, but cannot alter the output.

If someone can help, even by pointing me towards a DotNetNuke Source code design document, I would be extremely grateful.

Neil Highley
 
New Post 3/10/2006 2:51 AM
User is offline Neil Highley
3 posts
www.neilhighley.com
10th Ranked


Re: Cleaning up skinPlaceholder output 
I have found the solution to this problem, and it would have been prevented by a better documentation of the skinning process. this problem can be laid at both DotNetnuke and Wroxs doors as they both plagiarise a extremely brief explanation, with acronyms not explained, examples not provided and spelling mistakes in the main xml document.
Also, the documentation of the source code is also almost non-existant, with most summarys consisting of the name of the function paraphrased without any indication of framework functionality.

The following post (saved independently from the dotNetNuke forums) helped immensely and summarises in a much better way than any of the official documentation or books. Kudos to the author :)

http://forums.asp.net/1134269/ShowPost.aspx

Anyhoo.

There is a default container within the containers folder which is used to wrap any module added to a tab. Currently it uses a span tag. To ensure HTML 4.0 and above compliance, change this to a div.

portals/
    /default
       /containers
          - No container.ascx

Summary
To add container skins via the XML file, set the containerName to the folder name within portals/_default/containers and the containerType to L (meaning that it is a LOCAL container skin) and set the containerSrc to the file you wish to use to wrap a module.
Place the corresponding containerSrc file within the containerName folder and reference it within your skin by using the containerSrc.
Also, check out the link above for a more detailed explanation.

Good luck.

Neil Highley
http://neilhighley.com
 
New Post 3/10/2006 6:02 AM
User is offline Neil Highley
3 posts
www.neilhighley.com
10th Ranked


Re: Cleaning up skinPlaceholder output 
Another span tag can be found in the
DesktopModules/Html/htmlModule.ascx

Neil Highley
 
 Page 1 of 1
Previous Previous
 
Next Next
  Forum  General DotNetN...  Extend It! ( Pr...  Cleaning up skinPlaceholder output
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:

1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
 


Personify Design, Inc.
Seattle-based Personify Design has developed customized DotNetNuke websites for a wide range of customers to meet many different types of needs, including distributed authorship across thousands of pages to integrated Verisign e-commerce capabilities.
www.personifydesign.com 		DNN Outsourcing
50% more affordable services comparing to Western Europe and US: Custom DotNetNuke module development, skins, consulting, maintainence... Over 15.000 working hours of experience in custom DotNetNuke Solutions development, 8 years experience in outsourcing, excellent references!
www.dnnoutsourcing.com 		Expressnet - DotNetNuke Hosting
Expressnet provide premium quality ASP.NET Web Hosting. We specialise in Windows based products including ASP.NET and Microsoft SQL Server. We offer fantastic value packages for DotNetNuke hosting. We also offer free asp.net web hosting
www.expressnet.com.au

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP