"Something Has Gone Wrong" Error
The "Something has gone wrong" message is standard 'generic error message' that Vanilla serves when something unexpected happens. From it, we can determine:
- Issue is likely originating from Vanilla
- Something has gone wrong
By itself, it doesn't offer a ton of information but using the Debug function on the client's Console page, we can get an idea of what is causing the problem. The best practice here is the following:
- Keep 'Something has gone wrong' error up in it's own tab.
- In another tab, open the Console page for the community you're seeing the error in.
- Hit 'Debug Mode'
4) In the browser tab with the error present, reload the page. It should show you something like the following:
5) Turn off "Debug Mode" in the Console page
The cause of the error can best be determined by the top-most information (everything above the 'Backtrace' section). In this example, the issue will likely need dev attention. In some cases though, the error will seem to indicate a conflict with a certain addon being active, or an issue with something in theme or sometimes a database issue.
Some of these can be acted on by Support Agents simply by turning off or resolving whatever is causing the conflict.
In cases where the issue is database related (look for "Missing Table" or "Missing Column" in the error), it can sometimes be resolved by running a utility update on that client's site.
In cases where a Support Agent is unable to resolve the issue on their own, when making a ticket for the Support Devs, include a screenshot of the error message that comes up with Debug Mode. That is significantly more helpful than the generic 'Something has gone wrong' error. Also make sure you include exact replication steps for how the 'Something has gone wrong' error was triggered, so the devs can get to it on their own.