[TYPO3-dev] Question about RTE link generation

[Stanislas Rolland]

Hi Steffen,,
> we all know RTE as the "Eierlegende-Wollmilch-Sau" (sry, don't know any 
> corresponding word in english) of editors. Something, which bothers me 
> all the time is the link generation.
> The wizard-window with selection for email-adresses,pages and so on is 
> very nice for editors... But for admins there is the questions: why ara 
> links generated as "full tags" and not as <link typolinkparam>text</link>.
> 
Perhaps RTE transformation is not correctly configured in your installation?

> Generating links and URLs completely TS config about linkvars, 
> linkhandlers, hooks on linkgeneration (such as googleanalytics, download 
> counter) and furthermore realurl are ignored.
> 
Links inserted in the RTE are typolinks and are rendered as such in the 
FE. If they are not rendered with realurl in your installation, I would 
think that something is not correctly configured.

> So is there any reason why not acting like the standard tt_content link 
> wizard (returning a parameter for typolink.parameter) and saving the 
> link by <link param>|</link>, letting the parsefunc doing the rest, 
> respecting all configuration.
> 
The links are inserted in the RTE as a-tags so that they may be rendered 
correctly in the editing area of the RTE and may be edited correctly in 
the DOM tree used by the RTE. However, these links are transformed on 
the way to the database and are indeed inserted in the database as 
typolinks and should therefore be rendered in the FE just like any other 
typolinks and all their features.

> If there is no reason for that: Tell me how I can help you refactoring 
> this to work "the typo3 way" of link generation... (Probably a switch 
> like "use classic link generation" in future versions for backwards 
> compatibility).
> 
I think that the RTE works the TYPO3 way. The RTE extends the "standard 
link wizard" and uses an adapted version of script browse_links.php (for 
historical reason, I would think). Some extensions that may hook on 
browse_links.php or on class.browse_links.php may need to hook also on 
the corresponding RTE scripts. If they neglect to do so, the features 
they provide may not be available in the RTE. It may be possible to get 
rid of the RTE version of script browse_links.php, but I think the 
benefits would be minor.

Kind regards,
Stanislas