[2024-02-22T07:56:15.568696+00:00] mautic.CRITICAL: Uncaught PHP Exception Twig\Error\RuntimeError: "An exception has been thrown during the rendering of a template ("Mautic\CoreBundle\Twig\Extension\ContentExtension::getCustomContent(): Argument #2 ($vars) must be of type array, bool given, called in /var/www/html/newsletter/var/tmp/twig/6f/6fccdec65d4eb4f8ce60c19b2ea0f04f.php on line 404")." at /var/www/html/newsletter/docroot/app/bundles/EmailBundle/Resources/views/Email/details.html.twig line 251 {"exception":"[object] (Twig\\Error\\RuntimeError(code: 0): An exception has been thrown during the rendering of a template (\"Mautic\\CoreBundle\\Twig\\Extension\\ContentExtension::getCustomContent(): Argument #2 ($vars) must be of type array, bool given, called in /var/www/html/newsletter/var/tmp/twig/6f/6fccdec65d4eb4f8ce60c19b2ea0f04f.php on line 404\"). at /var/www/html/newsletter/docroot/app/bundles/EmailBundle/Resources/views/Email/details.html.twig:251)\n[previous exception] [object] (TypeError(code: 0): Mautic\\CoreBundle\\Twig\\Extension\\ContentExtention::getCustomContent(): Argument #2 ($vars) must be of type array, bool given, called in /var/www/html/newsletter/var/tmp/twig/6f/6fccdec65d4eb4f8ce60c19b2ea0f04f.php on line 404 at /var/www/html/newsletter/docroot/app/bundles/CoreBundle/Twig/Extension/ContentExtension.php:33)"} {"hostname":"prod-usa-newsletter","pid":2084194}
Hi @mzagmajster ,
the grapeJS plugin is enabled and I tried all the template, the result is the same.
I tried reinstall the vendor packages but I don’t know if it is right because nothing changed… same problem:
Reading from those tutorials and no surprise that the upgrade failed.
First tutorial is making the installation using the wrong user. But then recover by doing a “chown www-data:”
Same for the second one (and in your case, most likely the one that blew it all up).
What is missing in those How To is either adding ‘su -e www-data “cmd in the how to”’ or, in the case of the second How To, doing a “chown www-data: /var/www/html -R”
Failing to do so is creating root owned files which are write protected against www-data user. Thus generating a 500 when www-data tries to edit those files.