[TYPO3-core] RFC: Bug 5907: RTE-Plugins: Use record specific RTEtsConfigParams

Michael Stucki michael at typo3.org
Fri Jul 13 19:02:01 CEST 2007

Uuuh, that was probably a hard-one...
I just tested this with the help of Oliver. Can confirm both problem and

After all, I would even say that this is a no-brainer, it's just hard to get
that far and see what the problem actually is.

So I would say, commit this if nobody objects until tomorrow evening.

- michael

Oliver Hader wrote:

> This is a SVN patch request.
> Problem:
> The RTEhtmlarea plugin UserElements offers a possibility to create
> custom tags. The shown popup window with those user elements gets called
> with the GET parameter "RTEtsConfigParams" which has several information
> about the tablename, uid, pid, ... of the field the RTEhtmlarea field
> was put it.
> Currently the information of the variable "RTEtsConfigParams" is created
> only for the _first_ instance of RTEhtmlarea in the JavaScript variable
> RTEarea[0]['RTEtsConfigParams']. Thus, all other RTE fields get the same
> RTEtsConfigParams.
> This makes it impossible to render record and field specific user
> elements in the popup window showing the available tags.
> This behaviour occurs also in other Plugins of RTEhtmlarea, the
> "UserElements" plugins was just taken as example.
> Solution:
> Use RTEarea[<editorNumber>]['RTEtsConfigParams'] instead of
> RTEarea[0]['RTEtsConfigParams'] to have the correct configuration for
> each instance of RTEhtmlarea.
> Comments:
> The attached patch changes this behaviour for the plugins
> TYPO3HtmlParser, TYPO3Browsers, Acronym and UserElements. The changed
> compressed scripts are also part of the patch.
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=5907
> Branches: TYPO3_4-1 & Trunk
> olly

Use a newsreader! Check out

More information about the TYPO3-team-core mailing list