IE 8 vs. RedDot CMS

[java...@gmail.com]

Dotters--

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 is slightly better but still pretty much incapacitating when using
IE 8 to access CMS 9. Many things not functioning and some buttons can
only be clicked once; the second time around they are just dead.

I have not looked into the root cause for this; further, I am not even
well-informed on this: does RedDot have some kind of announcement/
guideline/document on this subject?

I've had users in the past asking me why FF or Safari do not work well
with RedDot CMS; I am pretty sure soon someone will ask me why the
only "kosher" browser does not even work well.

Anyone of you guru's out there has more insight? Am I the only one who
is not aware of an IE 8 hotfix for RedDot CMS? Or has someone in
RedDot come up with some workaround yet?

I remember when IE 7 came out and QuickBooks 2004 was completely
crippled and Intuit warned their users not to upgrade or else
QuickBooks would die on their PC. I've also come across with
organizations who forbid their employees to use any browsers other
than IE 6 simply because they are on older versions of SAP ...

From what I can see, the challenge from IE 8 to RedDot CMS is at least
at par, if not larger, than the aforementioned scenarios.

Henry Lu

[frederic....@reddotusergroup.de]

Hi Henry,

have you tried the IE8 compatibility mode yet?
RedDot's HTML/JS code is FAR away from being W3C standards compliant.

Frederic

[Henry Lu a.k.a. Javahand]

I shall. And thanks!

[Nick Galotti]

I started using IE8 yesterday and was only able to use SmartEdit. Once
I switched to compatibility mode I was able to use SmartTree and
Server Manager and haven't had a problem so far. That isn't to say
there isn't any problems I just haven't found one.
-Nick

On Mar 25, 7:19 am, "Henry Lu a.k.a. Javahand" <javah...@gmail.com>
wrote:
> I shall. And thanks!

[Henry Lu a.k.a. Javahand]

Nick--

IE 8 on CMS 9 brings out SmartTree and Server Manager but once you get into the details -- template editing for example -- the javascript-driven user interface is very buggy.

IE 8 on CMS 7.5 goes just as you described.

Of course, these all applies to "normal" mode.

Henry Lu

[Nick Galotti]

Thanks for the extra info. I forgot to mention that we are using CMS
7.5.
-Nick

On Mar 25, 8:24 am, "Henry Lu a.k.a. Javahand" <javah...@gmail.com>
wrote:

> Nick--
>
> IE 8 on CMS 9 brings out SmartTree and Server Manager but once you get into
> the details -- template editing for example -- the javascript-driven user
> interface is very buggy.
>
> IE 8 on CMS 7.5 goes just as you described.
>
> Of course, these all applies to "normal" mode.
>
> Henry Lu
>

[markus giesen]

- WinXP SP2
- IE8 default mode
- RedDot 9.0.0.31
Telerik editor works fine, what about that that with your servers?

[markus giesen]

With the above version I was also able to use the Template editor
without any differences to IE7 (that means Ctrl+Z might still annoy
us..)

On Mar 26, 2:55 am, Nick Galotti <ngalo...@gmail.com> wrote:

[Henry Lu a.k.a. Javahand]

First try with IE 8 compatibility mode on a Vista visiting CMS 7.5 Server.

I was able to access Server Manager and SmartTree. Once I started editing a template, the issue with placeholder buttons (creating a placeholder, deleting one or modifying one.) recurred. I was not able to access the button again if it was clicked once before.

I will try it on CMS 9 when I get a chance.

[Timo Zimmermann]

Have a look to the website from microsoft. I just enabled the
EmulateIE7-Modus directly on the IIS which is used by Reddot CMS.

http://msdn.microsoft.com/en-gb/library/cc817572.aspx

Implementing the META Switch on IIS
Windows Internet Explorer 8 introduces document compatibility modes
that allow Web developers to tell the browser to render their pages in
the same way as older versions would. The compatibility mode can be
specified on a per-page or per-site basis.
This document describes how to implement a very common document
compatibility mode, EmulateIE7, supported by Windows Internet Explorer
8, on a per-site basis, using custom headers in Internet Information
Services (IIS).