So you hit “Save” after crafting a new email in Mautic 7.2.1, and bam — a “500 Internal Server Error” stares you down. Frustrating, right? If this all started after upgrading your PHP to 8.4.27 and your host disabled PHP’s session.upload_progress.enabled, you’re not alone. This issue just popped up on the Mautic forums, and it’s worth a quick dive.
The error logs are telling: a PHP TypeError complaining that the FormBundle controller expected an integer but got a string. Then there’s a missing class error — Symfony\Component\DomCrawler\Crawler not found — during email validation. Both are good clues.
First, the string-vs-int mismatch hints at a bug or a compatibility hiccup. Mautic’s code expects an integer ID somewhere in the form preview logic, but it’s getting a string. That’s likely a type declaration issue surfaced by PHP 8.4’s stricter type checks. It usually calls for a patch or a workaround until Mautic updates fully adjust for PHP 8.4.
Second, the missing Symfony DomCrawler class suggests your environment might be missing a required dependency or that the autoloader is misfiring. This component is essential for Mautic’s email link validation, which runs when you save emails. Without DomCrawler, validation crashes — hello, 500 error.
Checking GitHub for related issues didn’t return a neat fix yet. This problem looks like an emerging PHP 8.4 compatibility snag combined with potential composer dependency issues. If you’re comfortable with command line, running composer install or composer update in your Mautic directory (if you manage your own instance) might restore the missing DomCrawler class.
But if your host restricts server settings like disabling session.upload_progress.enabled, that’s another wrinkle. Mautic relies on PHP sessions working correctly. Hosts tweaking these settings can break sessions, which in turn breaks forms, emails, and saving actions.
What’s the takeaway? If you’re running Mautic 7 on PHP 8.4 and hit this, it’s likely a combo of early PHP 8.4 teething problems plus missing dependencies or server limits. Keep a close eye on the official Mautic forums and GitHub for patches and updates. Meanwhile, consider downgrading PHP temporarily to 8.3.x or lower if you can, or reach out to your host about session settings. And of course, always keep your backups ready before you tweak versions or composer.
For those self-hosting, this is a solid reminder that Mautic’s cutting-edge upgrades can sometimes clash with rapidly evolving PHP versions and hosting quirks — it’s definitely not “set it and forget it.”
If managing all this sounds like a headache you don’t want? That’s where platforms like Mailertizer come in — we handle Mautic hosting, PHP updates, and compatibility so you can focus on your marketing, not troubleshooting.
Want to dive deeper into this thread and see community updates? Check out the original forum discussion here.