Community Budget Report: Rector and Fractor Updates for TYPO3 v14

In the final quarter of 2025, ahead of the TYPO3 v14.0 release, my community budget proposal was about how I wanted to create as many rules as possible to cover the deprecations and breaking changes introduced in TYPO3 v14, while also extending Fractor with new features and rules.

I had big goals planned as the list of deprecations and breaking changes was long, but just in time I was able to close all issues tagged with v14.0 (106 issues), and create 45 new rules for a smooth TYPO3 v14 migration plus a few others.

One of these additions was a new code quality rule requested by Core team member, Georg Ringer, that makes maintaining his News system (news) extension easier. The rule is useful for extension developers who want to be compatible with two (or more) different TYPO3 versions at the same time, as it removes the compatibility layer for a specific version.

If you have an idea for a new Rector rule that would help your own projects, feel free to create an issue in the GitHub repository.

Check Out the Overview of All the Rector Rules

Find the completed TYPO3 Rector milestone here: Funding for implementing Rector & Fractor rules Q4/2025

Fractor (the code migration tool for file types other than PHP) also received some great new features that makes working with the tool more enjoyable and flexible.

In addition to these features, a number of new rules were created specifically for upgrading to TYPO3 v14. A total of 18 issues were closed for this milestone, out of which 11 are new rules for TYPO3 v14.

Several new cli parameters are now available. For example, the --no-progress-bar option hides the progress bar, which is useful for CI integration. 

Another addition is the --only parameter that makes it possible to run a single rule from a set that is configured in the settings file. Combined with the new --output-format parameter, this enables workflows such as generating a list of rules in JSON format, running each rule individually, and creating separate commits per rule. I have such a script running already and can share it if requested.

Finally, there is a new script available that creates an initial config file for Fractor. If you run Fractor without any configuration, Fractor will offer to create a configuration file but that file is very generic. If you want to create an initial config file tailored specifically for a TYPO3 project, you can run the command vendor/bin/typo3-fractor-init.

Check Out the Overview of All the Fractor Rules

Find the completed Fractor milestone here: Funding for implementing Rector & Fractor rules Q4/2025