Browsing Hebrew translation

92.

You can combine the targets with bitwise operations, e.g. ``LOG_TARGET_SCREEN | LOG_TARGET_ERRORLOG``.

93.

log_file: File containing error messages

94.

``$cfg->log_file = '/path/to/dataroot/error.log';``

95.

If you use LOG_TARGET_FILE, this is the file to which errors will be logged. By default, it will write to the file ``error.log`` under the dataroot. If you change this in config.php, make sure you use a folder which is writable by the web server.

96.

log_backtrace_levels: Log backtraces

97.

For example: ``$cfg->log_backtrace_levels = LOG_LEVEL_WARN | LOG_LEVEL_ENVIRON;`` (default)

98.

The log levels that will generate backtraces. Useful for development, but probably only warnings are useful on a live site.

99.

log_backtrace_print_args: Log backtraces

100.

``$cfg->log_backtrace_print_args = null;`` (default)

101.

Print the values of function and method arguments when printing a backtrace. This can be useful for debugging, but it is a security risk because function parameters may include sensitive data such as passwords and private keys. Though arguments whose names suggest that they contain passwords, will still be blanked out even if this feature is enabled.