Custom skin not showing up after upgrade

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

    Posted 15 Oct 2012 Link to this post

    Hi, I had a custom skin in my current website and has been working fine for a while. I recently upgraded to the latest telerik asp.net ajax version using the upgrade wizard and it does not seem to be working at all anymore. I've compared the project prior to the update to the new project and I don't notice anything that is missing.

    Basically everything looks normal, the buttons, or the skin around the rad window is just invisible. 

    I look at the css of the page and I see it referencing it correctly... I'm kind of at a lost. Is there any common problems with this that I should be looking for?

    Thanks
  2. Galin
    Admin
    Galin avatar
    526 posts

    Posted 18 Oct 2012 Link to this post

    Hello Derek,

    Could you please give us more information about the older version, which you have used before?

    Also, you can view the Release notes.

    All the best,
    Galin
    the Telerik team
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Derek
    Derek avatar
    5 posts
    Member since:
    Nov 2008

    Posted 26 Oct 2012 Link to this post

    Just figured out the issue. For whatever reason it decided to add a css folder prior the file path.

    So in the file it was shown as 

    background-image:url('css/MySkin/Button/ButtonSprites.gif?v=2');

    but if you look at the generated CSS through the RadStyleSheetManager it would come out

    css/css/MySkin/Button/ButtonSprites.gif?v=2

    This must be a new feature with the latest version of Telerik compared to the year+ old version we were using prior. I simple went through and removed the css/ from the background image in the css files and so then the file path would come out correctly. Just like that it's working again.
Back to Top