Looks very much like a failed database migration. Did you run the upgrade through shell or through the webinterface? In one case we supported, it was one single database issue, that could have been fixed with one single SQL statement
Hi thank you for your comment, as I mentioned in my post Ive updated using the dashboard feature.
Now we managed to somehow patch it up by removing the /app/cache content.
We are back up, however for some unknown reason I can’t access the components > forms section anymore, and on top of that I can’t seem to be able to send emails at all using the emails feature.
Clear the cache
There are several ways to do that. The easiest is to go to the /app/cache folder and delete its content. If you want to do it via CLI command, navigate to the Mautic root folder and run rm -rf app/cache/*. The new cache files will generate itself after the next Mautic refresh in the browser.
It might happen that the files won’t generate itself. It can be caused by the wrong folder permission and Mautic doesn’t have permission to write the new cache files. Contact your sysadmin and ask them to fix it for you.
Tip: Don’t execute Mautic commands as the root user yourself and do not run Mautic commands in the root crontab. This way all the files which will be created by the command will have the root as the author and Mautic won’t be able to rewrite those files.
Ive already tried step 1 delete cache though it doesn’t fix it.
ok assuming I can’t get hold of my sysadmin atm, how can I fix these permissions? Which ones shall I fix?
Here is the permission on that folder
/home/admin/web/mautic.designdiverso.com/public_html/app/cache/prod/doctrine/orm/Proxies/__CG__MauticPluginBundleEntityPlugin.php
we’ve managed to downgrade to 2.15.1 wasn’t that easy fight but in the end we prevailed.
I personally believe that open source sometimes can be tricky, for instance when a new buggy update is introduced there should a notification, somewhere within dashboard, mentioning (upgrade at your own risk) or something like that.