Custom skins not working when using RadStyleSheetManager

2 posts, 0 answers
  1. Derek
    Derek avatar
    5 posts
    Member since:
    Nov 2008

    Posted 26 Oct 2012 Link to this post

    Hi, I've been really struggling with getting a custom skin to work in a test website.

    I created a simple skin through the telerik tool and extracted the zip file into my css folder. I added in the common and telerik folders to the same css folder.

    When I use a direct link tag in the header

    <link href="css/MySkin/Button.MySkin.css" rel="stylesheet" type="text/css" />

    With my button:

    <telerik:RadButton ID="RadButton1" runat="server" Skin="MySkin" EnableEmbeddedSkins="false"  Text="RadButton" >

    It works fine and shows up correctly. 

    When I attempt to use a RadStyleSheetManager the button shows up but with nothing in the background. No image.

    ID="RadStyleSheetManager1" runat="server">
                    <telerik:StyleSheetReference IsCommonCss="true" Path="~/css/MySkin/Button.MySkin.css" />

    I set the background in the css to just be a solid color and it shows up. So it looks like it's accessing the css and loading it correctly, but not actually loading the button image sprite. 

    <add key="Telerik.Web.UI.StyleSheetFolders" value="~/css/;~/css/Common/;~/css/Telerik/; ~/css/MySkin/; " />

    Is in my web.config. 

    How can I use the RadStylesheetManager with my custom skin?
  2. Derek
    Derek avatar
    5 posts
    Member since:
    Nov 2008

    Posted 26 Oct 2012 Link to this post

    I figured out the issue, it was purely something to do with the references from the web.config

    <add key="Telerik.Web.UI.StyleSheetFolders" value="~/css/;~/css/Common/;~/css/Telerik/; ~/css/MySkin/; " />


    <add key="Telerik.Web.UI.StyleSheetFolders" value="~/css/MySkin/; " />

    And it started working correctly. When I looked up in the css that was being generated I noticed that there was no button sprite being referenced and assumed that must be because of me referencing things I don't need to. I removed the unneeded references and it started working. 
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top