Tridion 2011 SP1 : Tridion GUI Javascript error with Translation Manager and Powertools 2011 installed

Question

I recently installed Tridion 2011 SP1 with SDL module Translation Manager enabled.

Everything was working fine. Then I installed the Tridion 2011 Powertools, following the installation procedure.

When trying to reload the GUI (browser cache emptied and modification parameter instanciated for server element in WebRoot\Configuration\System.Config) I'm getting the following Javascript error :

SCRIPT5007: Unable to get value of the property 'getItemType': object is null or undefined
Dashboard_v6.1.0.55920.18_.aspx?mode=js, line 528 character 851

And here is the concerned JS line:

Tridion.TranslationManager.Commands.Save.prototype._isAvailable=function(c,a){var
e=c.getItem(0),f=$models.getItem(e),b=f.getItemType(),d=$models.getItem(this.getTmUri ())

The preceding Javascript lines are dealing with other TranslationManager commands, so I suppose it is a kind of TranslationManager commands registration or somehting.

Trying to browse my Tridion publications by selecting any folder/strucutreGroup will also give the same error and the right frame (content frame) will not display any Tridion items but simply display:

Loading ...

Has anyone already experienced similar issue ?

For now I have no other choice than commenting out the Powertools sections file

Tridion_Home\web\WebUI\WebRoot\Configuration\System.Config

Thank you, François

Answer 1

Strange thing here is that it refers to Save command which is not intended to be called or used from Dashboard.

I`d suggest to disable JS minification (JScriptMinifier filter in System.config), as it will probably show more correct details.

Another useful thing would be this error call stack.

--

I was not able to reproduce an issue from initial question, but had following error when I installed PT:

PowerTools is not defined

which appears in *\PowerTools\Editor\PowerTools\Client\Shared\Scripts\ProgressDialog\ProgressDialog.js where it tries to register PowerToolsBase namespace, instead of PowerTools.

I`ll be surprised if adding

Type.registerNamespace("PowerTools");

at the top of the file will fix a problem, as in my case it was breaking entire GUI no matter if TM included or no.