"Open in a separate window" Fails to Load After 6.0.6 Upgrade

[jfiore]

We upgraded to ZCS 6.0.6 NE yesterday and everything seems to have gone very well except we have not been able to use the "Open in a separate window" option in the web client since the upgrade. A new window does open but the message does not show. The new window says "Loading...."

When double-clicking a message to launch in a new window/tab, we receive the following JS error.

Error: ZmContact is not defined
Source File: https://servername/service/zimlet/co...=en&country=US
Line: 141

Is anyone else having this problem? Any ideas on what we can do to fix this? Thank you.

James

[guarana]

We're experiencing the same thing, but only on some accounts, not all. The open in new window works for some.

[king0770]

It's a bug. https://bugzilla.zimbra.com/show_bug.cgi?id=45852

Workaround

1) Edit /opt/zimbra/zimlets-deployed/com_zimbra_email/email.js

2) Go to line 29, and add the following *under* line 29

AjxDispatcher.require(["ContactsCore", "Contacts"]);


OLD
===

Com_Zimbra_Email.prototype.init =
function() {
if (appCtxt.get(ZmSetting.CONTACTS_ENABLED)) {
this._composeTooltipHint = ZmMsg.leftClickComposeHint + "
" + ZmMsg.rightClickHint;
this._newTooltipHint = ZmMsg.leftClickNewContactHint + "
" + ZmMsg.rightClickHint;


New
===

Com_Zimbra_Email.prototype.init =
function() {
if (appCtxt.get(ZmSetting.CONTACTS_ENABLED)) {
AjxDispatcher.require(["ContactsCore", "Contacts"]);
this._composeTooltipHint = ZmMsg.leftClickComposeHint + "
" + ZmMsg.rightClickHint;
this._newTooltipHint = ZmMsg.leftClickNewContactHint + "
" + ZmMsg.rightClickHint;


After the edit run the following flush cache commands:

zmprov fc zimlet com_zimbra_email

zmprov fc config

zmprov fc server `zmhostname`

[guarana]

Thanks, that worked.

[jfiore]

Yes, works beautifully. Thank you.

[mrobertson]

I downloaded the 6.0.6 update on May 2, 2010. The code bug addressed on April 16 is still not been added to the download. Is it common to not fix the downloads after a bug is addressed?

Mike

[phoenix]

I downloaded the 6.0.6 update on May 2, 2010. The code bug addressed on April 16 is still not been added to the download. Is it common to not fix the downloads after a bug is addressed?

If you're talking about the bug mentioned in post #3 above then it was not scheduled for the 6.0.6 release, you can check for which version it's targeted by looking at the Product Portal - you can also check the bug report, the give away is what version the fix was verified on.