In any case, we will need to be reminded of more information about your installation to be able to provide suggestions. For example:
- Can you tell me the FULL version number, as listed in Admin > Settings, or returned when you run php symfony tools:get-version ?
- I can tell from the file path that you are using Apache instead of Nginx for your webserver. What other changes have you made from the recommended installation instructions?
- What version of PHP do you have installed?
- Does your AtoM installation meet the recommended minimum hardware requirements listed here? How much memory does your installation have?
Meanwhile, I recently created a roundup guide for resolving common 500 error issues. It includes a subsection on errors following an upgrade, that your team should review. See:
As noted there, the most common causes we have seen strange errors after upgrading are:
- Did not read the upgrade instructions at all and attempted to just "upgrade in place" by loading a new AToM tarball version on top of the old one
- Forgot to upgrade some dependencies (generally related to 1)
- Forgot to drop and recreate the database BEFORE loading the previous version's database dump
- Forgot to run the upgrade task AFTER loading the previous database dump
Please review the suggestions provided in that subsection. If those suggestions do not help you to resolve the issue, then hopefully with more information (i.e. the answers to the questions above) we can provide some additional suggestions to help get things working again!
Cheers,
@accesstomemory