Issue with FF3 + ZCS 4.5.11 admin page?

[SSS]

I just upgraded to Firefox 3 and now the Zimbra admin login page doesn't load properly. Anyone else getting this?

The normal user login screen loads ok, but the admin screen just loads the background colour and that's it.

Page loads ok in Internet Explorer and in FF2. I've tried it on another PC with FF3 loaded and it still doesn't load properly.

Any ideas?

[mmorse]

Are you still 4.5.10 as reported by your profile version? (I see another post where your talking about possibly upgrading to 4.5.11) There have been bugs on this, that couldn't be reproduced on current builds.
-However there's no more 4.5.x builds planned except for absolutely critical security issues, so I'm not sure there's much we can suggest besides looking into a 5.0.x series upgrade (current is 5.0.6).

[SSS]

Yeah I'm on 4.5.11 need to update my profile.
Was looking into going to 5 at some stage anyway, just a case of having the time to do it.

Until then, was hoping there was a fix or something for it.

[parixit]

I also have the same issue. I am using firefox 3 and the admin page just loads the background color.

I am also running 4.5.10

Any ideas?

[dljordaneku]

I am running 4.5.7 and have the same issue. We are going to upgrade to the latest version in the near future but have several projects we are working on and haven't had a chance yet. I really don't want to use IE to do any of my admin stuff so any idea on how to fix this would be great.

Thanks.

dj

[ssatre]

Same issue here... I suppose it's a good thing that today is upgrade day for me.

*crosses fingers and jumps in*

[richard-hdd]

We are running "Release 4.5.10_GA_1575.RHEL4_20071117152457 CentOS4 FOSS edition" and after upgrading to Firefox 3.0 and noticed that the admin page doesn't load either. It looks like there is some kind of JavaScript error that is causing the page to not load correctly:

Error: resp.GetVersionInfoResponse is undefined
Source File: https://mail.hddbroker.com:7071/zimb...v=071117154042
Line: 10737

Unfortunately the work around for me is using IE7. We are too going to upgrade in the near future to 5.x but that isn't going to be for another month or so.