We recently upgraded one of our apps (was running a 2008 version) to the latest version of the controls, and of course, the skins changed, and now I need to get the old skins back while keeping the new controls.
I found this post, and a few other articles on the site, and tried to follow the instructions:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/all-radcontrols-q3-2008-skins-are-now-compatible-with-the-q1-2009-release.aspx
This works mostly. I set up a directory under App_Themes called Default_2008 (using the Default skin from the files above) and set up entries in the web.config as instructed.
One of the issues I'm having is that some of the controls don't work properly without the embedded base stylesheets. The Menu and Editor are good examples of this. I thought about setting the EnableEmbeddedBaseStyleSheet property to "true" for the controls I was having issues with, but it seemed like there were some differences between the old base stylesheets and the new ones, so I didn't want to do that. Including the old base stylesheet code in with the custom skin stylesheet fixes things, but I'm not sure whether that's the best course of action.
Another issue I saw is that when I tried to include the Widgets stylesheets, it screwed up the entire site -- scroll bars no longer appeared, the alignment was all wacky, different fonts, bizarre sizing on controls, etc. I'm not really sure the best way to include these is, as I think they are needed to style the Editor control properly.
I feel like I'm trying to swim upstream with this, which usually means that I'm going about something incorrectly. Is there a better way of setting a custom site-wide skin than what I'm doing? I feel like I'm missing something important here.
I found this post, and a few other articles on the site, and tried to follow the instructions:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/all-radcontrols-q3-2008-skins-are-now-compatible-with-the-q1-2009-release.aspx
This works mostly. I set up a directory under App_Themes called Default_2008 (using the Default skin from the files above) and set up entries in the web.config as instructed.
One of the issues I'm having is that some of the controls don't work properly without the embedded base stylesheets. The Menu and Editor are good examples of this. I thought about setting the EnableEmbeddedBaseStyleSheet property to "true" for the controls I was having issues with, but it seemed like there were some differences between the old base stylesheets and the new ones, so I didn't want to do that. Including the old base stylesheet code in with the custom skin stylesheet fixes things, but I'm not sure whether that's the best course of action.
Another issue I saw is that when I tried to include the Widgets stylesheets, it screwed up the entire site -- scroll bars no longer appeared, the alignment was all wacky, different fonts, bizarre sizing on controls, etc. I'm not really sure the best way to include these is, as I think they are needed to style the Editor control properly.
I feel like I'm trying to swim upstream with this, which usually means that I'm going about something incorrectly. Is there a better way of setting a custom site-wide skin than what I'm doing? I feel like I'm missing something important here.
1 Answer, 1 is accepted
0
Andy
Top achievements
Rank 1
Rank 1
answered on 05 Nov 2010, 07:16 PM
Due to the length of time it was taking, we decided to just go with a new built-in skin