With the additional extension EXT:flux you can quickly and flexibly create your own content elements and page layouts with pure fluid templating markup. Up to now, the extensions EXT:fluidcontent and EXT:fluidpages were additionally required. In EXT:flux 8 the extension EXT:fluidcontent was no longer necessary, about which we have already written a blog article, but now the extension EXT:fluidpages is up for grabs!
More about the EXT:fluidpages technology itself can be found at https://fluidtypo3.org/documentation/templating-manual/templating/creating-templates/page-template.html.
Now version 9.3 of EXT:flux announced that you can provide page layouts without EXT:fluidpages. Instead, the development of EXT:fluidpages will be stopped. This means that the migration away from EXT:fluidpages is also relevant when updating to TYPO3 version 10. Here we will show you how to free an existing project from EXT:fluidpages and how to use EXT:flux to provide your page layouts. In the following code examples we assume that all elements are bundled in a provider or sitepackage extension "EXT:template" with the vendor name AEMKA. As with any system-technical intervention, we recommend a backup of the file system and database of the TYPO3 installation in advance. It was tested with version 9.3.2 of EXT:flux under TYPO3 CMS 9.5.18.
As soon as you update from e.g. EXT:flux 9.2 to 9.3, there are currently still a few small problems and necessary adjustments, which are partly also discussed in this ticket: https://github.com/FluidTYPO3/flux/issues/1742:
It may be necessary to make a database adjustment in the admin tools (formerly Install Tool) after the extension update and to create new fields in the database, empty the system and Autoload cache. After that you can use EXT:flux 9.2. See also https://github.com/FluidTYPO3/flux/issues/1740.
A new feature in this EXT:flux version is also the automatic creation of template folders, called "plug-and-play templates". You can disable this feature in the settings of the extension under "Admin Tools" > "Settings" and then delete the automatically created "design" folder in the Webroot.
By the way, if you do not want to use EXT:fluidpages based page layouts with EXT:flux 9.3, you have to empty the object "page.5" in the Typoscript setup:
page.5 >
If you have used EXT:fluipdages based page layouts up to now, you have to set the "Columns from selected "Page Layout"" value in the page properties under "Backend-Layout (only for this page)" and "Backend-Layout (for subpages of this page)" in EXT:flux version 9.3 without EXT:fluidpages. The value of EXT:fluidpages previously used here no longer works.
It even looks like there will be a migration wizard for this soon: https://github.com/FluidTYPO3/flux/commit/89f1dbf29ba449450d5ddc5e0f18e20e504eafbc.
If you have written a php controller to change data of your EXT:fluidpages page layout, you have to change the class name of the inherited php class from
\FluidTYPO3\Fluidpages\Controller\PageController
to:
\FluidTYPO3\Flux\Controller\PageController
If all these steps are followed, you can uninstall and delete EXT:fluidpages, as long as it is not a dependency of the provider extension. The previous registration of EXT:fluidpages page layouts per line:
\FluidTYPO3\Flux\Core::registerProviderExtensionKey('AEMKA.Template', 'Page');
in the ext_localconf.php remains the same.
You can get rid of one more extension in the system again. In addition, the development on EXT:fluidpages has also been stopped and will no longer be available for TYPO3 CMS 10, so it is another preparatory step for the update to the upcoming LTS version of TYPO3 CMS.
