Sitefinity 3.7 bug on IE 10

6 posts, 0 answers
  1. Shari
    Shari avatar
    1 posts
    Member since:
    Mar 2011

    Posted 30 Nov 2012 Link to this post

    Hi We are using sitefinity 3.7 for two of our applications, found a serious bug when open the site on IE 10, when we go to https://www.medicalhomebuilder.org/sitefinity ( https://www.medicalhomebuilder.org is our domain name) and enter username and pwd, we got a server error:  Invalid value for 'encryptedTicket' parameter, it happens on our other site as well.

    We can't find the forum for sitefinity on your site now.
    Can you tell us how to fix it or tell us where should I post this question.
    Thanks,
  2. Stefani Tacheva
    Admin
    Stefani Tacheva avatar
    7 posts

    Posted 04 Dec 2012 Link to this post

    Hi,

    I want to inform you that unfortunately Sitefinity 3.7 does not support Internet Explorer 10 and your Sitefinity 3.7 might not work properly with this browser version. Apologies for the inconvenience.

    Kind regards,
    Stefani Tacheva
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Mark
    Mark avatar
    15 posts
    Member since:
    Feb 2010

    Posted 11 Dec 2012 Link to this post

    Michael

    Have you tried forcing compatibility mode - emulate IE 7 or similar??
  4. Stefani Tacheva
    Admin
    Stefani Tacheva avatar
    7 posts

    Posted 26 Jan 2013 Link to this post

    Hi,

    We are unable to reproduce the problem on our side. However, the information below might be useful:

    Sitefinity uses the standard ASP.NET Login control that comes with the .NET Framework. The error comes from FormsAuthentication.Decrypt ASP.NET static method when it is trying to decrypt authentication ticket which is passed as a string.

    It is possible that encryptedTicketstring is very long, it is string empty or it is not well formated and it could not be decrypted. ASP.NET uses the <machineKey> element for encryption and decryption of
    forms authentication cookie data. By default, both both validationKey and decryptionKey are set to AutoGenerate. There might be  a problem if you are running the website in web farm with AutoGenerated keys.

    All the best,
    Stefani Tacheva
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  5. Justin
    Justin avatar
    1 posts
    Member since:
    Aug 2011

    Posted 16 Apr 2013 Link to this post

    Hi Stefani,
    When you say "By default, both both validationKey and decryptionKey are set to AutoGenerate", where can we change this in a 3.7 build.  We have customers still using this version and cannot even login to the backend in IE10 without using Compatability mode or forcing IE9 document mode.

    Version 3.7 isn't that old and many of our/your customers still need this resolved.  Thanks in advance.
  6. Stefani Tacheva
    Admin
    Stefani Tacheva avatar
    7 posts

    Posted 19 Apr 2013 Link to this post

    Hello,

    The following version Sitefinity 3.7 has been released 2010, when there were no IE 10. The Sitefinity 3.7 version is using old version of rad controls. Rad controls teams have introduced official support for IE10 and Visual Studio 12 in a "Refresh" named build ver. 2012.2.815 of rad controls. This build is not available in the release notes. The latest official build Q3 2012 SP2 (version 2012.3.1308), offers full support for IE10. This means that if you want to use Sitefinity on IE10 you need to migrate your project to Sitefinity 5.4.

    The RadControl teams are following the trends and provide support for new browser versions in releases of Rad controls, which are follow them. There are cases in which the new browsers are with backwards compatibility with the old processors, then the old versions of Rad controls work with them. Chrome and Firefox rarely have breaking changes. IE itself are trying to improve their browser and we need to make a lot of changes in Rad Controls because of these breaking changes they make with every release of IE. This is the reason why our old versions of Rad controls are not working on IE10. If you do not want to migrate your project to our latest Sitefinity version 5.4 you could render the page in old IE mode:

    <meta http-equiv="X-UA-Compatible" content="IE=8" />
    or
    <meta http-equiv="X-UA-Compatible" content="IE=9" />

    All the best,
    Stefani Tacheva
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top