Bug #15822
closedhtmlArea RTE does not load when served by Win XP Home
0%
Description
The RTE_HTMLArea isn?t loading on certain WAMP. Only the massage ?The editor is being loaded. Please wait...? is showing.
Some JavaScript errors appearing.
The first error is:
--------------- (Firefox console start)
Fehler: syntax error
Quelldatei: http://localhost/germansweets/typo3temp/rtehtmlarea_htmlarea_4bd37204cde576f3683f6bbe97a18ae7.js
Zeile: 1846
Quelltext:
if (typeof(_editor_url) == "string") {
--------------- (Firefox console end)
This is no browser problem. It does not work from remote to.
On another WAMP and LAMP the RTE is working well.
The working RTE is running on WIN XP pro. The fault RTE is running on Win XP home. That is the main difference.
I tried a lot configuration. PHP 4 / 5. With and without PEARL. Activating and deactivating several PHP extensions. But nothing happened.
(issue imported from #M2865)
Files
Updated by Stanislas Rolland over 18 years ago
Maybe you can report the TYPO3 version? the version of htmlArea RTE?
Do you mean that you have problems when TYPO3 is installed on Win XP Home?
Updated by Stanislas Rolland over 18 years ago
The script uses XMLHttpRequest to download required script components. Maybe this fails for some reason? The issue may also be with downloading css files.
Using TYPO3 4.0RC1 and htmlArea RTE 1.3.0, try the following extension settings:
Default configuration settings: Minimal
Enable troubleshooting mode: enabled
Enable compressed scripts: disabled
Please report any Page TSConfig settings.
Updated by Stanislas Rolland over 18 years ago
I don't understand why you copy your TS template. I asked for your Page TSConfig settings.
Use the system extension provided with TYPO3 4.0RC1. Delete any other local or global versions.
What happens when you set:
Default configuration settings: Minimal
Enable troubleshooting mode: enabled
Enable compressed scripts: disabled ?
How do you know that Ajax is running well?
What other extensions are installed?
Updated by Stanislas Rolland over 18 years ago
I am running out of ideas...
Maybe permissions on files created in typo3temp?
Could you send me copy of the source HTML of the backend frame in which the RTE is displayed?
Updated by Stanislas Rolland over 18 years ago
Could there be some invalid character in one of the generated JS files? Or perhaps broken, incomplete file?
Please do the following: delete all files prefixed rtehtmlarea_ from typo3temp directory. Try to load the editor. Inspect all newly created files with same prefix in typo3temp. Anything suspicious in these files?
Use the minimal configuration settings to do this test so that less files will be created.
Updated by Stanislas Rolland over 18 years ago
What do you mean:
"Opera shows the same errors like Firefox."
Is the editor enabled in Opera?
Updated by Stanislas Rolland over 18 years ago
Is the size and content of
typo3temp/rtehtmlarea_htmlarea_4bd37204cde576f3683f6bbe97a18ae7.js
the same as the size and content of
typo3/sysext/rtehtmlarea/htmlarea/htmlarea.js?
Updated by Stanislas Rolland over 18 years ago
It always stopped at Line 2825:
--------
var editor = RTEarea[editorNumber]["editor"]EOF
I don't understand where this EOF is coming from. And this is not the content of line 2825.
Updated by Oliver Hader over 17 years ago
Thomas, what exactly did you change in the htmlarea.js? Maybe you can provide a diff file concerning these changes?
Updated by Oliver Hader over 17 years ago
Thomas, please don't mix bugs. This bug report is about something different. The Firefox 2.0.0.3 issue is found at bug-id #5266
I removed your three files submitted from 23rd to 26th March 2007 because they are duplicates to bug #5266.
Updated by Stanislas Rolland over 14 years ago
Is this issue in any way related with the RTE, or even TYPO3?
It seems that the script file gets corrupted on these installation or during transfer to the client browser.
Updated by Stanislas Rolland over 14 years ago
No feedback for a long time. Closing the issue.