Bug #22575
closedT3 version 4.4.0beta1: Again, like with previous alpha or beta versions, the RTEhtmlarea does not start
0%
Description
Again, like with previous alpha or beta versions, the RTEhtmlarea does not start. Looks like a old problem is coming back.
The RTE gives a "The editor is being loaded. Please wait..."
And that's it.
All caches flushed and typo3temp complete emptied
No local extensions, and a lot of the system extensions like adv. fe-editing, reporting etc. also uninstalled.
(issue imported from #M14290)
Updated by Steffen Gebert over 14 years ago
Ah.. and could you please check beta2? Are the files in typo3temp/rtehtmlarea/ created, after you flushed RTE cache?
Updated by Daniel Doesburg over 14 years ago
In FF3.6.3, chrome and ie8 under windows 7
In typo3temp/rtehtmlarea/ are a lot of new files. The whole temp directory was emptied after installing beta2
And as far as I can see are the permissions also correct.
Updated by Daniel Doesburg over 14 years ago
The problems above are with a site who I already made as T3version4.1.
I've upgraded it from version to version.
And now I've the mentioned problems.
But I've set up a new site as a T3-4.4.0b1 site. After updating all is well. Also the RTE.
So I think, there are some rests of the previous versions what makes the difference.
I'll search for it.
For the time being, set this bug op hold.
Sorry
Updated by Stanislas Rolland over 14 years ago
Any error on the JavaScript console?
Updated by Stanislas Rolland over 14 years ago
Please enable RTE troubleshooting mode in the Extension Manager, and report any errors displayed in the log below the RTE-enabled content element.
Or report any JS error displayed on the JavaScript console.
Updated by Daniel Doesburg over 14 years ago
It's because this:
RTE.default.toolbarOrder = ..., lefttoright, righttoleft, ...
Updated by Ben van 't Ende over 14 years ago
Hey Daniel,
What exactly do you mean. Is that piece of TS the reason the RTE is not loading?
Updated by Stanislas Rolland over 14 years ago
See #14374.
This is now fixed in SVN trunk (for TYPO3 4..4 beta3).