Hi Richard (and Ibrahim),
I have previously written a general high-level guide to troubleshooting 500 errors in this forum thread:
There is also our Troubleshooting documentation, here:
- You will generally need back-end / command-line access to resolve 500 errors. If you do not have this, talk to the IT person or system administrator responsible for installing and maintaining your AtoM instance
- With any 500 error, the first step we recommend is to get more information from the webserver error logs
- Many errors in AtoM can be resolved by restarting services and running some of AtoM's common maintenance tasks
- Of these, the only one I would definitely not run during business hours would be repopulating the search index, as this will temporarily make your data unavailable, and can take a while to run - even days for very large installations!
- If none of those work, sometimes the problem is due to data corruption - fortunately, AtoM now has a command-line task that can check for and even fix common forms of data corruption
In your specific case, if it is an issue with archival description hierarchies, then the nested set may be corrupted. I would recommend you:
- Rebuild the nested set
- Run the generate slugs task (in case any lower level descriptions are missing a slug for some reason)
- Clear the application cache
- Restart PHP-FPM and if you are using it, memcached
See if that resolves the issue. If it doesn't, and nothing in the links and suggestions above does (be sure to check that error log for further information), then reply back here with details from the error log, as well as a list of the steps you tried and what happened, and we'll see if I or another user here can provide any further suggestions for you.
Cheers,