Project

General

Profile

Actions

Bug #24469

closed

Adminpanel throws an JS-error : Typo3AdminPanel is not a constructor

Added by Björn Pedersen almost 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2011-01-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The error causes the workspace-splitview to become rather short in height (see http://forge.typo3.org/issues/11539)

(issue imported from #M16909)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #11539: Split viewClosedSteffen Kamper2010-12-17

Actions
Actions #1

Updated by Jeff Segars almost 14 years ago

Thanks for the bug report! Are there any specific steps for duplicating this issue? Does the Javascript error occur all the time and in all browsers for you?

Actions #2

Updated by Björn Pedersen almost 14 years ago

The problem seems to occur sporadic, but I will investigate it further.

Actions #3

Updated by Jeff Segars almost 14 years ago

I've finally found a way to duplicate this...ironically enough, its using the wec_devo extension (from my company).

The extension inserts a ton of JS directly into the page and "</head>" is part of the JS that is inserted. This causes the header insertion in index_ts.php to fail.

$TSFE->content = str_ireplace('</head>', $BE_USER->adminPanel->getAdminPanelHeaderData() . '</head>', $TSFE->content);

Actions #4

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Accepted to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?

Actions #5

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF