Project

General

Profile

Actions

Bug #41440

closed

RTE does not load in Frontend in USER_INT plugins with TYPO3 6.0

Added by Christian Buelter about 12 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
RTE (rtehtmlarea + ckeditor)
Target version:
-
Start date:
2012-09-28
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.0
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

In a non-cached plugin, the frontend RTE does not load in TYPO3 6.0.

This is the same behaviour as described in http://forge.typo3.org/issues/23019, but now with TYPO3 6.0 (tested against the current git master branch).

I tested it with ke_troubletickets, but any other non-cached frontend plugin making use of the RTE should also be affected.

Steps to reproduce this:

1. Install ke_troubletickets, insert plugin pi1 ("Show tickets") into a page. You need a valid frontend login to use this extension.

2. Open a new ticket, the RTE does not load.

3. In ext_localconf.php change

t3lib_extMgm::addPItoST43($_EXTKEY,'pi1/class.tx_ketroubletickets_pi1.php','_pi1','list_type',0);

to

t3lib_extMgm::addPItoST43($_EXTKEY,'pi1/class.tx_ketroubletickets_pi1.php','_pi1','list_type',1);

(making it a cached plugin)

Now the RTE appears in the frontend, but of course the extension functionality breaks.

I testet a bit and at some point I was able to load the RTE by replacing the calls to $this->pageRenderer with $GLOBALS['TSFE']->getPageRenderer in FrontendRteController.php and RteHtmlAreaBase.php, but still some CSS was obviously missing. This is just a remark which hopefully is helpful.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #62806: RTE: Remove unused template fileClosedStanislas Rolland2014-11-10

Actions
Actions #1

Updated by Gerrit Code Review about 12 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15413

Actions #2

Updated by Stanislas Rolland about 12 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #3

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF