How to migrate away from fluidpages

If you want to upgrade a fluidpages dependent website to TYPO3 v10, you will notice that there is no version of fluidpages compatible with TYPO3 v10.

You have to remove the fluidpages extension and render your website without it. That is what I will be showing in this article.

This article was tested on a TYPO3 v9.5 instance with flux version 9.4.2

Update flux extension

• Make sure to backup your project files and database so you can easily recover in case anything goes wrong.
• Go to the TER (TYPO3 Extension Repository), search and download the latest version the flux extension. At the time of writing, it was version 9.4.2.
• Extract the zip file to the typo3conf/ext/ folder of your project.
• Delete or rename the existing flux folder and rename the extracted folder to flux.
• Flux is now updated. You can check the version in the ADMIN TOOLS > Extensions module.

If you get a “……. Unknown column ‘tx_fed_page_controller_action’ in field list” kind of error after the flux update, go to the ADMIN TOOLS > Maintenance module. Then, click on the Analyze database button.

From there, you can add the required fields and/or columns to the database.

Remove fluidpages dependency in extensions

Now remove the dependency on fluidpages from extensions that depend on it so it can be deactivated and deleted from the TYPO3 instance.

• To see the extensions which are dependent on fluidpages,
  • Open the ADMIN TOOLS > Extensions module and search for fluidpages on this page.
  • On the row of the fluidpages extension, click on the icon.
  • You will see a “Cannot deactivate extension ‘fluidpages’ – The extension(s) ‘……..’ depend on it.” error. In this message are the list of extensions which depend on fluidpages.
  • Note down these extensions because they will be deactivated after you deactivate fluidpages and you will have to activate them again.

• For each of these extensions,
  • Open the ext_emconf.php file (found in the extension’s root directory).
  • Remove the fluidpages item from the “$EM_CONF[$_EXTKEY]['constraints']['depends']” array.
• Next, deactivate and delete the fluidpages extension.

Execute the flux update script

This migration script just updates the “backend_layout” or “backend_layout_next_level” fields of page records where the values are “fluidpages__grid” or “fluidpages__fluidpages” to the value “flux__grid“.

• Open the ADMIN TOOLS > Extensions module and search for flux on this page.
• On the far right of the flux extension row, click on the icon to start the migration/update process.
• Click on “Perform migration” button.
• You will now see the migration results indicating a successful migration.

Activate the extensions that were dependent on fluidpages and test

Like I said earlier, the extensions which were dependent on fluidpages were deactivated after deactivating the fluidpages extension.

Now, activate all those extensions and test your work.

You can test by just opening some pages from the page tree in the WEB > Page module, checking the backend layouts and also the display on the frontend.

Everything should display/work exactly as it was before you removed the fluidpages extension.

So, that’s it for this article. I hope it was of help to you. If you encountered problems let me know in the comments.