1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Theme Conversion From 3.7 to 4.0

Theme Conversion From 3.7 to 4.0

4 posts, 0 answered
  1. Peter
    Peter avatar
    3 posts
    Registered:
    29 Jan 2008
    06 Oct 2011
    Link to this post
    I am having issues getting the navigation control to appear in 4.0 as it did in 3.7.  I copied my Theme to the App_Theme/Theme-Name/Global directory and while the theme seems to apply correctly to the rest of the page, the RadMenu (navigation control) is appearing without any styles.

    I have a RadMenu.skin file in the Global folder which references the Menu folder and i tried setting the wrapper to Menu and it still doesnt work.

    How can i get the navigation skin from 3.7 to work in 4.2?
  2. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    07 Oct 2011
    Link to this post
    Ok, so in the Nav control down on the bottom right you specified the wrapper class (skin) as "Menu"?

    That means your custom skin .css should have items in it like this

    .RadMenu_Menu
    .RadMenu_Menu a.rmLink{
        
    }

    Assuming that's all right, I would then as a next step fire up Firefox, and firebug.  Go to the "Net" tab and make sure that CSS file is indeed coming down okay.

    Steve

  3. Stanislav Velikov
    Stanislav Velikov avatar
    1113 posts
    Registered:
    18 Sep 2017
    11 Oct 2011
    Link to this post
    Hi Peter,

    What Steve suggested is the correct approach to attach styling in Skin files to your navigation control. If you are experiencing any more troubles applying the styling please write back.

    Regards,
    Stanislav Velikov
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  4. Peter
    Peter avatar
    3 posts
    Registered:
    29 Jan 2008
    11 Oct 2011
    Link to this post
    The wrapper class was set up correctly as were the css class names.  The problem turned out to be that the .skin file in the root of the theme was causing the css file not to be read correctly for some reason.  In 3.7 we had our theme set up with the skin file at the root of the theme and the Menu css and files in a folder named Menu:

    Custom Theme
    ---Menu
    -------Menu.css
    -------img.gif
    ---Panel
    Menu.skin


    The minute i deleted the skin file and moved the menu.css file to the root, it seemed to work fine (i had to update the image references in the css file, but that wasnt too much.)

    Hope this makes sense.
4 posts, 0 answered