DevKit

Error Log

  1. Reload Error Log
  2. Date and Time of the log update
  3. Error log content
  4. Clear log
error log
1
2
3
4

Reload Error Log

Instead of reloading the entire browser, we have added the CTRL (Command) + R shortcut to help you refresh the list.

Date and Time

To ensure the log is up-to-date, we have added the date and time of the latest update to the log.

Error log content

By default, the error log is a file located on your server. To access it, you would need FTP access or an FTP plugin. You have to locate, download, and open the file. Since the error log is constantly updating, it’s much easier to have it displayed within WordPress, with updates visible upon page reload.

In the section title, you can also see a timestamp indicating the last update. This timestamp does not change on reload. It only updates if something happens in your WordPress that triggers a notification and update in the error log.

Clear error log

Error logs can grow very long very quickly, making them difficult to manage. That’s why we have added an option to clear the log.

Filter Error Log

Error log can long and messy.
Under settings you can select what error log type you want to read.

E_ALLAll errors and warnings, as supported. This includes all error types except E_STRICT prior to PHP 5.4.0.
E_ERRORFatal runtime errors. These indicate errors that cannot be recovered from, such as a memory allocation problem.
E_WARNINGRuntime warnings (non-fatal errors). Execution of the script is not halted.
E_PARSECompile-time parse errors. Parse errors should only be generated by the parser.
E_NOTICERuntime notices. Indicate something that could be an error but could also happen in the normal course of running a script.
E_CORE_ERRORFatal errors that occur during PHP’s initial startup. This is like E_ERROR, but it is generated by the core of PHP.
E_CORE_WARNINGWarnings (non-fatal errors) that occur during PHP’s initial startup. This is like E_WARNING, but it is generated by the core of PHP.
E_COMPILE_ERRORFatal compile-time errors. This is like E_ERROR, but it is generated by the Zend Scripting Engine.
E_COMPILE_WARNINGCompile-time warnings (non-fatal errors). This is like E_WARNING, but it is generated by the Zend Scripting Engine.
E_USER_ERRORUser-generated error message. This is like E_ERROR, but it is generated in PHP code using the function trigger_error().
E_USER_WARNINGUser-generated warning message. This is like E_WARNING, but it is generated in PHP code using the function trigger_error().
E_USER_NOTICEUser-generated notice message. This is like E_NOTICE, but it is generated in PHP code using the function trigger_error().
E_STRICTEnable to have PHP suggest changes to your code which will ensure the best interoperability and forward compatibility of your code.
E_RECOVERABLE_ERRORCatchable fatal error. It indicates that a potentially dangerous error occurred, but did not leave the Engine in an unstable state.
E_DEPRECATEDRun-time notices. Enable this to receive warnings about code that will not work in future versions of PHP.
E_USER_DEPRECATEDUser-generated warning message. This is like E_DEPRECATED, but it is generated in PHP code using the function trigger_error().

Table of Contents