Translations by Masayuki Kuwada

The administration in Mahara is reserved for site and institution administrators. Configuration settings and functionalities that are only available to site administrators with full privileges are marked as such.

The ``config.php`` file sits in the ``/htdocs`` directory of your site. If you want to view all possible variables and their default values, you can find them in ``/htdocs/lib/config-defaults.php``. You can overwrite any default values by placing the variable in your ``config.php`` file.

A configuration variable needs to be written in the correct syntax in order to function. In Mahara, this is done the following way: ``$cfg->variable = value;``.

**variable =**: Here you see the variable that is to be set. Generally, it consists of one word, or words are joined together with underscores. The variable cannot contain any spaces.

**value;**: The value that the variable takes is displayed. The values can be different things, for example:

``$cfg->openbadgedisplayer_source = '{"shortname":"url","shortname":"url"}';``

remoteavatarbaseurl: Remote avatar server URL

The site administrator can decide to add "Copy of..." for copied pages and collections. If ``$cfg->renamecopies = true;``, copies of new pages and collections will have "Copy of" prepended to their titles. The default setting is ``$cfg->renamecopies = false;``.

sitethemeprefs: Choose your browse theme from any theme

If the site administrator allowed it, you can choose any theme that is available to you as your browse theme on your :ref:`"Account settings" <general_account_options>` page. In that case, you are not restricted to only use your institution theme or if you are a member of multiple institutions choose between them.

You can allow your users to personalise their portfolio pages beyond choosing a theme. This is done via :ref:`skins <skins>` in Mahara. Skins can be created on the :ref:`site level <site_skins>` or by individuals. Institutions can :ref:`allow or deny the use of skins <add_institution>` for their users.

Without this configuration variable, anybody can run the cron job (scheduled tasks) on your site or an upgrade potentially causing problems.

*Configure site* is only accessible by site administrators.

In *Configure site* you can:

set general parameters for your Mahara site

In *Site options* you can set global options that will apply by default throughout the entire site.

One or more fields may be disabled if overridden by a setting in your config.php file.

When you are done editing one or more settings, click the *Update site options* button at the bottom of the page.

**Site name**: Choose a name for your Mahara instance. It appears in certain places around the site, e.g. in the title bar of the browser and in emails sent from the site. Therefore, it should not be too long.

**Language**: Set the default language for your site. If you have multiple language packs installed, you see a drop-down menu. Otherwise, the standard language, English, is displayed.

**Country**: The country selected is the default for country selections throughout your Mahara installation, e.g. in :ref:`contact information <contact_info>`.

**Theme**: Mahara comes with a number of themes that you can use. Choose one from the drop-down menu to make it the default theme for your site. If you have :ref:`institutions <site_admin_institutions>` set up, they can :ref:`choose their own theme <add_institution>`. You can `search for community-contributed themes <https://wiki.mahara.org/index.php/Themes/Contributed_themes>`_ on the Mahara wiki.

**Drop-down navigation**: If set to "Yes", the main Mahara navigation uses a drop-down menu for its subnavigation.

When you change this setting, you need to re-index the search index for the change to take effect.

**Staff statistics access**: If set to "Yes", institution staff will have access to the statistics for users in their institutions. This is normally restricted to administrators and site staff.

You can configure the internal search plugin in the :ref:`administration of the search plugin <plugin_search>`.

**Confirm registration**: :index:`If set to "Yes", administrators <single: Confirm registration site-wide>` cannot make the *Confirm registration* setting optional when :ref:`configuring an institution <add_institution>`. This prevents institution administrators from disabling this setting when it is required site-wide to not allow user accounts to be created without administrator approval.

**reCAPTCHA site key**: Enter the site key for your site's reCAPTCHA account.

**reCAPTCHA secret key**: Enter the secret key for your site's reCAPTCHA account.

**Proxy address**: If your site uses a proxy server to access the Internet, specify the proxy in ``hostname:portnumber`` notation.

**Proxy authentication model**: Select your proxy's authentication model (none or basic [NCSA]), if appropriate.

**Proxy credentials**: Enter the credentials required for your proxy to authenticate your web server in ``username:password`` format.

Email settings

**SMTP host**: If you want to force Mahara to use a specific SMTP server instead of the system one, enter its hostname here, e.g. ``smtp.example.com``. It is possible to specify more than one host by separating them with semicolons, e.g. ``smtp1.example.com;smtp2.example.com``, but keep in mind that all other settings, e.g. authentication credentials and port numbers, will apply to all listed servers. It is not possible to specify different credentials for each server in this list. This feature is useful when SMTP host authentication is not required or you list different frontends for the same mail server in which case other settings will work.

**User**: If your SMTP server requires authentication, enter the username here.