Saturday, July 10, 2010

DotNetNuke: Free Module - Sample SiteMap with Navigation and Filter

Check out this free dnn module showing site map with option to filter the links using alphabet. Here are some of it's features:
  • Ajax to load tab links for an alphabet
  • Option to see all tab links or specific tab link
  • Only initial version to present the idea
  • It uses jQuery Navigation Pluggin  to show filter links
  • Screenshot:

Further improvements and objectives

The basic idea to would be to create a module that can be used as a dynamic page that shows various links and can be used for SEO purpose.

Send your suggessions

Please send in your wish list of features that you expect and can add value to this. Please feel free to download and evaluate the module and use it in whatever way you want.


DotNetNuke: Common tips for skin Developers


    Skin Development

  1. How to add reference to jQuery?
    Add following server tag at the top of your skin file
    Add following at the end of your skin file:

    <%  DotNetNuke.Framework.jQuery.RequestRegistration()%> 
    <script runat="server">
     Protected Sub Page_Init(ByVal sender As Object, ByVal e As EventArgs) Handles Me.Init
     End Sub
    Thanks to Brian Dukes for correcting this
  2. How to access Tab Name?

    <%=  PortalSettings.ActiveTab.TabName%> 
    Now that you know how PortalSettigns is having ActiveTab you can play with properties of ActiveTab which is of type TabInfo
  3. How to access currently logged in user?

    <%=  PortalSettings.UserInfo.DisplayName%> 
    Once again PortalSettigns, you can use PortalSettings.UserInfo.Roles to provide role based elements to your skin.
  4. how to get path of Skin folder?
    Most useful and easy one

    <%=  SkinPath%> 
    so if you want to show an tips.jpg which is images directory in your skin root directory, do this

    <img src="<%=SkinPath %>images/tips.jpg" alt="tips" title="tips" />
  5. How to find default portal and admin skins from database?

    selecT* from PortalSettings where SettingName in ('DefaultAdminContainer','DefaultAdminSkin','DefaultPortalContainer','DefaultPortalSkin')
    select * from HostSettings where SettingName in ('DefaultAdminContainer','DefaultAdminSkin','DefaultPortalContainer','DefaultPortalSkin')
    DNN will try to look at PortalSettings table and see if admin and default portal skins are available there, if found, it will apply that settings otherwise it will load it from HostSettings table.
    Here is more advanced link from dnn blog.

    Reference and links for skin development

  1. There are lots of skin objects, which are described well here, or you can download entire DotNetNuke Skinning Guide from dotnetnuke website.
  2. Building dnn skins using BluePrint css framework
    Free Sample skin developed using BluePrint css framework
  3. Tutorial on building DNN Skins using YAML
  4. Pros and cons of using css frameworks in dnn


Please drop me a line to get any kind help regarding the dnn skin development and administration problems.