Bug #18752: Error Tree not defined and Prototype not defined in Pagetree - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #18752

closed

Error Tree not defined and Prototype not defined in Pagetree

Added by Markus Koch almost 16 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Oliver Hader

Category:

Target version:

Start date:

2008-05-06

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.2

PHP Version:

5.2

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

With FF 2.0.0.14 and IE 7 on Vista SP1 i get always the following errors:
1.) Tree is not defined (Row 29)
2.) DragDrop is not defined (Row 51)
3.) Prototype is not defined (Row 66)
4.) Tree is not defined (Row 230)
The Error occured alwas in Module in "typo3/alt_db_navframe.php?&currentSubScript=db_list.php".
I can't get the contextmenu of a tree item and expanding the entries is unpossible.

I use PHP 5.2.3, MySql 5.0.41, Apache 2.0.59, FreeBSD 6.2
(issue imported from #M8337)

Actions

Copy link

Updated by Stefan almost 16 years ago

Hi there,
had the same errors.
try to update PMK Textarea Widget - pmktextarea to current version (http://typo3.org/extensions/repository/view/pmktextarea/0.3.0/)

This solved my problems.

Actions

Copy link

Updated by Oliver Hader almost 16 years ago

Hm, could not reproduce this on a clean 4.2 installation.
But if an XCLASS overwrites some core methods (like e.g. the mentioned extension does), it might lead to a similar behaviour you mentioned.

Thus, you should addtionally check the XCLASS environment on your system...

Actions

Copy link

Updated by Stefan almost 16 years ago

I repeated the following steps and reproduced the errors:

1. "normal" installation of typo3 4.1.2
2. before updateing to 4.2.0: creating symlinks
3. installing 4.2.0
4. changing symlinks
5. login to new backend
6. errors occured
7. updating pmktextarea from version 0.2.0 to 0.3.0
8. errors gone

Hope it helps in my case.

Note: Of course i deleted all cached files (typo3 and browser) after step 4.

Actions

Copy link

Updated by Guido Lauermann almost 15 years ago

Hi,
i had the same errors.

I updated from version 4.1.5.
In 4.1.5 there was a Firefox bug and i needet the extension mn_ff3_be_bugfix.
This extension used XCLASS, and these extensions can produce some problems.

After deinstall mn_ff3_be_bugfix this problem was fixed.

Look also in your Configuration->$TYPO3_CONF_VARS->BE->XCLASS for other extensions, that used XCLASS.

cooper

Actions

Copy link