6.3 Widget ViewHelpers

Widgets are ViewHelpers

Widgets feature their own controller

Widgets are interfaces

Widgets cannot be cascaded

Widgets do not return any content, but process them

Widget classes always extend the abstract class \TYPO3\CMS\Fluid\Core\Widget\AbstractWidgetViewHelper

A Widget must have its own template

Widget class files should be stored in directory Classes/ViewHelpers/Widget/

Widgets can only be used in the frontend

Widgets can only be used in the backend

Widgets use their own ViewHelpers to manage sub-requests

Widget class files are located under Classes/ViewHelpers/Widgets/

Widget class files are located under Classes/Widgets/

The controller class file of a Widget-ViewHelper is located under Classes/ViewHelpers/Widgets/Controller/

The controller class file of a Widget-ViewHelper is located under Classes/Controller/Widgets/

Widgets must be registered in the global configuration file typo3conf/LocalConfiguration.php

Template files of a Widget are located under Resources/Private/Templates/ViewHelpers/Widget/<widgetname>/

<f:widget.paginate> for the pagination of objects

<f:widget.sort> for sorting objects and arrays in alphanumeric order.

<f:widget.metaTags> for adding meta tags to the HTML output.

<f:widget.filter> for removing swearword from a text.

<f:widget.autocomplete> for auto-completing input fields.

<f:widget.link> for creating links to Extbase actions within widgets

This is not possible, because Widget templates are not configurable

By utilising the subkey view.widget in TypoScript

By utilising the subkey view.template in TypoScript

If the template is located in the sub-directory widget, nothing more needs to be done

Template files with the file extension _w.html are automatically treated as Widget templates

\TYPO3\CMS\Extbase\ViewHelpers\Paginate\InputValues

\TYPO3\CMS\Extbase\Persistence\Generic\QueryResultInterface

\TYPO3\CMS\Extbase\Persistence\ObjectStorage

\TYPO3\CMS\Extbase\Persistence\ObjectStorageInterface

\ArrayAccess