Skins now working

Hi,

I have created a skin file with the theme and the theme is correctly set for the master page. For some reason it is not picking up the skins. But the slyles are correctly displayed. Any idea why? My theme is defined under App_Themes asp.net folder.

Thanks!

This is the code in the masterpage:

<asp:HyperLink ID="lnkHome" runat="server" SkinID="HomeLink"></asp:HyperLink>

<asp:HyperLink ID="lnkContact" runat="server" SkinID="ContactLink"></asp:HyperLink>

<asp:HyperLink ID="lnkCareers" runat="server" SkinID="CareersLink"></asp:HyperLink>

<asp:HyperLink ID="lnkLogin" runat="server" SkinID="LoginLink"></asp:HyperLink>

<

asp:HyperLink runat="server" NavigateUrl="/beauty-home" >Home</asp:HyperLink>

asp:HyperLink runat="server" NavigateUrl="/beauty-home/careers" SkinID="CareersLink">Carrers</asp:HyperLink>

<

asp:HyperLink runat="server" NavigateUrl="/beauty-home/login" SkinID="LoginLink">Login</asp:HyperLink>

Hi Duneel,

There is a bug related to the .skin files that we have logged for fixing with ID - 103355. The .skin files does work properly in Sitefinity 4.0, but all stylesheets are applies correctly on the page. You can style the control by using the theme stylesheet with some css rules inside it.

Kind regards,
Ivan Dimitrov
the Telerik team

Hi Ivan,

My requirement is to have a diferrent NavigateURL for each theme for few hyperlink controls in the MasterPage. How do I do that using CSS Rules? Can you share some sample code if you have?

Thanks!
Duneel

Hi Ivan,

Do you know when bug 103355 is going to be fixed?

Thanks,

Steve

Hello Duneel,

The current status of the bug is "Not Done" and the it has not been assigned to someone for fixing. We will review all bugs after 3rd of January and see what can be fixed for the official release.

Regards,
Ivan Dimitrov
the Telerik team

Any update as to when skins will be supported?

Thanks

Hello Duneel,

We will definitely do it in Q1. It's possible to have a fix earlier, and in this case we will release it in an internal build. I suggest you following the internal builds from the next week (we cannot fix it this week for sure).

I hope this helps.