+1-888-365-2779
Try Now
More in this section

Forums / General Discussions / Sitefinity 3.7 does not like IE9

Sitefinity 3.7 does not like IE9

16 posts, 0 answered
  1. Robert Williams
    Robert Williams avatar
    11 posts
    Registered:
    27 Sep 2012
    22 Mar 2011
    Link to this post
    I downloaded IE9.  The browser was much better without the extra space gone.  I, though, went to edit a site I developed in Sitefinity 3.7.  I really didn't like how it moved the Add Controls from the right to the left.  As a result, I could not publish the page.  Major pain!  I don't know how compatible newer versions of Sitefinity is with IE9, but that was my experience. 
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    22 Mar 2011
    Link to this post
    Hello Robert,

    Sitefinity 3.x and 4.0 does not support IE 9 officially. We will try to sort out the issue for Sitefnity 4.0 and IE 9 after Q1 which is scheduled for the first half of April. We are going to discuss whether it will be possible to release SP for Sitefinity 3.x as well.

    Regards,
    Ivan Dimitrov
    the Telerik team
  3. RSewell
    RSewell avatar
    54 posts
    Registered:
    25 Apr 2007
    24 Mar 2011
    Link to this post
    Before I read this or saw any announcement from Telerik regarding IE9, I also upgraded.  "Add Controls" is still on the right for me.

    The only thing I've noticed is that the first page I edited (the site's Home page) under IE9 became locked by the edit, and I can neither Publish nor cancel changes.  It posts back to itself, but will not go back to the Pages view, and does not give me any message indicating a problem.  If I use the browser's Back button to go back to All Pages view, it shows a red lock on the file and it says I have it locked.

    How do I unlock this file?
  4. RSewell
    RSewell avatar
    54 posts
    Registered:
    25 Apr 2007
    24 Mar 2011
    Link to this post
    Oops.  Forget my complaint above.  I see that my problem was caused by something else entirely.  I had an old version of a user control that used the PostBackUrl on one of the controls.  I uploaded the new control, refreshed, and was able to cancel the update.
  5. Mike
    Mike avatar
    208 posts
    Registered:
    10 Dec 2007
    02 Apr 2011
    Link to this post
    Hi Ivan,

    I hope for the sake of those of us who are supporting lots of clients on Sitefinity 3.x we are able to get a patch for this.

    But for others reading this, I've found that adding the Meta tag:

    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

     


    fixes this issue.  Make sure you add the tag before any stylesheet declarations, and you're going to want to check the site thoroughly for styling changes that may be impacted by this. Of course, that doesn't help people who can't (or won't) add the tag.

    Regards,
    Mike Sharp
  6. Shaka
    Shaka avatar
    11 posts
    Registered:
    07 Jan 2011
    03 May 2011
    Link to this post
    I am having the same problem. I think one of my developers tried to edit a page using IE9 on a MAC. We both use the same administrator account to login and edit the pages. But now when I login, one of the pages is locked, and I do not know how to unlock the page.
    How can I unlock the page that is currently locked?
  7. bindu
    bindu avatar
    1 posts
    Registered:
    07 May 2011
    07 May 2011
    Link to this post
    any problem with google crome or firefox?
  8. Henry
    Henry avatar
    1 posts
    Registered:
    12 May 2011
    13 May 2011
    Link to this post
    We are using Chrome in our office. So far, we don't have major problems with it
  9. Scott Bradley
    Scott Bradley avatar
    27 posts
    Registered:
    20 Jan 2010
    30 Jun 2011
    Link to this post
    Mike:
    This sounds promising.  Where should that tag go? in the master page of the page we're editing?  or a sitefinty admin template?
  10. Mike
    Mike avatar
    208 posts
    Registered:
    10 Dec 2007
    30 Jun 2011
    Link to this post
    For me it worked by simply including it in the master page of the page I was editing, but that might not be the only place in the administration screens where there might be problems with IE9.  And to be honest, I'm a little suprised that it worked at all, since that page is rendered inside of the administration page. 

    But if you don't want that on your site's master page, you could try to add it to Sitefinity/Admin/Admin.master.  If a new Sitefinity SP or build came along that fixes the issue, it would simply replace your change anyway, so modifying a Sitefinity file like that seems harmless.  It's worth a try anyway.  Try it and let me know how it works out.

    Regards,
    Mike Sharp
  11. Eric Tangedahl
    Eric Tangedahl avatar
    12 posts
    Registered:
    11 Aug 2009
    12 Jul 2011
    Link to this post
    Is there now a SP available so v3.7 will work properly in IE9?
  12. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    13 Jul 2011
    Link to this post
    Hi Eric,

    The SP that will fix IE9 issue for 3.x edition is not scheduled. You can try to upgrade the RadControls with bindingRedirect, but this might broke other parts of the CMS.
    Another option is migrating to 4.x edition using the migration tool.

    Regards,
    Ivan Dimitrov
    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
  13. Eric Tangedahl
    Eric Tangedahl avatar
    12 posts
    Registered:
    11 Aug 2009
    04 Aug 2011
    Link to this post
    Can you point me towards the 4.0 conversion tool?  Does this seem to be working fairly well for users or has it been a difficult conversion?

    thanks,
    Eric
  14. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    05 Aug 2011
    Link to this post
    Hi Eric,

    The migration tool will be build as a module with 4.2 release. It migrates the data from all build in modules, pages, users etc with several clicks. We removed the tool from codeplex and now there is a forum thread about the migration.

    All the best,
    Ivan Dimitrov
    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
  15. Julio Molina-Muscara
    Julio Molina-Muscara avatar
    4 posts
    Registered:
    12 Aug 2005
    31 Aug 2011
    Link to this post
    I was able to fix the Internet Explorer 9 (IE 9) not working well in Sitefinity 3.7 problem by enabling the Compatibility View option.

    This option is found under Tools.

    Simply browse to Sitefinity 3.7 site and enable the Compatibility View option. You can test the fix by editing a back end page and finding the ability to edit Generic Content controls and other features.

    You can enable the Compatibility View option by selecting it from the Tools menu, or by clicking the little icon of a broken page that's located to the right of the address bar. 

    I hope this helps :)
  16. Mike
    Mike avatar
    208 posts
    Registered:
    10 Dec 2007
    30 Sep 2011
    Link to this post
    An update to an old post, I know, but I recently came across an issue that my previous fix didn't address.

    If you need to use CSS3 on a site, putting the metatag in the master page defeats that support for IE9, so what I did was add this to the master page head (an asp:literal)
    <head id="Head1" runat="server"  profile="http://www.w3.org/2005/10/profile">
        <title></title>
        <meta http-equiv="content-type" content="text/html; charset=utf-8" /> 
        <asp:Literal ID="CompatLiteral" runat="server" />
        <meta name="progid" content="CPi.Web.Public" />

    Then in the codebehind, I added this to the master page load event:
    protected void Page_Load(object sender, EventArgs e)
    {
        if (!IsPostBack)
        {
            Literal headLiteral = this.Page.Header.FindControl("CompatLiteral") as Literal;
            if (CPi.Web.Public.Utility.IsPageInEdit(headLiteral))
                headLiteral.Text = "<meta http-equiv=\"X-UA-Compatible\" content=\"IE=EmulateIE7\" />";
        }
    }

    On all my projects, I have a common Utility class in the App_Code directory, with some common static methods, such as tests for whether a page is in Admin, Edit or Preview mode.

    Anyway, the idea is this injects the X-UA-Compatible meta tag in the head controls (at a specific location, which is why I can't simply add it to the controls collection) whenever a page is in Edit mode. 

    Until I upgrade this client to SF 4.0, this works for me, so I thought I'd share it. 

    Regards,
    Mike Sharp





Register for webinar
16 posts, 0 answered