Bug #19423
closedEdit in Rich Text Editor - Button doesn't work anymore in Web>Page
0%
Description
If any user or admin clicks on the button "Edit in Rich Text Editor" in Web>Page Module for any text content element, this results in a broken Rich Text Editor (rtehtmlarea).
This is reproducable in TYPO3 4.2.2 with Firefox, IE7, Chrome and Opera. It also occurs with a new clean TYPO3 4.2.2 installation.
See attached screenshots.
Firefox error console says:
Error: TBE_EDITOR is not defined
Source: http://.../typo3/wizard_rte.php?&P[table]=tt_content&P[uid]=307&P[pid]=10&P[field]=bodytext&P[returnUrl]=%2Ftypo3%2Fsysext%2Fcms%2Flayout%2Fdb_layout.php%3Fid%3D10
Line: 204
(issue imported from #M9497)
Files
Updated by Oliver Hader about 16 years ago
Please test the attached patch in combination with the patch provided at issue #9494
Updated by Christian Hernmarck about 16 years ago
I have problems with the patch:
...../typo3/typo3_src-4.2.2_copy# patch p0 < 0009497.patch saving rejects to file typo3/wizard_rte.php.rej
patching file typo3/alt_palette.php
patching file typo3/wizard_rte.php
Hunk #1 FAILED at 110.
1 out of 1 hunk FAILED -
patching file typo3/mod/user/ws/workspaceforms.php
Hunk #1 succeeded at 137 with fuzz 1.
patching file typo3/sysext/cms/layout/db_layout.php
Hunk #1 succeeded at 404 with fuzz 1.
Hunk #2 FAILED at 545.
1 out of 2 hunks FAILED -- saving rejects to file typo3/sysext/cms/layout/db_layout.php.rej
/Christian
Updated by Oliver Hader about 16 years ago
Please check the attached new patches (the old one was only for Trunk):
0009497_trunk.patch - TYPO3 4.3 development (Trunk)
0009497_4-2.patch - TYPO3 4.2.x
The patches now include also the fix for issue #9494 - this has to be handled in one step an cannot be separated.
Updated by Christian Hernmarck about 16 years ago
Just implemented 0009497_4-2.patch - this fixes this rte problem on my 4.2.2 installation (no other tests...).
Thanx
Updated by Tobias Liebig about 16 years ago
The Patch 0009497_4-2.patch worked for me too (4.2.2).
It also fixes #9494 (brocken password and double fields)
Updated by Tobias Liebig about 16 years ago
i'll suggest to replace this:
function typoSetup () {
this.passwordDummy = '********';
this.decimalSign = '.';
}
var TS = new typoSetup();
with something like:
var TS = TS || {};
TS.passwordDummy = '********';
TS.decimalSign = '.';
and do the same for all "function typoSetup" in
typo3/jsfunc.tbe_editor.js
typo3/alt_main.php
typo3/backend.php
typo3/alt_doc.php
so the order does not matter anymore, as the TS object is not overwritten, but extended.
Updated by Steffen Kamper about 16 years ago
@Tobias: looks great. Could you make a patch therefore?
@Olly: i tested #9494 and works perfect, no need for the palette-stuff imho
Updated by Oliver Hader about 16 years ago
Thanks for your feedback. I'm going to put the patches on the Core List tomorrow.
The changes for the "TS" thingy will go to a new issue and RFC and for TYPO3 4.3 only
Updated by Daniel Krupke about 16 years ago
Thanks for that patch. It works quite fine with TYPO3 4.2.2 environments.
Updated by Leonhard Wimmer about 16 years ago
Thank you for the patch. It works perfectly.
Updated by Francois Suter about 16 years ago
I can only add my voice to that. The patch works real fine. I hope you can submit the patch to the core list soon. And then we should probably have a hot fix 4.2.3 release.
Updated by Administrator Admin about 16 years ago
I'm a real newbie, but how do I apply the patch?
Updated by Michael Stucki about 16 years ago
Fixed in TYPO3 4.2.3 (rev. 4326) and Trunk (rev. 4327).