TYPO3 14.2: Automatically check fluid templates for errors with fluid:analyse

TYPO3 14 comes with a new CLI command that makes your life much easier during migration: fluid:analyze automatically checks your Fluid templates for syntax errors and deprecations.

The problem: Hidden errors in templates

Anyone who has ever migrated a major project to a new TYPO3 version will be familiar with this: Fluid templates that have worked for years suddenly start throwing errors. Maybe even weeks after the go-live, when an editor calls up a rarely used template.

With Fluid 5 in TYPO3 14, there are some breaking changes that can cause exactly such hidden problems. Manually searching through all templates is tedious and error-prone.

The solution: One command for all templates

The new fluid:analyze command automatically searches through all fluid templates in your project and reports

• Syntax errors (invalid tag nesting, missing attributes)
• Invalid ViewHelpers or namespaces
• Forbidden variable names (with leading underscore)
• Deprecations of ViewHelpers or arguments

vendor/bin/typo3 fluid:analyze

The output shows you directly where the problem lies:

[DEPRECATION] packages/myext/Resources/Private/Templates/Test.fluid.html: <my:obsolete> has been deprecated in X and will be removed in Y.
[ERROR] packages/myext/Resources/Private/Templates/Test2.fluid.html: Variable identifiers cannot start with a "_": _temp

Perfect for CI/CD pipelines

The command is deliberately designed to be CI-friendly:

• Exit code 1 only for real errors
• Exit code 0 for deprecations (warnings, but no hard error)

This allows you to integrate the check into your pipeline without deprecations from third-party extensions blocking your build.

What is checked?

The command automatically finds all templates with the new file extension *.fluid.*. So if you have already switched to the new Fluid file extension, you will benefit immediately.

The check for variable names with a leading underscore is particularly valuable. These are no longer permitted in Fluid 5 because they are reserved for internal purposes. A frequent stumbling block during migration, which the command reliably detects.

Connection with other Fluid 5 changes

The fluid:analyze command is the central tool for finding the breaking changes from Fluid 5 in your project. I have already summarized the most important changes in my article on Fluid 5 breaking changes. With fluid:analyse, you can now automatically check whether your project is affected.

Source: Changelog "Feature: #108763 - Console command to analyze Fluid templates"

Conclusion

The new fluid:analyse command is a small but powerful tool for migrating to TYPO3 14. It saves time, finds hidden problems and can be seamlessly integrated into CI/CD workflows.

By the way: I'm currently working on the TYPO3 Complete Course with a flexible access model that will be updated with every new TYPO3 version. If you want to be the first to know when it starts and get the discounted introductory price, sign up for the waiting list.