Home → Bug Reports →

User interface defaults to Internet Explorer 7

• Edit

Michael McGinnis

Sep 27, 2012 @ 07:45 PM

Apparently some Cascade Server user interface code is making most of the content disappear from certain of my pages if they are edited using Internet Explorer:

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

This code forces the user interface to render if IE7 mode, even in IE9. The pages are fine if edited using Firefox or Chrome, or if I manually set the browser to IE9 using F12 developer tools. Otherwise only the title, header and footer are published.

Now, this only happens on pages that use XSLT to rearrange the DEFAULT region content (similar to the method IU demonstrated at the user conference).. So I could try to rewrite the format to avoid the problem. But does the user interface really still need to be keyed to IE7? I see that it still is in 6.10.9 - f3239b. How about 7.0?

1. Support Staff 1 Posted by Tim on Sep 28, 2012 @ 02:22 PM

   

   Hi Michael,

   Can you attach the page-level XSLT you are referring to? I'd like to have a look at it and also see if I can reproduce the behavior you mentioned above.

   Thanks

   • Edit

2. 2 Posted by Michael McGinni... on Sep 28, 2012 @ 06:15 PM

   

   The XSLT is applied to the Default region not the page. I've also attached the template. And here's the Data Definition for the Content Type:

   <system-data-structure>
     <text wysiwyg="true" identifier="article" label="Main"/>
     <text wysiwyg="true" identifier="sidebar" label="Sidebar/Footer"/>
     <text multi-line="true" identifier="extra" label="Extra Metadata"/>
     <asset type="block" identifier="aside" label="Block" render-content-depth="2"/>
   </system-data-structure>
   

   • custom-emergency.xslt 893 Bytes
   • secondary-template.txt 728 Bytes
   • Edit

3. Support Staff 3 Posted by Tim on Oct 01, 2012 @ 06:34 PM

   

   Michael,

   Thanks for attaching that information. Do you also have some content that I can copy/paste into the 'Main' section? I'm seeing in here that your XSLT is looking specifically for a <section> element having an id of 'emergencyContent'. I want to make sure that I am taking the same exact steps that you are to reproduce this behavior, so I'd like to get the same content you are pasting into the 'Main' section of your Page.

   Thanks

   • Edit

4. 4 Posted by Michael McGinni... on Oct 01, 2012 @ 06:37 PM

   

   Here you go. Thanks.

   • emergency.txt 3.19 KB
   • Edit

5. Support Staff 5 Posted by Tim on Oct 02, 2012 @ 12:52 PM

   

   Hi Michael,

   I had some more time to look at this yesterday and believe I found the cause. In IE, I noticed that TinyMCE (the WYSIWYG editor) is changing:

   <section id="emergencyContent">
   <!-- code here -->
   </section>
   

   to:

   <section id="emergencyContent"></section><section></section>
   <!-- code -->
   <section></section><section></section>
   

   This is breaking your XSL transformation because your XSLT is attempting to output everything inside of <section id="emergencyContent"></section> (which in this case is now empty).

   I tried this in a local development instance of Cascade Server which uses a newer version of TinyMCE and it is keeping the tags as expected. This newer version of TinyMCE will be available in Cascade 7.2. I don't currently have an ETA on when 7.2 will be released, but my guess is that we may release a Beta before the end of the year. Until 7.2 final is available, I would recommend avoiding edits to this page in IE since the behavior now causes your XSLT to output no content at all.

   Let me know if you have any further questions.

   Thanks!

   • Edit

6. Michael McGinnis closed this discussion on Oct 02, 2012 @ 02:43 PM.