[SOLVED] Javascript errors in Admin Console after upgrade

[albanach]

Running on Ubuntu 6.4 LTS 32bit

We previously had the network edition and upgraded to v6.

Thereafter we migrated successfully to the open source edition, 6.0.4

Due to a missing preferences option in 6.0.4 we upgraded today to 6.0.6

Thereafter I could no longer edit any user account as a result of a javascript error.

I then upgraded to 6.0.7 GA and have the same problem.

The error is:

JavaScript error encountered in method 
ZaAccountViewController.prototype._setView message: this._view is 
undefined fileName: https://zimbra.example.com:7071/zimbraAdmin
/js/Admin_all.js.zgz?v=100611004005 lineNumber: 10771 stack: ([object 
Object],true,(void 0))@https://zimbra.example.com:7071/zimbraAdmin
/js/Admin_all.js.zgz?v=100611004005:10771 ([object Object],true,(void 
0))@https://zimb...

If I try and edit a COS I get this error:

JavaScript error encountered in method 
ZaCosController.prototype._setView message: com_zimbra_delegatedadmin is 
not defined fileName: https://zimbra.example.com:7071/service/zimlet
/res/Zimlets-nodev_all.js.zgz.js?v=100611004005 lineNumber: 4826 stack: 
([object Object],[object Object])@https://zimbra.example.com:7071/service
/zimlet/res/Zimlets-nodev_all.js.zgz.js?v=100611004005:48...

Essentially I can no longer adminsiter the server from the Admin console.

Any suggestions?

[albanach]

Update

This was solved with:

/opt/zimbra/bin/zmzimletctl undeploy com_zimbra_delegatedadmin

followed by a zimbra restart and cache clearing on the browser.

Looks like there's an issue though, since we had been running a GA release without problem before. Hopefully this can be fixed so future GA releases don't bork for previous NE customers.

[phoenix]

Originally Posted by albanach

Update

This was solved with:

/opt/zimbra/bin/zmzimletctl undeploy com_zimbra_delegatedadmin

followed by a zimbra restart and cache clearing on the browser.

Looks like there's an issue though, since we had been running a GA release without problem before. Hopefully this can be fixed so future GA releases don't bork for previous NE customers.

You'll need to file a bug report for that please.