Button icons in dev, not in prod...

2 posts, 0 answers
  1. Philippe
    Philippe avatar
    8 posts
    Member since:
    Jun 2010

    Posted 21 Feb 2014 Link to this post

    I use some buttons with PrimaryIconCssClass defined. (2013Q3SP2 version 13.3.1324.0)


    <telerik;RadButton ID="btnSend" runat="server" Skin="Silk" Text="Envoyer" OnClick="btnSend_Click">
        <Icon PrimaryIconCssClass="rbMail" PrimaryIconLeft="8" PrimaryIconTop="5"></Icon>

    Everything runs fine in development, but the icons are not displayed in production (see attaches file) !
    Any idea ?

  2. Danail Vasilev
    Danail Vasilev avatar
    1502 posts

    Posted 24 Feb 2014 Link to this post

    Hello Philippe,

    I have already replied to the same question you have asked in the support ticket, so that I paste my answer here, for the rest members of the community:

    I can suggest that you try the following steps:

    • Can you confirm there aren't any JavaScript errors on your page that could break the proper functionality and rendering of the script control on your page? If there are such errors they should be find and fixed.
    • It may be possible that there are some global styles on your page layout that breaks the appearance of the scripts controls. You can try removing all of the custom CSS and if that fixes your issue, then you can start turning one by one the styles until you find and fix the problematic rule. More information on this matter is available in Distorted Appearance help article.
    • Can you confirm that all the requests executed by the page are successful? If there are requests which are not successful they could prevent control's scripts and styles from loading. If that is the case you can try
      • Toggling the state of the CDN(turning it on/off)
      • Clearing the cache of the browser/ASP server on which you are running the page.
      • Use Fiddler or FireBug to see which requests are failing and why. You can also examine briefly Web Resources Troubleshooting and Troubleshooting Deployment on the Production Server help article and use the provided solutions, in case similar issues are present.
      • Can you check whether the system date of the production server is not correct and if so, does fixing it resolve the issue?
    • Can you confirm whether the issue is browser specific (if so which is the browser and its version) or it occurs in most major browsers like FireFox, IE, Chrome, etc?

    Danail Vasilev
    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 UI for ASP.NET AJAX, subscribe to the blog feed now.
Back to Top