The format for HTML errors produces clickable messages that direct the user to a page describing the error or function in causing the error.
These references are affected by docref_root and docref_ext.
In case of manual pages you can download the manual in your language and set this ini directive to the URL of your local copy.
If your local copy of the manual can be reached by Note: This is a feature to support your development since it makes it easy to lookup a function description.
However it should never be used on production systems (e.g. at the top of your script will not catch any parse errors.
For debugging purposes: NOTICE messages will warn you about possible bugs in your code. It is extremely useful to find typos and to save time for debugging. These messages may include things such as calling non-static methods statically, defining properties in a compatible class definition while defined in a used trait, and prior to PHP 5.3 some deprecated features would issue Set the maximum length of log_errors in bytes.
STRICT messages provide suggestions that can help ensure the best interoperability and forward compatibility of your code.
In error_log information about the source is added.
The default is 1024 and 0 allows to not apply any maximum length at all.
This length is applied to logged errors, displayed errors and also to If this parameter is set to On (the default), this parameter will show a report of memory leaks detected by the Zend memory manager.
This report will be send to stderr on Posix platforms.
On Windows, it will be send to the debugger using Output Debug String(), and can be viewed with tools like » Dbg View.
This parameter only has effect in a debug build, and if error_reporting includes If enabled, error messages will include HTML tags.