// you’re reading...


RedDot CMS at the moment not compatible with Internet Explorer 8?

As Henry Lu has pointed it out on the google groups

I’ve been using IE 8 to access RedDot CMS 7.5 and RedDot CMS 9. Why?
Just for the heck of it.
It is pretty much a death sentence when using IE 8 with RedDot CMS
7.5; too many things are just not clickable.

it seems like the new version 8 of Microsofts Internet Explorer doesn’t work properly with the last version (7.5) of RedDot CMS Open Texts Web Solutions Suite.

The results might depend on the specific RedDot version. Testing with a Open Text Web Solution Server caused no errors so far and seemed ok. But still, there is no official support by Open Text.

What are your experiences with Internet Explorer 8 and your RedDot CMS or (Open Text Web Solutions Server)?
If you have any insights about a new hotfix release or how your project/server works with the new IE, feel free to comment.

Share and Enjoy:
  • Print
  • email
  • Twitter
  • Digg
  • Reddit
  • StumbleUpon
  • Google Bookmarks
  • del.icio.us
  • MisterWong
  • Facebook
  • LinkedIn

No related posts.

About the author:

Markus Giesen Markus Giesen is a Solutions Architect and RedDot CMS Consultant, formerly based in Germany. Travelling around the world to find and offer solutions for a better world (in a very web based meaning). He just found a way to do this as part of a Melbourne based online consultant house. On this blog Markus shares his personal (not his employers) thoughts and opinions on CMS and web development. In his spare time you will find him reading, snowboarding or travelling. Also, you should follow him on Twitter!


6 comments for “RedDot CMS at the moment not compatible with Internet Explorer 8?”

  1. Maybe it works (better) using IE8 compatibility mode. RedDot’s HTML/JS code is FAR away from being W3C standards compliant.

    Our initial thinking for IE8 involved showing pages requesting “Standards” mode in an IE7’s “Standards” mode, and requiring developers to ask for IE8’s actual “Standards” mode separately. We made this decision, informed by discussions with some leading web experts, with compatibility at the top of mind.

    In light of the Interoperability Principles, as well as feedback from the community, we’re choosing differently. Now, IE8 will show pages requesting “Standards” mode in IE8’s Standards mode. Developers who want their pages shown using IE8’s “IE7 Standards mode” will need to request that explicitly (using the http header/meta tag approach described here).


    Posted by Frederic Hemberger | March 25, 2009, 9:21 am
  2. This wouldn’t be the first time that Opentext shit doesn’t work in standard browsers. We weren’t allowed to install Vista at work for two years while we waited for them to fix their shit.

    Posted by Frank | March 27, 2009, 3:50 pm
  3. Further testing with IE8 and the new version was ok, so I think they did a good job concerning Internet Explorer 8.
    And avoiding Vista for 2 years, that’s something to appreciate in my opinion.. ;)
    No, seriously, I think it’s not too bad with the version 9. But still, a hotfix for all the users with lower versions is definitely necessary!.

    Posted by Markus Giesen | March 28, 2009, 5:01 am
  4. We’re running Build

    I put IE8 in compatibility mode for the domain and aside from one or two buttons being a little stubborn to click on, have not had any issues at all.

    Posted by RedDolt | April 1, 2009, 6:21 pm
  5. There is definitely an issue with IE8 an the NavigationManager. You can’t open the Contextmenu in “Normal Mode”.

    Seriously, will you teach all your editors to switch to “Comatibility View” just for RedDot/OpenText? It’s hard enough to explain why they shouldn’t use Firefox (no TranslationEditor, no Drag’n'Drop in NavigationManager…).

    Its up to OpenText to fix that.

    According to the OpenText-Support you’ll have to wait for version 10, !perhaps! there will be a hotfix for version 9, but definitely none for lower versions.

    Meanwhile, you could try this at own risk (of losing support).
    Add to the HTML-Header in
    \CMS\ASP\Navigation\FormType0003.aspx this line:

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

    Posted by Michael | April 21, 2009, 8:49 am
  6. Doesn’t AD policy allow the ability to push out a list of web pages that need to be set in compatibility mode for ie8? i assume if an organisation is large enough to warrant a automated deployment of ie8 surely the policy could be pushed out as well (and i assume more than cms would be broken by ie8)?.. or alternately for smaller organisations with adhoc ie8 installs you could simply email around a .reg file to the user effected (if the have priveledges to install ie8 themselves then they should be able to load up a reg file)

    Posted by Morgan Ritchings | April 22, 2009, 6:41 am

Post a comment

Stay up to date! - Get notified about followup comments

If you don't feel the urge to comment but wish to stay in the loop:
Just enter your email and subscribe to new comments.

Subscribe without commenting

Recent Tweets

  • RT @AirKraft: Transport Canada breakout: they manage 80K pages and 300K assets with WSM(RedDot). Wow! #OTCW 2010-11-11
  • The RedDot usergroup session 'Future of WCM' is in National Harbor 7, now. See you there! #otcw 2010-11-11
  • RT @yttergren: @AirKraft: Calling all WSM(RedDot) devs: share your solutions on http://bit.ly/bgPIof EVERY solution can win an iPad #OTCW 2010-11-10
  • Come to the Solution Exchange session. Enhance your (#reddot) CMS project! Chesapeake 12, 3:20pm #otcw Looking forward to see you there! 2010-11-10
  • More updates...