Error reports to the developer
What the engine sends the developer when it hits an error in its own code, what it never sends and how to turn it off.
When the engine itself (or a module or theme that ships with it) hits an error, it can send the developer a short anonymous report. Such reports help find and fix errors faster. It is on by default and turns off with one switch.
What is sent
Once a day, in the background, after visitors have been answered:- the engine and PHP versions and, if the error is in one of our modules, the module version;
- the error class (for example PDOException);
- the file and line inside the engine or its modules and up to six lines of the call chain from there;
- the error code (the same as in the log), the day and how many times it happened that day;
- a random installation number, used only to count how many different sites met the same error; it is not derived from your address, keys or database.
What is never sent
- the site address;
- the text of the error message (the engine does not even read it for the report: it can hold data);
- requests and their parameters, variable values, cookies;
- paths outside the engine, visitors, users, page and entry content;
- errors in third-party modules and themes (those not signed by us) at all.
See what will be sent
“Diagnostics → Error reports” shows whether it is on, how many errors are waiting and exactly the JSON that will go out. While nothing is waiting, it shows a sample with made-up values.Turn it off
In the installation wizard the “Send error reports to the developer” box is ticked by default and can be cleared. Afterwards: “Site settings → Updates → Send error reports to the developer”. Turning it off wipes the queue of unsent reports and deletes the installation number; turning it on again makes a new one.On development copies (a local address, debug mode) reports are never sent.