Link handling¶
Links entered in the backend in TYPO3 are stored in an internal format in the database.
Input of different link formats in the backend. The rich-text editor is disabled for demonstration of these formats.¶
For example, a link to the page with uid 42 is stored in a backend field as
t3://page?uid=42 and in the rich-text editor (RTE) as
<a href="t3://page?uid=1">test</a>.
Such links must be converted before they are output as HTML in the frontend. For example, in Fluid all input from the RTE should be output by the ViewHelper format.html:
<f:format.html>{myContent.bodytext}</f:format.html>
Links provided in backend fields like the header_link can be used as
input in the ViewHelper link.typolink:
<f:link.typolink parameter="{myContent.header_link}">
{myContent.header_link}
</f:link.typolink>
In TypoScript, RTE content can be converted by the function parseFunc, link fields can be converted into HTML by the function typolink.
In PHP context links are usually stored in an array format. Each link type is handled by a Core link handler which maps between different formats.
The link browser is the modal in which users can configure links in both the Rich text editors (RTE) and the FormEngine. The link browser offers tabs for the different types of links like page, external, file, email, phone record and possibly more. Each tab of the link browser has an associated backend link handler that renders the tab and handles editing links. The link browser can be extended by custom links to different record types and custom link handler implementations.
A link browser for records of the custom table 'haiku'¶
Contents: