Review main Abandoned

62318[WIP][FEATURE] Introduce FLUIDPAGE frontend page generation

Benni Mack CR 0 V 0 Expert +1132 −894 updated 10/20/21, 09:10

Commit message

In recent TYPO3 versions, the concepts of dataProcessors
(= preprocess and prepare data delivered to the view) and FLUID-based
content elements have become very popular.

Now, in order to give integrators a more flexible way to have
control of a full page, the full page content generation is moved
into a custom class, which now can have "PAGE" or "FLUIDPAGE".

This is now possible to have full control over the delivered contents:

page = FLUIDPAGE
page.templateRootPaths.10 = EXT:myextension/Resources/Private/Pages/Templates
page.layoutRootPaths.10 = EXT:myextension/Resources/Private/Pages/Layouts
page.variables.pages = 123
page.dataProcessors.20 = MenuProcessor...

When going the "FLUIDPAGE" way, all the TypoScript options like includeCSS
and includeJS are not applied anymore - for consistency reasons in order
to have Fluid-lovers to use Fluid as much as possible.

Still open and ToDo:
- Add tests
- Implement data processors
- Test uncached handling WITHIN fluid
- Restrucute PageRenderer to have a string as template, and get rid of some old dust, ensure that the Template Files do not contain markers anymore
- Possibly add ViewHelpers for adding JS/CSS/Resources/MetaTags
- Cache response object in cache_pages and work with response/stream instead of TSFE->content
- Introduce .format or .contentType option to automatically apply this to the response object directly.
- Move adding headers to the building functionality of a PageGenerator
- Find a cool way to render content in a usable way. ContentDataProcessor?

Review

  • Code review CR 0

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V 0

    Imported before Forger kept the single votes, the next import adds them.

Files 8