Bug #25175
closed
More than one Frontend RTE duplicates entire Page
Added by z.c over 13 years ago.
Updated over 9 years ago.
Category:
RTE (rtehtmlarea + ckeditor)
Description
When I include more than one RTE in my Frontend-Extension (multiple calls to tx_rtehtmlarea_pi2::drawRTE) the entire Page-Content (without USER_INT's) is rendered into the head of the Page ($GLOBALS['TSFE']->additionalHeaderData['rtehtmlarea']).
This happens in Line 240 of " * $Id: class.tx_rtehtmlarea_pi2.php 10503 2011-02-20 04:20:35Z stan $ *".
Possible Workaround:
Include something like this after the first Call to "tx_rtehtmlarea_pi2::drawRTE":
if ($this->RTEcounter == 1)
{
$this->additionalHeaderData_rtehtmlarea = $GLOBALS['TSFE']->additionalHeaderData['rtehtmlarea'];
}
else
{
$GLOBALS['TSFE']->additionalHeaderData['rtehtmlarea'] = $this->additionalHeaderData_rtehtmlarea;
}
(issue imported from #M17763)
I can confirm this behaviour in TYPO3 Versions from 4.4.4 to 4.5.2
- Category set to RTE (rtehtmlarea + ckeditor)
- Target version deleted (
0)
- TYPO3 Version set to 4.5
I can confirm this bug for all versions of TYPO3 4.5.x and for all template mapping methods: traditional, templavloila and Fluid.
The main problem seems to be that the page renderer is reset after rendering the first RTE. This also clears the special template file and that file is not restored, so on next rendering the default template file is used to render the css and js inclusions which results in a duplicate page.
As a workaround/solution to this problem you should simply avoid to render more than one RTE with the same instance of tx_rtehtmlarea_pi2. Create a new instance per RTE and you are fine.
- Status changed from New to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF