Over the various versions of IPB forums and applications, one of the most significant challenges for self-hosted admins has been the lack of clarity in error messages. In the past, having error codes listed was incredibly helpful. They allowed me to identify issues quickly and resolve them without needing to open a support ticket. This saved considerable time—what might have taken an hour to fix on my own could otherwise take days of back-and-forth with support to resolve.

The current example of error handling isn’t very helpful for self-hosted admins. Previously, the error code lists provided a way to look up and address issues independently, which was invaluable. I’d like to request that this feature be restored to assist self-hosted admins in troubleshooting errors more efficiently.

Im not sure what else you would want from that, to be honest. Its a 404, page not found

We would go more down the road of making it more obvious what the issue is and better logging, than providing lists. You would be able to see things like this in system and error logs, which would give more detail where needed. But in the case of this one, the page simply doesnt exist

10 hours ago, Marc said:

Im not sure what else you would want from that, to be honest. Its a 404, page not found

We would go more down the road of making it more obvious what the issue is and better logging, than providing lists. You would be able to see things like this in system and error logs, which would give more detail where needed. But in the case of this one, the page simply doesnt exist

This is more about the subject content, not 100% on the image, given it the over all idea of being back the listing of error codes that were listing before it was taken away IPB 3.0 ish.

21 minutes ago, ZakRhyno said:

This is more about the subject content, not 100% on the image, given it the over all idea of being back the listing of error codes that were listing before it was taken away IPB 3.0 ish.

What more do you want to know about the error? All relevant information is logged in the Error or System logs from an administrator standpoint.

The error codes themselves really only are relevant to developers. At which point, the developers have access to the code and review what is calling those error codes so there is no need for a list.

The error codes are mostly for our reference. If, for instance, there is a bug causing an error to show inadvertently (such as a user not allowed to view a topic, however all of their permissions say that they can), then it gives us an easy and direct starting point for debugging. This is why we recommend contacting support if a user is experiencing an error and you’re not sure how to resolve it - we can either instruct on what to do, determine if there is a bug, or sometimes even determine the experience resolving the issue can be improved in the software itself, even if there is no technical issue present.

For day to day cases, the error message that is displayed should suffice. As Marc said, in your specific example, that is a generic 404 page indicating a page does not exist in the software at all.

The previous error code database really only contained the codes and the same message that was displayed or something generic like “user did not fill in all required fields”, with a few exceptions. In many cases, this is already handled within the software itself - if you encounter an error as an admin, it will sometimes give you instructions on what to check to resolve, if it’s relatively simple to do so (such as if there are no payment gateways set up). If a specific field is required, the form will not submit and tell the user, etc.