Red Dot Management Server and IE9 incompatibility

[Chrzanowski, Romola]

Does Red Dot Management Server 10.1 Build 10.1.2.310 support Internet Explorer 9? I received a confusing answer from Open Text support, so will appreciate other comments. My client PC is Windows 7, and when upgraded to IE9 the Server Manager interface was broken (missing and/or grayed out content).

 

Has anyone found IE9 to work with RedDot 10.1? And, does anyone know if Release 11 is likely to offer improved support of browsers other than IE8 and lower?

 

Thanks for any opinions or information.

 

Romola Chrzanowski

University Applications Development

University at Albany

518.437.4525

 

[Evandro Moreno]

Romola,

All you need to do is to turn on compatibility view in IE. We run the same cms version as you and I have been using IE 8, 9, and 10 without problems.

Best,

Evandro Moreno

[Ibrahim Sawadogo]

Hi, reddot does not support ie9
Including ver. 11. I have tested it.

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

[Ibrahim Sawadogo]

The best browser for reddot is ie8.

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/nPc_D67CjoEJ.

[Tony Chung]

On Tue, Apr 17, 2012 at 1:57 PM, Ibrahim Sawadogo <ichi...@gmail.com> wrote:
> The best browser for reddot is ie8.
>

I find it curious that the reddot/OpenText CMS deliberately limits the
compatibility of the administration interface to such antiquated
browsers. I don't see how much of a part ActiveX plays in Smart Tree,
for example, or whether those features would be missed if they were
replaced by something coded in pure JavaScript.

-Tony

[Craig Plummer]

I think it was just poorly coded in the first place, I don't think there is anything that would require IE for it to work. I don't think it makes use of Active X as I have never been asked to install any components. It just wasn't written in a standards compliant way, which is likely why it doesn't work in IE9 unless you turn on compatibility mode.

It gets asked in almost every webinar when it will work with other browsers, but an excuse is always made. I think the latest was they would rewrite it to work in all browsers after IE10 is released, but considering that IE9 has been out a year and was in beta for about 6 months before that and OpenText still don't fully support it I think it is unlikely it will ever change.

Craig

[Richard Hauer]

Hi Craig,

 

There are certainly elements of SmartEdit that utilise ActiveX components including the Word editor integration, inline editing and drag and drop functions.  Remember that this interface was built when IE6 was the browser king with over 90% utilisation.  It also delivered a number of JavaScript enhancements over rival browsers of the day (hence its popularity at the time) but, as there were few properly established standards, Microsoft took a number of liberties in attempting to influence the overall direction of JavaScript; many of these did not stick.

 

SmartTree uses JavaScript that works in IE8 because of its legacy support for the not very modern JavaScript constructs used heavily by RedDot, but as Microsoft succumbed to industry pressure to drop support for vendor-specific ‘enhancements’ in favour of supporting ECMA standards-compliant behaviour in IE9 much of the UI because a bit broken.

 

I think OT have found it difficult to justify the cost that a ground-up rebuild of the SmartEdit and SmartTree UI would involve as IE8 is still very widely adopted and supported, but as time goes on this is less and less the case.

 

V11 presents a ground-up rebuild of the back-end technology stack for the ‘RedDot’ products and I think it’s reasonable that the front-end will receive similar treatment in the not too distant future (I have it on good authority actually).

 

Note that under MS policy, once IE10 is released support for IE7 will be stopped and IE8 becomes end-of-life, making it inevitable that organisations upgrade their browsers.  It’s impossible that OT don’t update their browser support at that time or they face the likelihood of being impossible to implement.

 

Rgds,

Richard.

--

You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/sqdt7cHTQSEJ.

[Craig Plummer]

Hi Richard,

Thanks for the response, I didn't realise there was ActiveX used as we disabled those features in our setup.

I think my personal feeling is that OpenText are slow to keep up with the latest developments in technology, I know they are trying to make things better now but they have a hell of a lot of catching up to do. As our team are moving more over towards Macs as our development, as it is a better platform for us for the non CMS development work we do it is frustrating to have to boot a VM just to edit some settings in the CMS. Especially when we work hard to make sure all our custom built applications work across all platforms.

The poor communication from OpenText about this issue hasn't helped either, with them saying IE9 support is coming in a particular update and then it not materialising with no explanation.

Regards,
Craig

To post to this group, send email to reddot-cms-users@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-users+unsubscribe@googlegroups.com.

[Richard Hauer]

I would have to agree on the visibility thing.

 

Though not a Mac person myself, I can see how your setup could become annoying quickly.  Can the Google Chrome “IE Tab” extension be run on a Mac? Seems like probably not, depending on how they’ve done it.  Worth a look though.

 

I’d suggest a Chrome/Firefox compatible version isn’t too far away...

 

Richard.

 

 

From: reddot-c...@googlegroups.com [mailto:reddot-c...@googlegroups.com] On Behalf Of Craig Plummer
Sent: Thursday, 19 April 2012 12:26 AM
To: reddot-c...@googlegroups.com
Subject: Re: Red Dot Management Server and IE9 incompatibility

 

Hi Richard,

Thanks for the response, I didn't realise there was ActiveX used as we disabled those features in our setup.

I think my personal feeling is that OpenText are slow to keep up with the latest developments in technology, I know they are trying to make things better now but they have a hell of a lot of catching up to do. As our team are moving more over towards Macs as our development, as it is a better platform for us for the non CMS development work we do it is frustrating to have to boot a VM just to edit some settings in the CMS. Especially when we work hard to make sure all our custom built applications work across all platforms.

The poor communication from OpenText about this issue hasn't helped either, with them saying IE9 support is coming in a particular update and then it not materialising with no explanation.

Regards,
Craig

On Wednesday, 18 April 2012 14:44:39 UTC+1, Richard Hauer (5 Limes) wrote:

Hi Craig,

 

There are certainly elements of SmartEdit that utilise ActiveX components including the Word editor integration, inline editing and drag and drop functions.  Remember that this interface was built when IE6 was the browser king with over 90% utilisation.  It also delivered a number of JavaScript enhancements over rival browsers of the day (hence its popularity at the time) but, as there were few properly established standards, Microsoft took a number of liberties in attempting to influence the overall direction of JavaScript; many of these did not stick.

 

SmartTree uses JavaScript that works in IE8 because of its legacy support for the not very modern JavaScript constructs used heavily by RedDot, but as Microsoft succumbed to industry pressure to drop support for vendor-specific ‘enhancements’ in favour of supporting ECMA standards-compliant behaviour in IE9 much of the UI because a bit broken.

 

I think OT have found it difficult to justify the cost that a ground-up rebuild of the SmartEdit and SmartTree UI would involve as IE8 is still very widely adopted and supported, but as time goes on this is less and less the case.

 

V11 presents a ground-up rebuild of the back-end technology stack for the ‘RedDot’ products and I think it’s reasonable that the front-end will receive similar treatment in the not too distant future (I have it on good authority actually).

 

Note that under MS policy, once IE10 is released support for IE7 will be stopped and IE8 becomes end-of-life, making it inevitable that organisations upgrade their browsers.  It’s impossible that OT don’t update their browser support at that time or they face the likelihood of being impossible to implement.

 

Rgds,

Richard.

 

From: reddot-c...@googlegroups.com [mailto:reddot-c...@googlegroups.com] On Behalf Of Craig Plummer
Sent: Wednesday, 18 April 2012 9:11 PM
To: reddot-c...@googlegroups.com
Subject: Re: Red Dot Management Server and IE9 incompatibility

 

I think it was just poorly coded in the first place, I don't think there is anything that would require IE for it to work. I don't think it makes use of Active X as I have never been asked to install any components. It just wasn't written in a standards compliant way, which is likely why it doesn't work in IE9 unless you turn on compatibility mode.

It gets asked in almost every webinar when it will work with other browsers, but an excuse is always made. I think the latest was they would rewrite it to work in all browsers after IE10 is released, but considering that IE9 has been out a year and was in beta for about 6 months before that and OpenText still don't fully support it I think it is unlikely it will ever change.

Craig

On Tuesday, 17 April 2012 22:19:47 UTC+1, Tony Chung wrote:

On Tue, Apr 17, 2012 at 1:57 PM, Ibrahim Sawadogo <ichi...@gmail.com> wrote:
> The best browser for reddot is ie8.
>

I find it curious that the reddot/OpenText CMS deliberately limits the
compatibility of the administration interface to such antiquated
browsers. I don't see how much of a part ActiveX plays in Smart Tree,
for example, or whether those features would be missed if they were
replaced by something coded in pure JavaScript.

-Tony

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/sqdt7cHTQSEJ.

To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

--

You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/n1mYjREbVM8J.
To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.

[Craig Plummer]

Unfortunately you can't use the IE Tab on a Mac, it uses the IE rendering engine installed on a machine and just displays it within a different browser. So as there is no IE rendering engine on a Mac it doesn't work.

Lets hope a Firefox / Chrome compatible version is released soon, although at the moment we are waiting for Oracle support to return so we can even upgrade to v11.

To post to this group, send email to reddot-cms-users@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-users+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/n1mYjREbVM8J.

To post to this group, send email to reddot-cms-users@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-users+unsubscribe@googlegroups.com.

[Tony Chung]

On 2012-04-18, at 8:30 AM, Richard Hauer <richar...@gmail.com> wrote:

Can the Google Chrome “IE Tab” extension be run on a Mac? Seems like probably not, depending on how they’ve done it.  Worth a look though.

For the IE tab to work, the system must be running IE. That is to say, not on a Mac.

I’d suggest a Chrome/Firefox compatible version isn’t too far away...

I'd hope so. OT excuse that a ground up standards compliant SmartTree rebuild is not cost effective is unreasonable, considering the cost of supporting the software.

What is  this "Word integration" you spoke of? As far as I can see, we have the RADeditor or the no editor.

At least if I edit my pages in Firefox I can have a real time spell checker (provided by Firefox). But due to being in large scale setup mode, we prefer to work in SmartTree, which is not Firefox compatible.

I would argue that using compliant standards with modern UI and data handling libraries would go a long way to OT growing user adoption and satisfaction.

That's just my opinion and not that of my company.

Cheers,

-Tony

[Joel Kinzel]

Richard, don't toy with my heart! An OTMS that is cross-browser?! I might actually cry if that comes true. 

Tony:

What is  this "Word integration" you spoke of? As far as I can see, we have the RADeditor or the no editor. 

I believe this option is in the General Settings (under Admin Proj. Settings).

I would argue that using compliant standards with modern UI and data handling libraries would go a long way to OT growing user adoption and satisfaction. 

I would second this, and actually take it a step further by saying that building something that is standards compliant is MORE cost effective than maintaining something that is not. Extensible design is a huge factor for many organizations now, and OT seems behind the curve (in my opinion) on this. 

[Dmitry Terner]

The continued failure to update the product into something recognizably modern is what is forcing us to consider our options in moving away from OWS. The roadmap slides I saw circulated a while ago are not encouraging.

[Tim D]

If you haven't yet and this is a priority for you and your organization please vote and comment on SolutionExchange for this and other feature ideas.

 

http://www.solutionexchange.info/idea/1.24.2371