You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
extbase extensions all rely on data that are stored in special tables.
The case that the data are coming from the content record itself is not covered in the documentation.
An element like this would be a content element instead of plugin, but can be rendered with controller and view, the repository is in this scenario not used, as the data are delivered already.
Expected behavior/output
How to setup an individual content element with extbase in TypoScript.
A description how to map incoming data in a renderAction() and display it without need for further queries.
Hybrid extbase extensions are thinkable / possible too, where content to be shown above list view or single view are entered in the content-record but also the plugin beside options.
Current behavior
extbase extensions all rely on data that are stored in special tables.
The case that the data are coming from the content record itself is not covered in the documentation.
An element like this would be a content element instead of plugin, but can be rendered with controller and view, the repository is in this scenario not used, as the data are delivered already.
Expected behavior/output
How to setup an individual content element with extbase in TypoScript.
A description how to map incoming data in a renderAction() and display it without need for further queries.
Links
https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/Extbase/Examples/Index.html
TYPO3 versions
[e.g. 11, 12] 11, 12, 13, main
The text was updated successfully, but these errors were encountered: