Here's a short explanation of
the configuration directives.
Set the error reporting level. The parameter is either an integer
representing a bit field, or named constants. The error_reporting
levels and constants are described in
and in php.ini. To set at runtime, use the
error_reporting() function. See also the
PHP 5.3 or later, the default value
E_DEPRECATED. This setting does not
E_DEPRECATED level errors. You may want
to show them during development.
Prior to PHP 5.3.0, the default value
In PHP 4 the default value is
E_NOTICE during development has
some benefits. For debugging purposes: NOTICE messages will warn you
about possible bugs in your code. For example, use of unassigned values
is warned. It is extremely useful to find typos and
to save time for debugging. NOTICE messages will warn you about bad style.
For example, $arr[item] is better to be written as
$arr['item'] since PHP tries to treat
"item" as constant. If it is not a constant, PHP assumes
it is a string index for the array.
In PHP 5 a new error level
E_STRICT is available.
Prior to PHP 5.4.0
E_STRICT was not included within
E_ALL, so you would have to explicitly enable this kind of
error level in PHP < 5.4.0. Enabling
E_STRICT during development
has some benefits. STRICT messages provide suggestions that can help
ensure the best interoperability and forward compatibility of your code.
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
E_STRICT errors such as assigning
objects by reference upon instantiation.
PHP Constants outside of PHP
Using PHP Constants outside of PHP, like in httpd.conf,
will have no useful meaning so in such cases the integer values
are required. And since error levels will be added over time, the maximum
E_ALL) will likely change. So in place of
E_ALL consider using a larger value to cover all bit
fields from now and well into the future, a numeric value like
2147483647 (includes all errors, not just
This determines whether errors should be printed to the screen
as part of the output or if they should be hidden from the user.
Value "stderr" sends the errors to stderr
instead of stdout. The value is available as of PHP
5.2.4. In earlier versions, this directive was of type boolean.
This is a feature to support your development and should never be used
on production systems (e.g. systems connected to the internet).
Although display_errors may be set at runtime (with ini_set()),
it won't have any effect if the script has fatal errors.
This is because the desired runtime action does not get executed.
Even when display_errors is on, errors that occur during PHP's startup
sequence are not displayed. It's strongly recommended to keep
display_startup_errors off, except for debugging.
Tells whether script error messages should be logged to the
server's error log or error_log.
This option is thus server-specific.
You're strongly advised to use error logging in place of
error displaying on production web sites.
Set the maximum length of log_errors in bytes. 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
$php_errormsg, but not to explicitly called functions
such as error_log()().
When an integer is used, the
value is measured in bytes. Shorthand notation, as described
in this FAQ, may also be used.
Do not log repeated messages. Repeated errors must occur in the same
file on the same line unless
is set true.
Ignore source of message when ignoring repeated messages. When this setting
is On you will not log errors with repeated messages from different files or
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 OutputDebugString(), and can be viewed with tools
like » DbgView.
This parameter only has effect in a debug build, and if
E_WARNING in the allowed
If enabled, the last error message will always be present in the
If enabled, error messages will include HTML tags. 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
If disabled, error message will be solely plain text.
If enabled, turns off normal error reporting and formats errors as
XML-RPC error message.
Used as the value of the XML-RPC faultCode element.
The new error format contains a reference to a page describing the error or
function causing the error. 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 "/manual/"
you can simply use
docref_root=/manual/. Additional you have
to set docref_ext to match the fileextensions of your copy
docref_ext=.html. It is possible to use external
references. For example you can use
Most of the time you want the docref_root value to end with a slash "/".
But see the second example above which does not have nor need it.
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. systems connected to the internet).
The value of docref_ext must begin with a dot ".".
String to output before an error message.
String to output after an error message.
Name of the file where script errors should be logged. The file should
be writable by the web server's user. If the
special value syslog is used, the errors
are sent to the system logger instead. On Unix, this means
syslog(3) and on Windows NT it means the event log. The
system logger is not supported on Windows 95. See also:
If this directive is not set, errors are sent to the SAPI error logger.
For example, it is an error log in Apache or stderr
See also error_log().