<?php

[0] Fix | Delete

/**

[1] Fix | Delete

* Defines database credentials.

[2] Fix | Delete

*

[3] Fix | Delete

* Most of Elgg's configuration is stored in the database. This file contains the

[4] Fix | Delete

* credentials to connect to the database, as well as a few optional configuration

[5] Fix | Delete

* values.

[6] Fix | Delete

*

[7] Fix | Delete

* The Elgg installation attempts to populate this file with the correct settings

[8] Fix | Delete

* and then rename it to settings.php.

[9] Fix | Delete

*/

[10] Fix | Delete

[11] Fix | Delete

date_default_timezone_set('America/New_York');

[12] Fix | Delete

[13] Fix | Delete

global $CONFIG;

[14] Fix | Delete

if (!isset($CONFIG)) {

[15] Fix | Delete

$CONFIG = new \stdClass;

[16] Fix | Delete

}

[17] Fix | Delete

[18] Fix | Delete

/*

[19] Fix | Delete

* Standard configuration

[20] Fix | Delete

*

[21] Fix | Delete

* You will use the same database connection for reads and writes.

[22] Fix | Delete

* This is the easiest configuration, and will suit 99.99% of setups. However, if you're

[23] Fix | Delete

* running a really popular site, you'll probably want to spread out your database connections

[24] Fix | Delete

* and implement database replication. That's beyond the scope of this configuration file

[25] Fix | Delete

* to explain, but if you know you need it, skip past this section.

[26] Fix | Delete

*/

[27] Fix | Delete

[28] Fix | Delete

/**

[29] Fix | Delete

* The full file path for Elgg data storage. E.g. "/path/to/elgg-data/"

[30] Fix | Delete

*

[31] Fix | Delete

* @global string $CONFIG->dataroot

[32] Fix | Delete

*/

[33] Fix | Delete

$CONFIG->dataroot = "[[softdatadir]]/";

[34] Fix | Delete

[35] Fix | Delete

/**

[36] Fix | Delete

* The installation root URL of the site. E.g. "https://example.org/elgg/"

[37] Fix | Delete

*

[38] Fix | Delete

* If not provided, this is sniffed from the Symfony Request object

[39] Fix | Delete

*

[40] Fix | Delete

* @global string $CONFIG->wwwroot

[41] Fix | Delete

*/

[42] Fix | Delete

$CONFIG->wwwroot = "[[softurl]]/";

[43] Fix | Delete

[44] Fix | Delete

/**

[45] Fix | Delete

* The database username

[46] Fix | Delete

*

[47] Fix | Delete

* @global string $CONFIG->dbuser

[48] Fix | Delete

*/

[49] Fix | Delete

$CONFIG->dbuser = '[[softdbuser]]';

[50] Fix | Delete

[51] Fix | Delete

/**

[52] Fix | Delete

* The database password

[53] Fix | Delete

*

[54] Fix | Delete

* @global string $CONFIG->dbpass

[55] Fix | Delete

*/

[56] Fix | Delete

$CONFIG->dbpass = '[[softdbpass]]';

[57] Fix | Delete

[58] Fix | Delete

/**

[59] Fix | Delete

* The database name

[60] Fix | Delete

*

[61] Fix | Delete

* @global string $CONFIG->dbname

[62] Fix | Delete

*/

[63] Fix | Delete

$CONFIG->dbname = '[[softdb]]';

[64] Fix | Delete

[65] Fix | Delete

/**

[66] Fix | Delete

* The database host.

[67] Fix | Delete

*

[68] Fix | Delete

* For most installations, this is 'localhost'

[69] Fix | Delete

*

[70] Fix | Delete

* @global string $CONFIG->dbhost

[71] Fix | Delete

*/

[72] Fix | Delete

$CONFIG->dbhost = '[[softdbhost]]';

[73] Fix | Delete

[74] Fix | Delete

/**

[75] Fix | Delete

* The database port.

[76] Fix | Delete

*

[77] Fix | Delete

* For most installations, this is 3306

[78] Fix | Delete

*

[79] Fix | Delete

* @global string $CONFIG->dbport

[80] Fix | Delete

*/

[81] Fix | Delete

$CONFIG->dbport = '3306';

[82] Fix | Delete

[83] Fix | Delete

/**

[84] Fix | Delete

* The database prefix

[85] Fix | Delete

*

[86] Fix | Delete

* This prefix will be appended to all Elgg tables. If you're sharing

[87] Fix | Delete

* a database with other applications, use a database prefix to namespace tables

[88] Fix | Delete

* in order to avoid table name collisions.

[89] Fix | Delete

*

[90] Fix | Delete

* @global string $CONFIG->dbprefix

[91] Fix | Delete

*/

[92] Fix | Delete

$CONFIG->dbprefix = '[[dbprefix]]';

[93] Fix | Delete

[94] Fix | Delete

/**

[95] Fix | Delete

* The database encoding.

[96] Fix | Delete

*

[97] Fix | Delete

* If installing a fresh instance of Elgg 3.x or later, this MUST be set to "utf8mb4".

[98] Fix | Delete

* If you've upgraded an earlier Elgg version, do not set this until you have

[99] Fix | Delete

* manually converted your Elgg tables to utf8mb4.

[100] Fix | Delete

*

[101] Fix | Delete

* @global string $CONFIG->dbencoding

[102] Fix | Delete

*/

[103] Fix | Delete

$CONFIG->dbencoding = 'utf8mb4';

[104] Fix | Delete

[105] Fix | Delete

/**

[106] Fix | Delete

* Multiple database connections

[107] Fix | Delete

*

[108] Fix | Delete

* Elgg supports master/slave MySQL configurations. The master should be set as

[109] Fix | Delete

* the 'write' connection and the slave(s) as the 'read' connection(s).

[110] Fix | Delete

*

[111] Fix | Delete

* To use, uncomment the below configuration and update for your site.

[112] Fix | Delete

*/

[113] Fix | Delete

//$CONFIG->db['split'] = true;

[114] Fix | Delete

[115] Fix | Delete

//$CONFIG->db['write']['dbuser'] = "";

[116] Fix | Delete

//$CONFIG->db['write']['dbpass'] = "";

[117] Fix | Delete

//$CONFIG->db['write']['dbname'] = "";

[118] Fix | Delete

//$CONFIG->db['write']['dbhost'] = "";

[119] Fix | Delete

//$CONFIG->db['write']['dbport'] = "";

[120] Fix | Delete

[121] Fix | Delete

//$CONFIG->db['read'][0]['dbuser'] = "";

[122] Fix | Delete

//$CONFIG->db['read'][0]['dbpass'] = "";

[123] Fix | Delete

//$CONFIG->db['read'][0]['dbname'] = "";

[124] Fix | Delete

//$CONFIG->db['read'][0]['dbhost'] = "";

[125] Fix | Delete

//$CONFIG->db['read'][0]['dbport'] = "";

[126] Fix | Delete

//$CONFIG->db['read'][1]['dbuser'] = "";

[127] Fix | Delete

//$CONFIG->db['read'][1]['dbpass'] = "";

[128] Fix | Delete

//$CONFIG->db['read'][1]['dbname'] = "";

[129] Fix | Delete

//$CONFIG->db['read'][1]['dbhost'] = "";

[130] Fix | Delete

//$CONFIG->db['read'][1]['dbport'] = "";

[131] Fix | Delete

[132] Fix | Delete

/**

[133] Fix | Delete

* Memcache setup (optional)

[134] Fix | Delete

* This is where you may optionally set up memcache.

[135] Fix | Delete

*

[136] Fix | Delete

* Requirements:

[137] Fix | Delete

* 1) One or more memcache servers (http://www.danga.com/memcached/)

[138] Fix | Delete

* 2) PHP memcache wrapper (http://php.net/manual/en/memcache.setup.php)

[139] Fix | Delete

*

[140] Fix | Delete

* You can set a namespace prefix if you run multiple Elgg instances

[141] Fix | Delete

* on the same Memcache server.

[142] Fix | Delete

*

[143] Fix | Delete

* Note: Multiple server support is only available on server 1.2.1

[144] Fix | Delete

* or higher with PECL library > 2.0.0

[145] Fix | Delete

*/

[146] Fix | Delete

//$CONFIG->memcache = true;

[147] Fix | Delete

//

[148] Fix | Delete

//$CONFIG->memcache_servers = array (

[149] Fix | Delete

// array(

[150] Fix | Delete

// 'host' => 'server1',

[151] Fix | Delete

// 'port' => 11211,

[152] Fix | Delete

// ),

[153] Fix | Delete

// array(

[154] Fix | Delete

// 'host' => 'server2',

[155] Fix | Delete

// 'port' => 11211,

[156] Fix | Delete

// ),

[157] Fix | Delete

//);

[158] Fix | Delete

[159] Fix | Delete

// namespace prefix (can only be used with memcached)

[160] Fix | Delete

// $CONFIG->memcache_namespace_prefix = '';

[161] Fix | Delete

[162] Fix | Delete

/**

[163] Fix | Delete

* Redis setup (optional)

[164] Fix | Delete

* This is where you may optionally set up Redis.

[165] Fix | Delete

*/

[166] Fix | Delete

//$CONFIG->redis = true;

[167] Fix | Delete

//

[168] Fix | Delete

//$CONFIG->redis_options = array (

[169] Fix | Delete

// 'database' => '', // The "database" option lets developers specific which specific database to use.

[170] Fix | Delete

// 'password' => '', // The "password" option is used for clusters which required authentication.

[171] Fix | Delete

//);

[172] Fix | Delete

//

[173] Fix | Delete

// Only one server can be configured

[174] Fix | Delete

//$CONFIG->redis_servers = array (

[175] Fix | Delete

// array(

[176] Fix | Delete

// 'host' => 'server1',

[177] Fix | Delete

// 'port' => 6379,

[178] Fix | Delete

// ),

[179] Fix | Delete

//);

[180] Fix | Delete

[181] Fix | Delete

/**

[182] Fix | Delete

* Better caching performance

[183] Fix | Delete

*

[184] Fix | Delete

* Configuring simplecache in the settings.php file improves caching performance.

[185] Fix | Delete

* It allows Elgg to skip connecting to the database when serving cached JavaScript

[186] Fix | Delete

* and CSS files. If you uncomment and configure these settings, you will not be able

[187] Fix | Delete

* to change them from the Elgg advanced settings page.

[188] Fix | Delete

*/

[189] Fix | Delete

//$CONFIG->simplecache_enabled = true;

[190] Fix | Delete

[191] Fix | Delete

/**

[192] Fix | Delete

* Configure the boot cache TTL

[193] Fix | Delete

*

[194] Fix | Delete

* Elgg can store most non-user-specific boot up data in a cache. If you want to

[195] Fix | Delete

* configure how long Elgg takes before invalidating this cache, uncomment the next line

[196] Fix | Delete

* and set it to a number of seconds. If not set Elgg will default to 3600 seconds.

[197] Fix | Delete

*/

[198] Fix | Delete

//$CONFIG->boot_cache_ttl = 3600;

[199] Fix | Delete

[200] Fix | Delete

/**

[201] Fix | Delete

* Set cache directory

[202] Fix | Delete

*

[203] Fix | Delete

* By default, Elgg uses the data directory to store cache files, but this may

[204] Fix | Delete

* be undesirable for sites with the data directory on a distributed file system

[205] Fix | Delete

* (e.g. multiple servers with load balancing). You can specify a separate location

[206] Fix | Delete

* for the cache files here.

[207] Fix | Delete

*/

[208] Fix | Delete

//$CONFIG->cacheroot = "";

[209] Fix | Delete

[210] Fix | Delete

/**

[211] Fix | Delete

* Set local cache directory

[212] Fix | Delete

*

[213] Fix | Delete

* By default, Elgg uses the cache directory to store cache files, but this may

[214] Fix | Delete

* be undesirable for sites with a cache location on a network share used by multiple webservers.

[215] Fix | Delete

* You can specify a separate location for the local cache files here.

[216] Fix | Delete

*/

[217] Fix | Delete

//$CONFIG->localcacheroot = "";

[218] Fix | Delete

[219] Fix | Delete

/**

[220] Fix | Delete

* Set views simplecache directory

[221] Fix | Delete

*

[222] Fix | Delete

* Elgg uses the asset directory to store cached asset files.

[223] Fix | Delete

* By default, assets are stored in the cache root and site owners are

[224] Fix | Delete

* advised to symlink project root /cache to asset root.

[225] Fix | Delete

* Using this config value, you can change the default behavior

[226] Fix | Delete

*/

[227] Fix | Delete

//$CONFIG->assetroot = "";

[228] Fix | Delete

[229] Fix | Delete

/**

[230] Fix | Delete

* Plugins with more than the configured number of plugin settings won't be loaded into

[231] Fix | Delete

* bootdata cache. This is done to prevent memory issues.

[232] Fix | Delete

*

[233] Fix | Delete

* If set to < 1 all plugins will be loaded into the bootdata cache

[234] Fix | Delete

*

[235] Fix | Delete

* Default: 40

[236] Fix | Delete

*/

[237] Fix | Delete

//$CONFIG->bootdata_plugin_settings_limit = 0;

[238] Fix | Delete

[239] Fix | Delete

/**

[240] Fix | Delete

* Enable SendFile file serving

[241] Fix | Delete

*

[242] Fix | Delete

* After enabling X-Sendfile/X-Accel on your server, you can enable its support in Elgg. Set the

[243] Fix | Delete

* X-Sendfile-Type value to "X-Sendfile" (Apache) or "X-Accel-Redirect" (Nginx).

[244] Fix | Delete

*

[245] Fix | Delete

* @global string $CONFIG->{'X-Sendfile-Type'}

[246] Fix | Delete

*/

[247] Fix | Delete

//$CONFIG->{'X-Sendfile-Type'} = '';

[248] Fix | Delete

[249] Fix | Delete

/**

[250] Fix | Delete

* Configure X-Accel on nginx (see SendFile above)

[251] Fix | Delete

*

[252] Fix | Delete

* For Nginx, you'll likely also need to set this to a mapping like: "/path/to/dataroot/=/download/".

[253] Fix | Delete

*

[254] Fix | Delete

* @global string $CONFIG->{'X-Accel-Mapping'}

[255] Fix | Delete

*/

[256] Fix | Delete

//$CONFIG->{'X-Accel-Mapping'} = '';

[257] Fix | Delete

[258] Fix | Delete

/**

[259] Fix | Delete

* Cookie configuration

[260] Fix | Delete

*

[261] Fix | Delete

* Elgg uses 2 cookies: a PHP session cookie and an extended login cookie

[262] Fix | Delete

* (also called the remember me cookie). See the PHP manual for documentation on

[263] Fix | Delete

* each of these parameters. Possible options:

[264] Fix | Delete

*

[265] Fix | Delete

* - Set the session name to share the session across applications.

[266] Fix | Delete

* - Set the path because Elgg is not installed in the root of the web directory.

[267] Fix | Delete

* - Set the secure option to true if you only serve the site over HTTPS.

[268] Fix | Delete

* - Set the expire option on the remember me cookie to change its lifetime

[269] Fix | Delete

*

[270] Fix | Delete

* To use, uncomment the appropriate sections below and update for your site.

[271] Fix | Delete

*

[272] Fix | Delete

* @global array $CONFIG->cookies

[273] Fix | Delete

*/

[274] Fix | Delete

// get the default parameters from php.ini

[275] Fix | Delete

//$CONFIG->cookies['session'] = session_get_cookie_params();

[276] Fix | Delete

//$CONFIG->cookies['session']['name'] = "Elgg";

[277] Fix | Delete

// optionally overwrite the defaults from php.ini below

[278] Fix | Delete

//$CONFIG->cookies['session']['path'] = "/";

[279] Fix | Delete

//$CONFIG->cookies['session']['domain'] = "";

[280] Fix | Delete

//$CONFIG->cookies['session']['secure'] = false;

[281] Fix | Delete

//$CONFIG->cookies['session']['httponly'] = false;

[282] Fix | Delete

[283] Fix | Delete

// extended session cookie

[284] Fix | Delete

//$CONFIG->cookies['remember_me'] = session_get_cookie_params();

[285] Fix | Delete

//$CONFIG->cookies['remember_me']['name'] = "elggperm";

[286] Fix | Delete

//$CONFIG->cookies['remember_me']['expire'] = strtotime("+30 days");

[287] Fix | Delete

// optionally overwrite the defaults from php.ini below

[288] Fix | Delete

//$CONFIG->cookies['remember_me']['path'] = "/";

[289] Fix | Delete

//$CONFIG->cookies['remember_me']['domain'] = "";

[290] Fix | Delete

//$CONFIG->cookies['remember_me']['secure'] = false;

[291] Fix | Delete

//$CONFIG->cookies['remember_me']['httponly'] = false;

[292] Fix | Delete

[293] Fix | Delete

/**

[294] Fix | Delete

* Disable the database query cache

[295] Fix | Delete

*

[296] Fix | Delete

* Elgg stores each query and its results in a query cache.

[297] Fix | Delete

* On large sites or long-running scripts, this cache can grow to be

[298] Fix | Delete

* large. To disable query caching, set this to true.

[299] Fix | Delete

*

[300] Fix | Delete

* @global bool $CONFIG->db_disable_query_cache

[301] Fix | Delete

*/

[302] Fix | Delete

$CONFIG->db_disable_query_cache = false;

[303] Fix | Delete

[304] Fix | Delete

/**

[305] Fix | Delete

* Automatically disable plugins that are unable to boot

[306] Fix | Delete

*

[307] Fix | Delete

* Elgg will disable unbootable plugins. If you set this to false plugins

[308] Fix | Delete

* will no longer be disabled if they are not bootable. This could cause requests

[309] Fix | Delete

* to your site to fail as required views, classes or cached data could be missing.

[310] Fix | Delete

*

[311] Fix | Delete

* Setting this to false could be useful during deployment of new code.

[312] Fix | Delete

*

[313] Fix | Delete

* @global bool $CONFIG->auto_disable_plugins

[314] Fix | Delete

*/

[315] Fix | Delete

$CONFIG->auto_disable_plugins = true;

[316] Fix | Delete

[317] Fix | Delete

/**

[318] Fix | Delete

* Control if Elgg should always validate classes previously stored in the ClassMap.

[319] Fix | Delete

* You can disable this for performance reasons (less disk checks) but you need to make sure the class map will never get stale data.

[320] Fix | Delete

*

[321] Fix | Delete

* @global bool $CONFIG->class_loader_verify_file_existence

[322] Fix | Delete

*/

[323] Fix | Delete

//$CONFIG->class_loader_verify_file_existence = false;

[324] Fix | Delete

[325] Fix | Delete

/**

[326] Fix | Delete

* This is an optional script used to override Elgg's default handling of

[327] Fix | Delete

* uncaught exceptions.

[328] Fix | Delete

*

[329] Fix | Delete

* This should be an absolute file path to a php script that will be called

[330] Fix | Delete

* any time an uncaught exception is thrown.

[331] Fix | Delete

*

[332] Fix | Delete

* The script will have access to the following variables as part of the scope

[333] Fix | Delete

* global $CONFIG

[334] Fix | Delete

* $exception - the unhandled exception

[335] Fix | Delete

*

[336] Fix | Delete

* @warning - the database may not be available

[337] Fix | Delete

*

[338] Fix | Delete

* @global string $CONFIG->exception_include

[339] Fix | Delete

*/

[340] Fix | Delete

$CONFIG->exception_include = '';

[341] Fix | Delete

[342] Fix | Delete

/**

[343] Fix | Delete

* To enable profiling, uncomment the following lines, and replace __some_secret__ with a

[344] Fix | Delete

* secret key. When enabled, profiling data will show in the JS console.

[345] Fix | Delete

*/

[346] Fix | Delete

//if (isset($_REQUEST['__some_secret__'])) {

[347] Fix | Delete

//

[348] Fix | Delete

// // send profiling data to the JS console?

[349] Fix | Delete

// $CONFIG->enable_profiling = true;

[350] Fix | Delete

//

[351] Fix | Delete

// // profile all queries? A page with a ton of queries could eat up memory.

[352] Fix | Delete

// $CONFIG->profiling_sql = false;

[353] Fix | Delete

//

[354] Fix | Delete

// // in the list, don't include times that don't contribute at least this much to the

[355] Fix | Delete

// // total time captured. .1% by default

[356] Fix | Delete

// $CONFIG->profiling_minimum_percentage = .1;

[357] Fix | Delete

//}

[358] Fix | Delete

[359] Fix | Delete

/**

[360] Fix | Delete

* Maximum php execution time for actions (in seconds)

[361] Fix | Delete

*

[362] Fix | Delete

* This setting can be used to set a custom default php execution time only for all registered Elgg actions.

[363] Fix | Delete

* Note that if some actions set their own execution time limit, this setting will no affect those actions.

[364] Fix | Delete

*

[365] Fix | Delete

* @global int $CONFIG->action_time_limit

[366] Fix | Delete

*/

[367] Fix | Delete

$CONFIG->action_time_limit = 120;

[368] Fix | Delete

[369] Fix | Delete

/**

[370] Fix | Delete

* Allow access to PHPInfo

[371] Fix | Delete

*

[372] Fix | Delete

* This setting can be used to allow site administrators access to the PHPInfo page.

[373] Fix | Delete

* By default this is not allowed.

[374] Fix | Delete

*

[375] Fix | Delete

* @global bool $CONFIG->allow_phpinfo

[376] Fix | Delete

*/

[377] Fix | Delete

$CONFIG->allow_phpinfo = false;

[378] Fix | Delete

[379] Fix | Delete

/**

[380] Fix | Delete

* Configure image processor

[381] Fix | Delete

*

[382] Fix | Delete

* This setting can be used to select a different image processor. By default the GD library is used.

[383] Fix | Delete

* Currently only 'imagick' is supported as a different configuration.

[384] Fix | Delete

* For Imagick the 'imagick' extension is required.

[385] Fix | Delete

*

[386] Fix | Delete

* @global string $CONFIG->image_processor

[387] Fix | Delete

*/

[388] Fix | Delete

//$CONFIG->image_processor = 'imagick';

[389] Fix | Delete

[390] Fix | Delete

/**

[391] Fix | Delete

* Control if webp images are allowed to be served for icons (if supported by server and browser).

[392] Fix | Delete

* Default enabled

[393] Fix | Delete

*

[394] Fix | Delete

* @global bool $CONFIG->webp_enabled

[395] Fix | Delete

*/

[396] Fix | Delete

//$CONFIG->webp_enabled = false;

[397] Fix | Delete

[398] Fix | Delete

/**

[399] Fix | Delete

* Email subject length limit

[400] Fix | Delete

*

[401] Fix | Delete

* The length limit for email subjects, defaults to 998 as described in http://www.faqs.org/rfcs/rfc2822.html

[402] Fix | Delete

*

[403] Fix | Delete

* @global int $CONFIG->emailer_transport

[404] Fix | Delete

*/

[405] Fix | Delete

//$CONFIG->email_subject_limit = 998;

[406] Fix | Delete

[407] Fix | Delete

/**

[408] Fix | Delete

* Configure emailer transport

[409] Fix | Delete

*

[410] Fix | Delete

* This setting can be used to select a different emailer transport. By default the Laminas Sendmail Transport is used.

[411] Fix | Delete

* Currently only 'smtp' and 'sendmail' are supported as a different configuration.

[412] Fix | Delete

* For 'smtp', the SMTP server's settings must be set, while 'sendmail' requires no configuration.

[413] Fix | Delete

*

[414] Fix | Delete

* @global string $CONFIG->emailer_transport

[415] Fix | Delete

*/

[416] Fix | Delete

//$CONFIG->emailer_transport = 'sendmail';

[417] Fix | Delete

[418] Fix | Delete

/**

[419] Fix | Delete

* Configure sendmail related settings

[420] Fix | Delete

*/

[421] Fix | Delete

//$CONFIG->emailer_sendmail_settings = '';

[422] Fix | Delete

[423] Fix | Delete

/**

[424] Fix | Delete

* Configure emailer SMTP settings

[425] Fix | Delete

*

[426] Fix | Delete

* This setting is only necessary if the above emailer transport is set to 'smtp'.

[427] Fix | Delete

* Please refer to https://docs.laminas.dev/laminas-mail/transport/smtp-options/#configuration-options

[428] Fix | Delete

* and https://docs.laminas.dev/laminas-mail/transport/smtp-authentication/#examples

[429] Fix | Delete

*/

[430] Fix | Delete

//$CONFIG->emailer_smtp_settings = array(

[431] Fix | Delete

// 'name' => 'localhost.localdomain',

[432] Fix | Delete

// 'host' => '127.0.0.1',

[433] Fix | Delete

// 'port' => 25,

[434] Fix | Delete

// 'connection_class' => 'login',

[435] Fix | Delete

// 'connection_config' => [

[436] Fix | Delete

// 'username' => 'user',

[437] Fix | Delete

// 'password' => 'pass',

[438] Fix | Delete

// 'ssl' => '', // OPTIONAL (tls or ssl)

[439] Fix | Delete

// 'port' => '', // OPTIONAL (Non-SSL default 25, SSL default 465, TLS default 587)

[440] Fix | Delete

// 'use_complete_quit' => '', // OPTIONAL

[441] Fix | Delete

// ],

[442] Fix | Delete

//);

[443] Fix | Delete

[444] Fix | Delete

/**

[445] Fix | Delete

* Configure notification queue delay

[446] Fix | Delete

*

[447] Fix | Delete

* This setting can be used to delay the processing of queued notifications. This can help when users create content and

[448] Fix | Delete

* quickly remove the content. A notification could be send out to subscribers about content which will be removed quickly

[449] Fix | Delete

*

[450] Fix | Delete

* The setting needs to be the number of seconds to delay the notification queue processing (eg. 3 minutes => 180 seconds)

[451] Fix | Delete

* Default: 0 (no delay)

[452] Fix | Delete

*/

[453] Fix | Delete

//$CONFIG->notifications_queue_delay = 180;

[454] Fix | Delete

[455] Fix | Delete

/**

[456] Fix | Delete

* Proxy configuration

[457] Fix | Delete

*

[458] Fix | Delete

* These settings can be used whenever there is the need to (optionally) configure a proxy

[459] Fix | Delete

*/

[460] Fix | Delete

$CONFIG->proxy = [

[461] Fix | Delete

// 'host' => '127.0.0.1',

[462] Fix | Delete

// 'port' => 25,

[463] Fix | Delete

// 'verify_ssl' => false,

[464] Fix | Delete

// 'username' => 'user',

[465] Fix | Delete

// 'password' => 'pass',

[466] Fix | Delete

];

[467] Fix | Delete

[468] Fix | Delete

/**

[469] Fix | Delete

* Logging level

[470] Fix | Delete

*

[471] Fix | Delete

* By default, the logging level at boot-time is calculated from PHP's error_reporting(), and during boot

[472] Fix | Delete

* it is changed to the value specified on the Advanced Settings page. INFO-level events like DB queries

[473] Fix | Delete

* will not be logged during the initial boot.

[474] Fix | Delete

*

[475] Fix | Delete

* However, if the level is set here, it will be used during the entire request. It can be set to one of

[476] Fix | Delete

* the string levels in Elgg\Logger or ''. E.g., use 'INFO' to log all DB queries during boot up.

[477] Fix | Delete

*/

[478] Fix | Delete

//$CONFIG->debug = 'INFO';

[479] Fix | Delete

[480] Fix | Delete

/**

[481] Fix | Delete

* Language to locale mapping

[482] Fix | Delete

*

[483] Fix | Delete

* Some features support mapping a language to a locale setting (for example date presentations). In this setting

[484] Fix | Delete

* the mapping between language (key) and locale setting (values) can be configured.

[485] Fix | Delete

*

[486] Fix | Delete

* For example if you wish to present English dates in USA format make the mapping 'en' => ['en_US'], or if you

[487] Fix | Delete

* wish to use UK format 'en' => ['en_UK'].

[488] Fix | Delete

*

[489] Fix | Delete

* It's possible to configure the locale mapping for mulitple languages, for example:

[490] Fix | Delete

* [

[491] Fix | Delete

* 'en' => ['en_US', 'en_UK'],

[492] Fix | Delete

* 'nl' => ['nl_NL'],

[493] Fix | Delete

* ]

[494] Fix | Delete

*

[495] Fix | Delete

* It's also possible to add new languages to the supported languages

[496] Fix | Delete

* [

[497] Fix | Delete

* 'my_language' => [], // no locale mapping

[498] Fix | Delete

* 'my_language2' => ['en_US'], // using USA locale mapping

[499] Fix | Delete