Project

General

Profile

Actions

Bug #16868

closed

each is not defined

Added by Christian Welzel about 17 years ago. Updated almost 16 years ago.

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

0%

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

Description

when using the current rtehtmlarea from ter (1.4.3) with firefox 2 on linux or firefox 1.5.0.9 on windows i get an "editor is being loaded. please wait..." and nothing more happens.
The JS Console shows the following error:

Error: each is not defined
Source File: http://localhost/typo3temp/rtehtmlarea_htmlarea_3020582421d8df37a2ff5eca0c7187e2-compressed.js
Line: 1

I use Typo3 4.1 from svn.

(issue imported from #M4810)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #16692: htmlArea RTE conflicts on using prototyped Array objects (e.g. Prototype JavaScript framework)ClosedKarsten Dambekalns2006-11-06

Actions
Related to TYPO3 Core - Bug #16939: Rich text editor not loadingClosedOliver Hader2007-02-04

Actions
Actions #1

Updated by Oliver Hader about 17 years ago

In TYPO3 4.1 the javascript frameworks prototype and script.aculo.us are used. The RTEhtmlarea in TYPO3 4.1 is changed to handle this.
The problem is faulty javascript programming in RTEhtmlarea, that uses the element "Array" as "Object" like this:

for (var i in someArray) { ... }

The mentioned "each" is a prototype to the Array element by prototype.js.
Thus the problem only exists in the TER version of RTEhtmlarea.

Actions #2

Updated by Michael Stucki about 17 years ago

Can you reproduce this if you turn compressed javascripts off (must be changed in the EM settings for rtehtmlarea)?

- michael

Actions #3

Updated by Michael Stucki about 17 years ago

Ah, I didn't see yet that Oliver already knows where the problem relies... All fine!

Actions #4

Updated by Oliver Hader about 17 years ago

I'll get in touch with RTEhtmlarea maintainer for the TER version and try to bring both versions (core & TER) to a common state.

Actions #5

Updated by Christian Welzel about 17 years ago

thanks for the hint.
after deletion of the ter version and installation of the version in b2 the editor is working again.

Actions #6

Updated by Oliver Hader about 17 years ago

It seems that the TER version is a copy of the latest release in stable branch (4.0.4). But prototype.js is part of the current unstable branch (4.1.x).

So, if 4.1 is released as stable (mid of February 2007), the TER version should also be updated. The core version is always the most recent one and contains all fixes.

Actions #7

Updated by Oliver Hader almost 17 years ago

Version conflicts. No bug at all.

Actions

Also available in: Atom PDF