Uncaught TYPO3 Exception: Too few arguments to function TYPO3\CMS\Redirects\Service\SlugService::__construct()

[seirerman]

I just upgraded TYPO3 from 13.4.24 to 13.4.25 (sluggi 13.0.3, no update to 14.x yet) and noticed an uncaught exception when clearing all caches (red bolt) via header dropdown menu:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Too few arguments to function TYPO3\CMS\Redirects\Service\SlugService::__construct(), 7 passed in /var/html/vendor/wazum/sluggi/Classes/Service/SlugService.php on line 30 and exactly 8 expected | ArgumentCountError thrown in file /var/html/vendor/typo3/cms-redirects/Classes/Service/SlugService.php in line 67. Requested URL: https://www.domain.com/typo3/record/commit?token=--AnonymizedToken--&cacheCmd=all

After downgrading to TYPO3 13.4.24 clearing all caches works fine, without any errors.

For some reason clearing the caches in the install tool works fine, though.

[wazum]

@seirerman
thanks for the report,
this is due this Core change here: TYPO3/typo3@6a16c5ac313
Please try the 14+ version and play around with it (should be a drop-in replacement with all existing features + a lot more), and I'll see if I can do something (one last time) for the old version 13 too.

[seirerman]

Thanks, I'll check out sluggi 14.x ASAP.

I also found out that I can't create new pages with TYPO3 13.4.25 and sluggi 13.0.1, so I have to downgrade to 13.4.24 for now.

[wazum]

@seirerman thanks for checking! I've been thinking about this over the weekend and I've decided not to backport fixes to the v13 branch anymore. The TYPO3 core change that broke the SlugService constructor is just one example — keeping up with core changes across multiple major versions has become unsustainable.

My recommendation: upgrade to sluggi v14 — it's a drop-in replacement and already handles the new SlugService signature. It also brings a lot of improvements like better conflict handling, redirect control, and more.

If you do make the switch, I'd really appreciate any feedback from real-world usage. Bug reports, edge cases, things that feel off — all of it helps. The more battle-tested it gets in production, the better it becomes for everyone.

For now, please pin TYPO3 to 13.4.24 if you need to stay on sluggi v13.