The fluidpages package from FluidTYPO3
Installs: 239 040
- php: >=7.1.0
- fluidtypo3/flux: ^9.0 | dev-development
- typo3/cms-backend: ^8.7 | ^9 | dev-master
- typo3/cms-core: ^8.7 | ^9 | dev-master
- typo3/cms-fluid: ^8.7 | ^9 | dev-master
- typo3/cms-frontend: ^8.7 | ^9 | dev-master
- typo3/cms-recordlist: ^8.7 | ^9 | dev-master
- fluidtypo3/development: ^4.0
- fluidtypo3/flux: dev-development
- fluidtypo3/fluidcontent: Gives the ability to render custom content elements with pure fluid.
- fluidtypo3/fluidcontent_core: Gives the ability to render core content elements with pure fluid.
This package is auto-updated.
Last update: 2023-03-17 19:21:43 UTC
Fluidpages: Fluid Page Templates
OBSOLETE - functionality now served by Flux
What does it do?
EXT:fluidpages enables the use of Fluid templates as page templates, each template file acting like an individual template. The template files are processed by the extension and a simplified method of selecting templates (two selector boxes, one for current page and one for subpage templates, like TemplaVoila).
Why use it?
Although the FLUIDTEMPLATE object in TypoScript allows Fluid templates to be used as page templates, it has limited capabilities. Using EXT:fluidpages the page templates are not only selectable in page properties but also rendered from a proper Controller.
In addition to this, Fluid Pages uses all the power of Flux to allow the template to contain dynamic but very compact configuration sections - which translate to fields in the page properties, the values of which are available when rendering the template.
When combined with the VHS extension this becomes a very powerful tool: the dynamic nature of Fluid templates and the flexibility of ViewHelpers - combined with extremely easy-to-use configuration options.
How does it work?
Fluid Pages are registered through TypoScript. The template files are then processed and the configuration contained in each is recorded and used to identify the page template when being selected by content editors.
When editing the page a Flux ConfigurationProvider takes care of processing the specific template's configuration and presenting it as fields available to the content editor much like TemplaVoila.
View the online templating manual for more information.
Installation using Composer
The recommended way to install the extension is by using Composer. In your Composer based TYPO3 project root, just do
composer require fluidtypo3/fluidpages.
Installation as extension from TYPO3 Extension Repository (TER)
Download and install as TYPO3 extension. Search for the term