Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: Issues with internet explorer 10 and MS 9311

  1. #1
    muro01 is offline Junior Member
    Join Date
    Jan 2009
    Posts
    19

    Default Issues with internet explorer 10 and MS 9311

    Hi,

    We just noticed that our site is not working with internet explorer 10 (not problem with firefox, chrome or safari), when we try to add click on the "add to cart" it doesn't do anything, i changed the IE10 to compatibility mode it worked fine, i noticed that when loading the page i get this JS error:

    SCRIPT5007: Unable to get property 'PageRequestManager' of undefined or null reference

    and when clicked to on add to cart i got this error:

    SCRIPT5009: 'theForm' is undefined


    Am i the only one having this issue? Any ideas on how can i fix it?

    thanks

  2. #2
    nicbe is offline Junior Member
    Join Date
    Apr 2008
    Posts
    3

    Default explanation and possibles fixs for IE10 issues with forms, post-back and javascript.

    Yes we were getting reports of login forms not working and the payment option choice facilities failing for customers using IE10 (please note - we are running an older version of storefront v.7.0.2.0 on non .net3.5 framework host servers (which is the main cause of our issues).

    The original browser definition files in the .NET 2.0 and .NET 4 frameworks do not recognise IE10 as a browser (as it wasn't invented then) so it defaults it to a 'down-level' definition. This stops support for features like JavaScript and post back cookie setting which is why login and forms etc. stop working.

    Hanselman explains the problem better than me here and he provides a series of fixes (we implemented the site only fixes which worked for us):
    http://www.hanselman.com/blog/BugAnd...rPosition.aspx

    If you are able to update your servers without it affecting your software then this MS hotfix may be best:
    http://support.microsoft.com/kb/2600100

    I hope this helps.