#78450Introduce PreviewRenderer pattern
Description
A pattern should be introduced which replaces the old and somewhat messy (content) preview rendering hooks with a strategy that works not only for content and has increased capability to add things like wrapping. The current preview rendering can be moved to a standard implementation.
After this is done, the following should be considered:
- Deprecation of content preview hooks (schedule for complete removal)
- Extraction of fluid based preview rendering to a separate PreviewRenderer which can be reused and configured not only using pageTSconfig
The registration of PreviewRenderer should be performed in TCA and done in a way that allows one PreviewRenderer per CType and “record type”. And by creating a custom PreviewRendererResolver implementation it becomes possible to dynamically return renderer based on other record/table parameters.
Reviews 4
Related issues 6
- Task #90348PageLayoutView and BackendLayout should be refactored to separate rendering, processing and fetching of content
- Bug #90528Init more properties of PageLayoutView in StandardContentPreviewRenderer
- Bug #90554Access to an undefined property TYPO3\CMS\Backend\Preview\StandardContentPreviewRenderer::$record.
- Bug #90556TYPO3 Exception: htmlspecialchars() expects parameter 1 to be string, null given
- Bug #90598Initialize emulated PageLayoutView before calling hooks
- Bug #91920Fluid Plugin Preview of extensions not possible by TSconfig