It's not a bug, it's a missing feature. bugs.TYPO3.org

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0005266 [tx_rtehtmlarea] block always 21.03.07 08:18 27.06.08 10:49
Reporter Stefano Cecere View Status public  
Assigned To Patrick Broens
Priority high Resolution fixed  
Status closed  
Summary 0005266: htmlarea doesn't load with new Firefox 2.0.0.3
Description with v1.5dev (shipped with typo3 4.1)

going back to FF 2.0.0.2 works well
Additional Information
Tags No tags attached.
Has patch
Patch is reviewed
Attached Files ? file icon T3X_rtehtmlarea-1_4_3a-z-200703251756.t3x [^] (270,117 bytes) 25.03.07 18:02
? file icon T3X_rtehtmlarea-1_4_3-z-200703261132.t3x [^] (265,847 bytes) 26.03.07 11:49
? file icon bug-5266-no-wamcom.diff [^] (154,999 bytes) 26.03.07 11:49
? file icon bug_5266.diff [^] (9,200 bytes) 26.03.07 12:16
? file icon bug_5266_4-0.diff [^] (152,008 bytes) 26.03.07 12:16
? file icon T3X_rtehtmlarea-1_5_1a-dev-z-200703271702.t3x [^] (336,754 bytes) 27.03.07 17:03
? file icon T3X_rtehtmlarea-1_1_6-z--TYPO3-3_7.t3x [^] (448,787 bytes) 28.03.07 11:00
? file icon T3X_rtehtmlarea-1_2_2-z--TYPO3-3_8.t3x [^] (387,093 bytes) 28.03.07 11:01

Sponsor -  Users sponsoring this issue
Sponsors List Total Sponsorship = EUR 80

26.03.07 19:47: Jonas D?bi (EUR 30)
27.03.07 15:07: move-elevator GmbH (Florian Wentzel) (EUR 50)

- Relationships Relation Graph ] Dependency Graph ]
related to 0004870closedPatrick Broens tx_rtehtmlarea htmlarea doesn't show up 
related to 0004238closedMichael Stucki tx_rtehtmlarea Problem in Code View in Firefox 1.5.0.7 
parent of 0005321closedOliver Hader tx_rtehtmlarea Link popup don't have scrollbar with compressed script and patch for FF2.0.0.3 (see 0005266) 
parent of 0005295closedPatrick Broens tx_rtehtmlarea rte not working with firefox2.0.0.3 
parent of 0005328closedPeter Niederlag tx_rtehtmlarea with vers1.4.4 htmlarea doesn't load in IE 7.x 
has duplicate 0005268closedOliver Hader - TYPO3 Core - javascript error firofox 2.0.0.3 
has duplicate 0005270closedOliver Hader tx_rtehtmlarea RichTextEditor doesn't work under Firefox 2.0.0.3 anymore 
has duplicate 0005277closedOliver Hader - TYPO3 Core - Problem with Rich Text Editor and Firefox 2.0.0.3 
has duplicate 0005279closedMichael Stucki tx_rtehtmlarea incorrect patch / closed issue 0005266 
has duplicate 0005280closedOliver Hader tx_rtehtmlarea RTE stopps loading with "this._undoQueue has no properties" 
has duplicate 0005376closedMichael Stucki tx_rtehtmlarea rte not working with firefox2.0.0.3 

-  Notes
(0013193)
David Zschille (reporter)
21.03.07 11:59

I checked this on three computers. All running WinXP SP2. On ervery i updated FF and FF-Portable in german and english to the current version 2.0.0.3. In every case htmlarea was not loading anymore on Typo3 4.0.5 with htmlarea 1.4.3.
(0013195)
Christian Brunner (reporter)
21.03.07 12:39

Same for me:
Vista Business
Typo3 4.1
FF 2.0.0.3
(0013196)
Michael Stucki (administrator)
21.03.07 13:16

Well, obviously it's not a TYPO3 issue since it worked with older versions of Firefox.

You can help us by reporting the problem to the Mozilla Devs.
(0013198)
Jonas D?bi (reporter)
21.03.07 13:53

We'll have to find a workaround because all users working with firefox 2 will be updated automatically.
(0013201)
Christian Hernmarck (reporter)
21.03.07 14:06

https://bugzilla.mozilla.org/show_bug.cgi?id=374738 [^]

It appeared with FF 2.0.0.3 - but it still may be a bug in HTMLArea...

/Chris
(0013207)
Alexander Grein (reporter)
21.03.07 15:23

I have the same Problem on MAC and PC.
After updating from 2.0.0.2 to 2.0.0.3 the HTMLArea do not work anymore.

I got this error javascript-error:
"editor has no properties"

In the generated rtehtmlarea_.....js file i found this definition:
var editor=RTEarea[editorNumber]["editor"];

Maybe this help's someone.
(0013211)
Stefano Cecere (reporter)
21.03.07 20:04

how i'd like to switch to TinyMCE as default RTE.... i made some experiments.. anybody using it in production?
(0013215)
Martijn (reporter)
21.03.07 21:00

This is https://bugzilla.mozilla.org/show_bug.cgi?id=374738 [^] in Mozilla's bug tracker.
If someone could make a minimal (or even unminimized, but at least one that is portable) testcase, that would be great.
(0013224)
Axel Klarmann (reporter)
22.03.07 09:04

Found a workaround with the add-on User-agent switching:

The only change one need is to replace the 1.3 in the version string, with e.g. 1.2

Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
will be
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.2) Gecko/20070309 Firefox/2.0.0.3

That goes in conjuntion with an line:
HTMLArea.is_wamcom = (HTMLArea.agt.indexOf("wamcom") != -1) || (HTMLArea.is_gecko && (HTMLArea.agt.indexOf("1.3") != -1));
in htmlarea.js on line 85

maybe that is the point where one has to start to change things
(0013226)
Stefan Precht (reporter)
22.03.07 09:52

I'm working on a TYPO3 4.0.4 installation with an htmlarea V1.4.3 using FireFox 2.0.0.3 and of course i have the same problem. Reported below. Maybe this is helpfull for somebody to find an solution to fix it!?

enableCompressedScripts is set to 0

If I empty all cashes and delete the editors js files in typo3temp too, the editor loads exactly one time. Due to this there occurs an JavaScript Error "this._undoQueue has no properties" in file htmlarea.js, function "HTMLArea.prototype._undoTakeSnapshot = function() ", line this._undoQueue[this._undoPos] = { text: txt, time: curTime };

If I load the editor a second time it hang up while loading.
Due to this there occured an other JS error.

"editor has no properties"
File: htmlarea.js
Function: HTMLArea.generatePlugins = function(editorNumber)
Line 1066: var editor = RTEarea[editorNumber]["editor"];
(0013230)
Patrick Broens (developer)
22.03.07 10:36

Solution:
RTEhtmlarea was checking if MacOS Wamcom version 1.3 was the user agent with a indexOf("1.3"). The revision number of Firefox also has 1.3 in it, because of revision number 1.8.1.3. This is now checked if version number has not indexOf(".1.3").

See the patch

Comments:
Thanks to Axel Klarmann for pointing in the right direction.

When testing delete all rtehtmlarea related files in typo3temp directory.
(0013231)
Patrick Broens (developer)
22.03.07 10:40

Changing the status to resolved.
(0013249)
Michael Stucki (administrator)
22.03.07 16:00

Reopening this bug, see user comment in bug 0005279.
 
 @Patrick: Next time please do not close bugs unless they have been successfully committed to SVN. Otherwise it's not possible for users to give feedback...
(0013250)
Axel Jindra (reporter)
22.03.07 16:02
edited on: 22.03.07 16:42

I have patched both js files without an error and the editor still won't load in FF 2.0.0.3 on Mac OS X

edit: I just tested the patch with FF 2.0.0.3 on Windows Vista and it doesn't work there either.

edit2: OK, blame on me, I did not delete the rtehtmlarea_* files in typo3temp, but due to the fact it said "When testing..." and I wasn't testing, I was serious ;-)
Now RTE works again.

(0013251)
Ruben Theerkorn (reporter)
22.03.07 16:06
edited on: 22.03.07 16:17

i patched too, and it won't work - thought i was the only one ;)
(Same System as Axel Jindra)

(0013253)
Staffan Ericsson (reporter)
22.03.07 16:12

When is the ter version updated? So all without shell access can update there rtehtmlarea?
(0013254)
Sascha Egerer (reporter)
22.03.07 16:18

i still have a problem after this patch, too.
Now there is an javascript error on line 954 in the htmlarea.js file

/**
 * Access an inline relational element and make it "accesible".
 * If a parent object has the style "display: none", offsetWidth & offsetHeight are '0'.
 *
 * @params object callbackFunc: A function to be called, when the embedded objects are "accessible".
 * @return object An object returned by the callbackFunc.
 * @author Oliver Hader <oh@inpublica.de>
 */
HTMLArea.prototype.accessParentElements = function(parentElements, callbackFunc) {
    var result = {};
    
    if (parentElements.length) {
        var currentElement = parentElements.pop();
        var elementStyle = document.getElementById(currentElement).style;


In the last line i get the error

The Error message is: document.getElementById(currentElement) hast no properties
(0013255)
Patrick Broens (developer)
22.03.07 16:27

For the people where the patch didn't work: Did you delete all rtehtmlarea related files in the typo3temp/ folder and clear the browser cache?
(0013256)
Ruben Theerkorn (reporter)
22.03.07 16:28

Yep, I deleted the whole temp folder to be on the safe side.
(0013257)
Sascha Egerer (reporter)
22.03.07 16:31

The RTE works in the Fullscreen Version but not inside of a content element
(0013258)
Bruno (reporter)
22.03.07 16:33

Don't forget after patching to clean your typo3temp directory manually. Also clear your Browser Cache!
After that Restart your Browser and log in!

It should work fine! TYPO3 4.1 on Windows and MAC FF
(0013259)
Patrick Broens (developer)
22.03.07 16:33

In addition to bugreport 5279:

----------------------------------------------------
the patch for issue 5266 is incomplete.

the patch tries to exclude following browser identifier
[code]
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
[/code]
with this line
[code]
HTMLArea.is_wamcom = (HTMLArea.agt.indexOf("wamcom") != -1) || (HTMLArea.is_gecko && HTMLArea.agt.indexOf("1.3") != -1 && HTMLArea.agt.indexOf(".1.3") == -1);
[/code]

this condition will still won't exclude future firefox versions, example:

[code]
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.3) Gecko/20070309 Firefox/2.0.0.3
[/code]

so the same bug will reappear in about half a year.
----------------------------------------------------------------------

This is not the case. This line is excluding FF to be HTMLArea.is_wamcom. The old line made FF seen as wamcom browser version 1.3 because it was looking for the string part "1.3", but it is excluding FF now with the ".1.3" (look at the dot).

This patch keeps working when FF version is 1.9.1.3
(0013264)
Oliver Hader (administrator)
22.03.07 19:27

Concerning the "HTMLArea.prototype.accessParentElements" note (0013254):
In fact this is a bug that should be solved by another patch (mostly conerning IRRE), see bug-id 0005177. The RFC has been sent to the Core-List one week ago - currently waiting for approval.
(0013266)
alexander onea (reporter)
22.03.07 21:02

in reply to note 13195:
you're right that your patch will work with my counter-example on bug 0005279, but you're wrong assuming that your patch is correct.

check this out:
[code]
var str = "Mozilla/5.0 [...]; rv:1.3.0) Gecko[...]Firefox/2.0.0.3".toLowerCase();
var condition = str.indexOf("1.3") != -1 && str.indexOf(".1.3") == -1;
alert(condition);
[/code]
... and no, adding another condition like "str.indexOf("1.3.") == -1" to the list of identifiers would still not be the proper solution since it only solves the symptom and not the problem itself - that you shouldn't determine "is_wamcom" by checking for parts of version numbers.
(0013272)
Patrick Broens (developer)
23.03.07 09:58

in reply to note 13266:

The string "Mozilla/5.0 [...]; rv:1.3.0) Gecko[...]Firefox/2.0.0.3" is a browser based on the WamCom release of mozilla. We are not checking the version number, but the revision number. Mozilla never released revision number 1.3.0 and 1.3.1. These numbers were for the WamCom project which ended somewhere in 2004. Revision number 1.3.0 is a release from the beginning of 2003, 1.3.1 of september the same year. This project came to an end in 2004.

I don't expect Mozilla ever to release revision 1.3, 1.3.0 or 1.3.1 or whatever in this range, when they are already on revision 1.8.1.3. It's the same as M&^%* releasing a new operating system in 2008 and call it Windows 94.

I hope this clears things regarding the WamCom releases and the check on it.
(0013275)
Christian Hernmarck (reporter)
23.03.07 10:09

Wouldn't it be easier to check
 indexOf("rv:1.3.")
instead of
 indexOf("1.3") AND indexOf(".1.3")
?

/ch
(0013276)
Patrick Broens (developer)
23.03.07 10:16

in reply to note 13275:

No, sometimes a space is used between rv: and the number, sometimes it's not. And putting a dot at the end will still not see revision 1.3 as WamCom, which is.
(0013282)
Jason Lefkowitz (reporter)
23.03.07 15:52

Re: 0013255 --

I patched the file, deleted all the contents of the typo3temp/ directory, cleared my browser cache, restarted the browser & logged in again. HTMLArea still does not load. Firefox 2.0.0.3 on Windows XP Pro.
(0013283)
Jason Lefkowitz (reporter)
23.03.07 16:09

Wait - I take it back. It now appears to work. Sorry about that!
(0013285)
Jason Lefkowitz (reporter)
23.03.07 17:09

Gack. Now it doesn't work again. Weird...
(0013286)
Oliver Hader (administrator)
23.03.07 17:19

@Jason: Do you get any JavaScript errors?
(0013289)
Jason Lefkowitz (reporter)
23.03.07 18:44
edited on: 23.03.07 18:47

I did. Based on those I think I've figured out the issue. It looks like the patch successfully updated the standard htmlarea.js, but it failed to patch the compressed version. When I was getting the regular one it worked fine; when I was getting the compressed one it wasn't. I disabled the compressed version in the config file and now it seems to be stable -- at least on the site whose localconf.php I updated.

Of course I now have a bunch of other sites to fix, but that appears to be a different error -- it's throwing an "editor has no properties" error when it tries to load the RTE, for some reason...

UPDATE: clearing out all the rtehtmlarea* files in the typo3temp/ directory of the affected sites appears to resolve that latter problem.

(0013291)
Marc V?ron (reporter)
24.03.07 08:41

I used patch.exe from GNU utilities for Win32 (http://unxutils.sourceforge.net/) [^] to apply the diff file. It has patched htmlarea.js, but htmlarea-compressed.js has been rejected.

As Jason, I disabled the compressed version (using the Extension Manager ). After deleting the rtehtmlarea* files in typo3temp/ the editor now works fine.
(0013292)
Christian Hernmarck (reporter)
24.03.07 08:51

I also noticed that the patch has a problem with the compressed version - i patched the compressed js file manually and this worked.
The compressed file is only a one liner... in the patch it seems that there are more than one line...
So - we can make a patch for the "normla" file and also give the whole new compressed file as a replacement....

(to patch a one liner doesn't make sense...)

Best would be an extension update!!!

/ch
(0013293)
Christian Hernmarck (reporter)
24.03.07 08:57

reply to 0013276:
As you wrote in 0013272 the check is only to detect this WamCom version. Are there also spaces between rv: and the version numer? you wrote "1.3.0 and 1.3.1" so I didn't know there is also an "1.3 "...
When Firefox reaches rv:1.30.something we are running in another problem... or our grand childern.... :-)
(0013299)
Hans vom Schloß (reporter)
24.03.07 16:27

Th@nx a lot to all of you for solving this problem so fast!

May someone can help the following little hint:

Reading, trying and - for the first time - failing to patch i rember to look at my typo3conf-directory ... there was an another instance of rtehtmlarea.
I learned: Always patch the working instance! ... but this was maybe a typical beginners problem ;-)
(0013306)
Christian Hernmarck (reporter)
25.03.07 18:02

Since I dont' know if someone is updating the current rtehtmlarea extensions I did it for version 1.4.3 -> 1.4.3a :-)
See attached file... T3X_rtehtmlarea-1_4_3a-z-200703251756.t3x
Changed: the two htmlarea(-compressed).js, Changelog and ext_emconf.php (version & md5).

Maybe someone can put this on TER??? (I never did this ...) and create an update for 1.1.5 and 1.5...

/Christian
(0013309)
Stefan Katzer (reporter)
26.03.07 10:37

after install the patch from 25.03.07 the bug ist still present. :-(
(0013312)
Christoph Bl?mer (reporter)
26.03.07 11:17

The patch: T3X_rtehtmlarea-1_4_3a-z-200703251756.t3x

is working at my typo3 installation.

Thanks.

When will it be on TER and when ist there an update for the 1.5.1 dev Version
And what is special about the 1.1.5 Version? It shows up as the newest Version in TER.
(0013314)
Karsten Dambekalns (developer)
26.03.07 11:52

I just uploaded a patch that removes the check for WaMCom completely (no updates on that project since 2003, abandoned since 2004). The T3X file is the patched version for easy testing.

REMEMBER to clear typo3temp/* AND your browser cache!
(0013315)
Michael Stucki (administrator)
26.03.07 12:17

I replaced Patricks patch with a slightly fixed version (removed double ";;" in the compressed version).

Additionally I have uploaded a patch for TYPO3 4.0.x
(0013319)
Marcel Alburg (reporter)
26.03.07 15:39

The extensions doens't work with typo3 4.1.

Is there any patch for htmlarea 1.5-dev ?
(0013320)
Michael Stucki (administrator)
26.03.07 15:48

Oh well... For sure it does! The attached patch bug_5266.diff is for current SVN which should be equal to TYPO3 4.1.

Please check the following:

- There must be no copy in typo3conf/ext/ or typo3/ext/, otherwise the modification in typo3/sysext/ is void.

- Remove typo3temp/*.js

- Clear your browser cache.
(0013322)
Marcel Alburg (reporter)
26.03.07 20:09

With bug_5266.diff and typo 4.1 with rhtmlarea 1.5-dev it works.

Thanks
(0013323)
Lars-Erik Forsberg (reporter)
26.03.07 21:18

I was able to successfully patch rtehemlarea v1.5dev on a TYPO3 4.1 install with "bug_5266.diff" supplied above. However I have been unable to successfully patch version 1.4.3 of the RTE on a TYPO3 instance using the 4.0.4 source.

My understanding from http://bugs.typo3.org/view.php?id=4870 [^] is that both htmlarea-compressed.js and htmlarea.js need to be altered?

When I attempt to apply the diff patch bug_5266_4-0.diff to "htmlarea-compressed.js" (version 1.4.3) I receive the following error:

patching file htmlarea-compressed.js
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file htmlarea-compressed.js.rej
patching file htmlarea.js
(0013325)
Christian Hernmarck (reporter)
26.03.07 23:17

reply to (0013323) Lars-Erik Forsberg:

Same here.

The no-wamcom-Patch semms to run through...

I patched it manually - the difference is describd in the former notes...

/ch
(0013330)
Robert Destigter (reporter)
27.03.07 09:23

I tried both .t3x files on a Firefox 2.0.0.3 and TYPO3 4.1 installation, but both fail.

The Firefox error console reports: "each is not defined". Clicking the error redirects me to the line: "var plugin = eval(plugin);"

IE, both 6 and 7 also fail (what else can you expect).
(0013345)
Oliver Hader (administrator)
27.03.07 15:31

In reply to note 0013330:
Using a version of RTEhtmlarea that was not made for TYPO3 4.1 will throw errors. The "each" thing comes from the prototype JavaScript framework. This was fixed in TYPO3 4.1 (using RTEhtmlarea 1.5.1 as system extension).
(0013346)
Clemens Riccabona (reporter)
27.03.07 15:38

My Xperience: Typo3 3.8. Intalled T3X_rtehtmlarea-1_4_3-z-200703261132.t3x as provided above as sysext.
Deleted all typo3temp files. Cleared all cache (and also my browsercache).

Now the editor loads, but the Window for creating links shows blank content.

:-(
(0013347)
Karsten Dambekalns (developer)
27.03.07 15:47

Regarding Note: 0013346 - the extension I uploaded is taken from 4.0.5, most probably it is simply incompatible to TYPO3 3.8.
(0013348)
Clemens Riccabona (reporter)
27.03.07 16:14

This may be right. But I can not update to typo3 4.1 immediately, because the system is a little bit more sophisticated set up, than 'normal' typo3 installations.
About 500 BE users, in about 200 groups, with about 250 different 'sites'.
As it is a 3.8, I'm also not able to tell the users, they should use IE, because most of them have already IE7, which breaks with typo3 3.8.0

AND: If it is not compatible with typo3 3.8.0, why isn't it set in ext_emconf.php????
(0013350)
Axel Klarmann (reporter)
27.03.07 16:15

The problem concerning 3.8 is solved by using the patch only (the diff may not work, but i didn't test this). I just removed the line of the browser test containing the test for the wamcom browser. The extension seems to be incompatible 3.8; Updated the files manually and it works for all version i got; 3.8 - 4.0
(0013351)
Christian Hernmarck (reporter)
27.03.07 16:27

@Clemens:

my rte 1.4.3 *is* for Typo3 >= 4.0 (see below) but AFAIK the ExtManager in Typo3 3.8 doesn't care about that...

So, we need a version 1.1.5a - which IMHO should run with Typo3 3.8

        'constraints' => array(
                'depends' => array(
                        'cms' => '',
                        'php' => '4.1.0-',
                        'typo3' => '4.0-',
                ),
(0013352)
Karsten Dambekalns (developer)
27.03.07 16:41

Regarding TYPO3 3.8: of course new fixed versions will be released for 3.8 as well.

But: the version I attached to this bug is for testing purposes, and as such I just didn't care for 3.8 - which I don't run anymore. So stay cool.
(0013353)
Clemens Riccabona (reporter)
27.03.07 16:48
edited on: 27.03.07 16:51

Solved the problem for my customer as follows:

Installed Version 1.3.8 from TER.

Deleted the OR of the is_wamcom Variable.

Worx now. :-)

I know, it's QD but for me it's okay in this special case.

(0013354)
Christian Hernmarck (reporter)
27.03.07 17:03

Just uploaded a corrected version for rtehtmlarea 1.5.1dev -> 1.5.1a-dev
for the ones with Typo3 v 4.1.0

Works for me - be sure to clean the browser cache and all typo3temp/htmlara... files

/Christian
(0013358)
Nico Thomaier (reporter)
27.03.07 19:05

Here A working Patch description can be found (german only)
http://www.net4media.de/neuigkeiten/typo3_news/index.html?expand=489&cHash=98121036fe [^]

i will post the fixed js files next
(0013364)
Christian Lerrahn (reporter)
28.03.07 01:18

Guys, it is rather unhelpful if dozens of people posts patches here that don't really solve the problem. That the patch helps you, does not seem to mean that it will help everyone.
Please do not write that your patch solves the problem if you haven't confirmed it properly. None of the patches I found here seemed to work for me (Firefox Linux 2.0.0.3).
(0013366)
Christian Hernmarck (reporter)
28.03.07 09:54

@Christian Lerrahn:
You're almost right. The problem is "solved" (FF 2.0.0.3 and rtehtmlarea don't work together) - I don't know why there are that much patches - it's IMHO much better (and for some people the only way) to upload a new rte extension - the only problem is the cache of Typo3 - AFAIK there is know "Typo3 way" to delete the typo3temp/rtehtmlarea*.js - but this is important!

BTW: I also use FF Linux 2.0.0.3 and my extensions (1.4.3a and 1.5.1a-dev) *are* working for me.
(0013369)
Christian Lerrahn (reporter)
28.03.07 10:26

Ok. I confirm that this works for me now, too. No clue why I could not get it to work before.
(0013370)
Clemens Riccabona (reporter)
28.03.07 10:38
edited on: 28.03.07 10:40

Just a question: Why is htmlarearte 1.5.1dev NOT in TER??

Probably this would be much easier to handle for most users. ;)

@Post 0013364 and all others which may be confused:
The only thing you have to get rid of is the Browserversion check 'is_wamcom' in connection with gecko browsers. This works I think for everyone in the described way ( -> patch both, htmlarea.js AND htmlarea_compressed.js -> delete all rtehtmlarea* files from typo3temp, -> clean your browsers cache and restart it!).
The way, how to get rid of the faulty wamcom test may be different ... (Depends on the needs of each installation -> Version of t3, version of htmlarea....)

(0013371)
Oliver Hader (administrator)
28.03.07 11:06
edited on: 28.03.07 11:08

I uploaded the new extension versions for TYPO3 3.7 and TYPO3 3.8. Please do not use them for TYPO3 4.x releases!!
End of this week there will be new patch-level releases of TYPO3 4.0 Core and TYPO3 4.1 Core which will include the fix on RTEhtmlarea. The RTEhtmlarea is since TYPO3 4.0 part of the Core and thus developed with the Core.

T3X_rtehtmlarea-1_1_6-z--TYPO3-3_7.t3x (RTEhtmlarea 1.1.6 for TYPO3 3.7 only)
T3X_rtehtmlarea-1_2_2-z--TYPO3-3_8.t3x (RTEhtmlarea 1.2.2 for TYPO3 3.8 only)

TYPO3 3.7 & 3.8 users: Please test these extensions and tell, if there are any problems on your releases. These extension upgrades will be published on the TER tomorrow.

(0013373)
Morten Therkildsen (reporter)
28.03.07 12:22

Will there be a new version of TYPO3? - should be. It's not fair to patch a fresh install of TYPO3.
(0013374)
Oliver Hader (administrator)
28.03.07 12:26

Morten, as mentioned one post before yours:
There will be new patch-level releases of TYPO3 4.0 and 4.1, which means:
TYPO3 4.0.6 and TYPO3 4.1.1 as new releases.
(0013383)
Oliver Hader (administrator)
28.03.07 15:33

Fixed in SVN: Trunk, TYPO3-4_1, TYPO3-4_0
(0013422)
Daniel Truninger (reporter)
29.03.07 13:35

1.5x Version for Typo3 4.1x and Firefox 2.03 works. Yes, now it has to be published on Typo3 TER asap … then we can close this bug, right?
(0013423)
Oliver Hader (administrator)
29.03.07 14:19

Okay, there were three new releases published to TER:

* 1.1.6 (replacing 1.1.5) for the TYPO3 3.7 branch
* 1.2.2 (replacing 1.2.1) for the TYPO3 3.8 branch
* 1.4.4 (replacing 1.4.3) for the TYPO3 4.0 branch (including the features by Stanislav that are not in Core)

Today or tomorrow there will be prerelease of 4.0.6 and 4.1.1. If nobody objects, the final patch-level releases will be published at the beginning of the next week. The versions that are part of the Core as system extensions were not uploaded to TER, these are:

* 1.3.9 (replacing 1.3.8) only in TYPO3 4.0.6! Not in TER!
* 1.5.2 (replacing 1.5.1) only in TYPO3 4.1.1! Not in TER!

Just check http://typo3.org/download/packages/ [^] for new releases the next few days...
(0013425)
Oliver Hader (administrator)
29.03.07 14:33

Several patches for different TYPO3 branches were published in TER and SVN. New releases of the 4.0.x and 4.1.x branches will be available in the next few days.

If you experience further problems concerning this issue and thus, only on Firefox 2.0.0.3, please make sure that you've installed the correct version of the extension, check if you're using a local extension or a system extension and finally clear the system cache. If the problem remains, please open a new bug-report and describe your problem in detail.

Thanks to anyone who supported TYPO3 to solve this bug by testing, researching, coding and whatever!

This bug is resolved and fixed!


Best regards,
Olly

- Issue History
Date Modified Username Field Change
21.03.07 08:18 Stefano Cecere New Issue
21.03.07 08:37 Michael Stucki Issue Monitored: Michael Stucki
21.03.07 11:10 Reto Schmid Issue Monitored: Reto Schmid
21.03.07 11:47 Maria Issue Monitored: Maria
21.03.07 11:59 David Zschille Note Added: 0013193
21.03.07 12:39 Christian Brunner Note Added: 0013195
21.03.07 12:39 Christian Brunner Issue Monitored: Christian Brunner
21.03.07 12:56 David Zschille Issue Monitored: David Zschille
21.03.07 13:16 Michael Stucki Note Added: 0013196
21.03.07 13:16 Michael Stucki Priority normal => high
21.03.07 13:16 Michael Stucki Status new => acknowledged
21.03.07 13:20 Peter Schnitzler Issue Monitored: Peter Schnitzler
21.03.07 13:53 Jonas D?bi Note Added: 0013198
21.03.07 13:54 Jonas D?bi Issue Monitored: Jonas D?bi
21.03.07 14:04 Patrick Broens Status acknowledged => assigned
21.03.07 14:04 Patrick Broens Assigned To => Patrick Broens
21.03.07 14:06 Christian Hernmarck Note Added: 0013201
21.03.07 14:08 Patrick Broens Relationship added related to 0004870
21.03.07 14:31 Michael Stucki Relationship added related to 0004238
21.03.07 15:17 Peter Kraume Issue Monitored: Peter Kraume
21.03.07 15:23 Alexander Grein Note Added: 0013207
21.03.07 15:23 Alexander Grein Issue Monitored: Alexander Grein
21.03.07 15:33 Davide Principi Issue Monitored: Davide Principi
21.03.07 15:41 Christian Buelter Issue Monitored: Christian Buelter
21.03.07 17:05 Tobias Hoevelborn Issue Monitored: Tobias Hoevelborn
21.03.07 17:09 Ruben Theerkorn Issue Monitored: Ruben Theerkorn
21.03.07 18:49 Thomas Janke Issue Monitored: Thomas Janke
21.03.07 20:04 Stefano Cecere Note Added: 0013211
21.03.07 21:00 Martijn Note Added: 0013215
21.03.07 22:15 Oliver Hader Issue Monitored: Oliver Hader
21.03.07 22:21 Oliver Hader Relationship added has duplicate 0005268
21.03.07 22:25 Oliver Hader Relationship added has duplicate 0005270
21.03.07 22:26 Jens K?ster Issue Monitored: Jens K?ster
22.03.07 05:25 Stevo Issue Monitored: Stevo
22.03.07 06:59 Dieter Bunkerd Issue Monitored: Dieter Bunkerd
22.03.07 07:27 Jan-Philipp Halle Issue Monitored: Jan-Philipp Halle
22.03.07 09:04 Axel Klarmann Note Added: 0013224
22.03.07 09:35 Stefan Precht Issue Monitored: Stefan Precht
22.03.07 09:52 Stefan Precht Note Added: 0013226
22.03.07 10:10 Staffan Ericsson Issue Monitored: Staffan Ericsson
22.03.07 10:27 Michael Birchler Issue Monitored: Michael Birchler
22.03.07 10:34 Patrick Broens File Added: bug5266.diff
22.03.07 10:36 Patrick Broens Note Added: 0013230
22.03.07 10:40 Patrick Broens Status assigned => resolved
22.03.07 10:40 Patrick Broens Resolution open => fixed
22.03.07 10:40 Patrick Broens Note Added: 0013231
22.03.07 11:12 TEDONE Issue Monitored: TEDONE
22.03.07 11:28 Thomas Issue Monitored: Thomas
22.03.07 12:59 Oliver Hader Relationship added has duplicate 0005277
22.03.07 14:31 alexander onea Issue Monitored: alexander onea
22.03.07 16:00 Michael Stucki Status resolved => feedback
22.03.07 16:00 Michael Stucki Resolution fixed => reopened
22.03.07 16:00 Michael Stucki Note Added: 0013249
22.03.07 16:01 Michael Stucki Relationship added has duplicate 0005279
22.03.07 16:02 Axel Jindra Note Added: 0013250
22.03.07 16:06 Ruben Theerkorn Note Added: 0013251
22.03.07 16:07 Ruben Theerkorn Note Edited: 0013251
22.03.07 16:10 Marc Issue Monitored: Marc
22.03.07 16:10 Marc Issue End Monitor: Marc
22.03.07 16:12 Axel Jindra Note Edited: 0013250
22.03.07 16:12 Staffan Ericsson Note Added: 0013253
22.03.07 16:12 Axel Jindra Note Edited: 0013250
22.03.07 16:17 Ruben Theerkorn Note Edited: 0013251
22.03.07 16:18 Sascha Egerer Note Added: 0013254
22.03.07 16:25 Bruno Issue Monitored: Bruno
22.03.07 16:27 Patrick Broens Note Added: 0013255
22.03.07 16:28 Ruben Theerkorn Note Added: 0013256
22.03.07 16:31 Sascha Egerer Note Added: 0013257
22.03.07 16:33 Bruno Note Added: 0013258
22.03.07 16:33 Patrick Broens Note Added: 0013259
22.03.07 16:42 Axel Jindra Note Edited: 0013250
22.03.07 16:44 Sascha Egerer Issue Monitored: Sascha Egerer
22.03.07 18:31 Peter E. Issue Monitored: Peter E.
22.03.07 19:27 Oliver Hader Note Added: 0013264
22.03.07 20:41 Stevo Issue End Monitor: Stevo
22.03.07 21:02 alexander onea Note Added: 0013266
22.03.07 21:22 Peter Schnitzler Issue End Monitor: Peter Schnitzler
23.03.07 04:13 asdfasd Issue Monitored: asdfasd
23.03.07 08:05 Oliver Hader Relationship added has duplicate 0005280
23.03.07 08:05 Dirk Diebel Issue Monitored: Dirk Diebel
23.03.07 09:37 Stefan Neufeind Issue Monitored: Stefan Neufeind
23.03.07 09:58 Patrick Broens Note Added: 0013272
23.03.07 10:09 Christian Hernmarck Note Added: 0013275
23.03.07 10:12 Thomas Issue End Monitor: Thomas
23.03.07 10:16 Patrick Broens Note Added: 0013276
23.03.07 10:20 Thomas Juhnke Issue Monitored: Thomas Juhnke
23.03.07 10:48 Marc V?ron Issue Monitored: Marc V?ron
23.03.07 11:49 Rainer Treichel Issue Monitored: Rainer Treichel
23.03.07 11:49 Daniel Chabrol Issue Monitored: Daniel Chabrol
23.03.07 14:33 Timo Boehme Issue Monitored: Timo Boehme
23.03.07 14:50 Sebastian Busch Issue Monitored: Sebastian Busch
23.03.07 15:52 Jason Lefkowitz Note Added: 0013282
23.03.07 16:09 Jason Lefkowitz Note Added: 0013283
23.03.07 17:09 Jason Lefkowitz Note Added: 0013285
23.03.07 17:19 Oliver Hader Note Added: 0013286
23.03.07 18:44 Jason Lefkowitz Note Added: 0013289
23.03.07 18:47 Jason Lefkowitz Note Edited: 0013289
23.03.07 18:48 Ekkehard Gümbel Issue Monitored: Ekkehard Gümbel
23.03.07 20:35 Matthias Kall Issue Monitored: Matthias Kall
24.03.07 08:41 Marc V?ron Note Added: 0013291
24.03.07 08:51 Christian Hernmarck Note Added: 0013292
24.03.07 08:57 Christian Hernmarck Note Added: 0013293
24.03.07 14:31 Francois Suter Issue Monitored: Francois Suter
24.03.07 16:27 Hans vom Schloß Note Added: 0013299
25.03.07 13:49 Jochen Weber Issue Monitored: Jochen Weber
25.03.07 17:23 Palahala Issue Monitored: Palahala
25.03.07 18:02 Christian Hernmarck File Added: T3X_rtehtmlarea-1_4_3a-z-200703251756.t3x
25.03.07 18:02 Christian Hernmarck Note Added: 0013306
25.03.07 23:53 Roger Bunyan Issue Monitored: Roger Bunyan
26.03.07 10:21 Harald Klotzberg Issue Monitored: Harald Klotzberg
26.03.07 10:37 Stefan Katzer Note Added: 0013309
26.03.07 10:39 Lukas Rueegg Issue Monitored: Lukas Rueegg
26.03.07 10:48 oLiver Gassner Issue Monitored: oLiver Gassner
26.03.07 11:17 Christoph Bl?mer Note Added: 0013312
26.03.07 11:28 adrian von buttlar Issue Monitored: adrian von buttlar
26.03.07 11:38 Gregor Weissmann Issue Monitored: Gregor Weissmann
26.03.07 11:49 Karsten Dambekalns File Added: T3X_rtehtmlarea-1_4_3-z-200703261132.t3x
26.03.07 11:49 Karsten Dambekalns File Added: bug-5266-no-wamcom.diff
26.03.07 11:52 Karsten Dambekalns Note Added: 0013314
26.03.07 11:53 Ruben Theerkorn Issue End Monitor: Ruben Theerkorn
26.03.07 12:16 Michael Stucki File Deleted: bug5266.diff
26.03.07 12:16 Michael Stucki File Added: bug_5266.diff
26.03.07 12:16 Michael Stucki File Added: bug_5266_4-0.diff
26.03.07 12:17 Michael Stucki Note Added: 0013315
26.03.07 15:39 Marcel Alburg Note Added: 0013319
26.03.07 15:48 Michael Stucki Note Added: 0013320
26.03.07 19:47 Jonas D?bi Sponsorship Added Jonas D?bi: EUR 30
26.03.07 19:47 Jonas D?bi Sponsorship Total 0 => 30
26.03.07 20:09 Marcel Alburg Note Added: 0013322
26.03.07 20:09 Philippe Gagnon Issue Monitored: Philippe Gagnon
26.03.07 20:30 Balisky Christophe Issue Monitored: Balisky Christophe
26.03.07 21:18 Lars-Erik Forsberg Note Added: 0013323
26.03.07 21:35 Lars-Erik Forsberg Issue Monitored: Lars-Erik Forsberg
26.03.07 22:26 Roland Obermayer Issue Monitored: Roland Obermayer
26.03.07 23:17 Christian Hernmarck Note Added: 0013325
27.03.07 01:30 David Bruchmann Issue Monitored: David Bruchmann
27.03.07 09:23 Robert Destigter Note Added: 0013330
27.03.07 09:31 Martin Mai Issue Monitored: Martin Mai
27.03.07 09:33 Robert Destigter Issue Monitored: Robert Destigter
27.03.07 13:05 Clemens Riccabona Issue Monitored: Clemens Riccabona
27.03.07 15:07 move-elevator GmbH (Florian Wentzel) Sponsorship Added move-elevator GmbH (Florian Wentzel): EUR 50
27.03.07 15:07 move-elevator GmbH (Florian Wentzel) Sponsorship Total 30 => 80
27.03.07 15:07 move-elevator GmbH (Florian Wentzel) Issue Monitored: move-elevator GmbH (Florian Wentzel)
27.03.07 15:29 ulf treger Issue Monitored: ulf treger
27.03.07 15:31 Oliver Hader Note Added: 0013345
27.03.07 15:38 Clemens Riccabona Note Added: 0013346
27.03.07 15:47 Karsten Dambekalns Note Added: 0013347
27.03.07 16:14 Clemens Riccabona Note Added: 0013348
27.03.07 16:15 Axel Klarmann Note Added: 0013350
27.03.07 16:21 Marcel Alburg Issue Monitored: Marcel Alburg
27.03.07 16:21 Marcel Alburg Issue End Monitor: Marcel Alburg
27.03.07 16:27 Christian Hernmarck Note Added: 0013351
27.03.07 16:28 Jens Hirschfeld Issue Monitored: Jens Hirschfeld
27.03.07 16:41 Karsten Dambekalns Note Added: 0013352
27.03.07 16:48 Clemens Riccabona Note Added: 0013353
27.03.07 16:50 Clemens Riccabona Note Edited: 0013353
27.03.07 16:51 Clemens Riccabona Note Edited: 0013353
27.03.07 17:03 Christian Hernmarck File Added: T3X_rtehtmlarea-1_5_1a-dev-z-200703271702.t3x
27.03.07 17:03 Christian Hernmarck Note Added: 0013354
27.03.07 18:01 Martin Mai Issue End Monitor: Martin Mai
27.03.07 19:05 Nico Thomaier Note Added: 0013358
27.03.07 19:09 Nico Thomaier File Added: patch-ff2-0-0-3.zip
28.03.07 01:15 Christian Lerrahn Issue Monitored: Christian Lerrahn
28.03.07 01:18 Christian Lerrahn Note Added: 0013364
28.03.07 09:54 Christian Hernmarck Note Added: 0013366
28.03.07 10:26 Christian Lerrahn Note Added: 0013369
28.03.07 10:38 Clemens Riccabona Note Added: 0013370
28.03.07 10:40 Clemens Riccabona Note Edited: 0013370
28.03.07 10:59 Oliver Hader File Deleted: patch-ff2-0-0-3.zip
28.03.07 11:00 Oliver Hader File Added: T3X_rtehtmlarea-1_1_6-z--TYPO3-3_7.t3x
28.03.07 11:01 Oliver Hader File Added: T3X_rtehtmlarea-1_2_2-z--TYPO3-3_8.t3x
28.03.07 11:06 Oliver Hader Note Added: 0013371
28.03.07 11:08 Oliver Hader Note Edited: 0013371
28.03.07 12:19 Jose Antonio Guerra Issue Monitored: Jose Antonio Guerra
28.03.07 12:22 Morten Therkildsen Note Added: 0013373
28.03.07 12:26 Oliver Hader Note Added: 0013374
28.03.07 15:33 Oliver Hader Note Added: 0013383
28.03.07 17:45 Rainer Treichel Issue End Monitor: Rainer Treichel
28.03.07 20:27 Lars-Erik Forsberg Issue End Monitor: Lars-Erik Forsberg
29.03.07 13:35 Daniel Truninger Note Added: 0013422
29.03.07 14:19 Oliver Hader Note Added: 0013423
29.03.07 14:26 Stefan Precht Issue End Monitor: Stefan Precht
29.03.07 14:33 Oliver Hader Status feedback => resolved
29.03.07 14:33 Oliver Hader Resolution reopened => fixed
29.03.07 14:33 Oliver Hader Note Added: 0013425
29.03.07 16:09 Christophe Monard Issue Monitored: Christophe Monard
29.03.07 16:38 Oliver Hader Relationship added parent of 0005321
30.03.07 11:29 ulf treger Issue End Monitor: ulf treger
30.03.07 14:38 Oliver Hader Relationship added parent of 0005295
30.03.07 14:40 Oliver Hader Relationship added parent of 0005328
02.04.07 05:38 Aobara BlazingBlade Issue Monitored: Aobara BlazingBlade
05.04.07 14:17 Christian Brunner Issue End Monitor: Christian Brunner
07.04.07 12:43 Michael Stucki Relationship added has duplicate 0005376
07.04.07 16:38 Jens K?ster Issue End Monitor: Jens K?ster
20.07.07 09:29 Dirk Diebel Issue End Monitor: Dirk Diebel
24.07.07 08:37 Bruno Issue End Monitor: Bruno
27.06.08 10:49 Ingo Renner Status resolved => closed
24.10.08 19:08 Oliver Hader Issue End Monitor: Oliver Hader
hosted by
bitfarmers TYPO3 Hosting
in case of Problems mail to:
service [at] bitfarmers [dot] com

Mantis 1.1.8[^]
Copyright © 2000 - 2009 Mantis Group
Powered by Mantis Bugtracker