Bug #20172
closedSwitching modules impossible due to JS error
0%
Description
The latest alpha2 still suffers from an error which makes me unable to use the TYPO3 backend both with Firefox 3 and Opera 9.x. Opera says:
JavaScript - http://noctus.net/typo3/backend.php
Event thread: click
Error:
name: TypeError
message: Statement on line 1: Type mismatch (usually non-object value supplied where object required)
Backtrace:
Line 1 of function script
top.goToModule('web_list');this.blur();return false;
...
stacktrace: ...
Firefox agrees:
Error: top.goToModule is not a function
Source File: http://noctus.net/typo3/backend.php#
Line: 1
(issue imported from #M10675)
Updated by Christian Kuhn over 15 years ago
Unable to reproduce here. Is your mentioned php version 4.3 correct?
Updated by Oliver Hader over 15 years ago
Cannot reproduce in Opera or Firefox on Mac OS X.
Please install the FireBug extension for Firefox and report a more detailed error description so that we can track down whether this is a bug. Thanks in advance!
Updated by Anonymous over 15 years ago
@Christian
Sorry about the PHP version, it's actually version 5.2.6.
@Oliver
Can you give me some hints how to get a more detailled info using Firebug? I've never used this extension before.
Updated by Oliver Hader over 15 years ago
Just install Firebug, enable it and see what errors are displayed.
You can copy the error message (pointing out also a backtrace and line numbers in files) and paste it here.
More information about that can be found here:
http://getfirebug.com/errors.html
Updated by Anonymous over 15 years ago
There isn't that much more info though:
top.goToModule is not a function
onclick(click clientX=44, clientY=85)9KtEvjDE...qow%3D%3D (Linie 2)
top.goToModule("web_txtemplavoilaM1");
Updated by Oliver Hader over 15 years ago
Well, there is... did you try it running without Templavoila?
Please try it again on a clean TYPO3 4.3 with not third party extensions installed.
Updated by Anonymous over 15 years ago
I think the problem comes down to everything not accessible declared via "var $name = $content" instead of making it globally available.
For example turning "var goToModule = function(...) {...}" into "function goToModule(...) {...}" within typo3/classes/class.modulemenu.php makes top.goToModule accessible. But then accessing top.TS will fail after that. But it should be fixable this way.
I'll try what Oliver suggested as soon as I find time for that.
Updated by Christian Kuhn over 15 years ago
Maybe this is related to #20526 ? Clearing caches (browser and typo3) helped ...
Updated by Anonymous over 15 years ago
The issue occurred due to XCLASS’ing of the tm_shared_lib extension. After disabling all of this extensions options, the backend started to work again.
You can close this issue now.