Error Codes Conventions

[Kevin Carwile]

What are the new conventions for error codes in IPB 4.0? They don't appear to follow along the same lines as they did in 3.x per the documentation at: https://www.invisionpower.com/support/guides/_/advanced-and-developers/api-methods/showing-errors-r184

[Mark]

ABXXX/Z

A = Severity

Severity	Description	Examples
1	User does something that is not allowed. Can happen in normal use.	User did not fill in a required form element.
2	Action cannot be performed. Will not happen in normal clicking around, but may happen if a URL is shared.	User does not have permission to access requested page; Page doesn't exist.
3	Action cannot be performed. Will not happen in normal use.	Secure key doesn't match; User submitted a value for a select box that wasn't in the select box.
4	Configuration error that may happen if the admin hasn't set things up properly.	Uploads directory isn't writable; Facebook application data was rejected.
5	Any error that should never happen.	No login modules exist; Module doesn't have a defined default section.

 

B = A single character representing the application.

 

XXX = A 3-digit number which represents the class. Starting with 100, it's just in the order we created them. We have a script which keeps track of them.

 

Z = A number or letter representing the error within that class. Starting at 1, when we get to 9, we then go A-Z.

[TSP]

 

Could you get this into the documentation section? I was looking for this and I first spent 5-10 minutes trying to find it in the doc section, before I eventually managed to find it by a search.