Browsing Yiddish translation

177.

If you have a multi-tenanted Mahara instance but do not want people from the individual institutions to communicate on the site or share groups, you can turn on 'Isolated institutions'.

178.

This can be beneficial when you set up a large site for several organisations and need to adhere to privacy regulations that don't allow people from one organisation to contact people from other organisations.

179.

See the section :ref:`'Isolated institutions' <isolated_institutions>` for more information.

180.

log_backtrace_levels: Log backtraces

181.

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

182.

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

183.

log_backtrace_print_args: Log backtraces

184.

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

185.

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.

186.

A ``null`` value here tells Mahara to hide argument values when ``$cfg->productionmode`` is enabled, and to show them otherwise. A ``true`` or ``false`` tells Mahara to always show or hide argument values in backtraces regardless of the value of ``$cfg->productionmode``.