<?php

[0] Fix | Delete

[1] Fix | Delete

return [

[2] Fix | Delete

[3] Fix | Delete

/*

[4] Fix | Delete

|--------------------------------------------------------------------------

[5] Fix | Delete

| Specifies the default CMS theme.

[6] Fix | Delete

|--------------------------------------------------------------------------

[7] Fix | Delete

|

[8] Fix | Delete

| This parameter value can be overridden by the CMS back-end settings.

[9] Fix | Delete

|

[10] Fix | Delete

*/

[11] Fix | Delete

[12] Fix | Delete

'activeTheme' => 'demo',

[13] Fix | Delete

[14] Fix | Delete

/*

[15] Fix | Delete

|--------------------------------------------------------------------------

[16] Fix | Delete

| Bleeding edge updates

[17] Fix | Delete

|--------------------------------------------------------------------------

[18] Fix | Delete

|

[19] Fix | Delete

| If you are developing with Winter, it is important to have the latest

[20] Fix | Delete

| code base. Set this value to 'true' to tell the platform to download

[21] Fix | Delete

| and use the development copies of core files and plugins.

[22] Fix | Delete

|

[23] Fix | Delete

*/

[24] Fix | Delete

[25] Fix | Delete

'edgeUpdates' => false,

[26] Fix | Delete

[27] Fix | Delete

/*

[28] Fix | Delete

|--------------------------------------------------------------------------

[29] Fix | Delete

| Back-end URI prefix

[30] Fix | Delete

|--------------------------------------------------------------------------

[31] Fix | Delete

|

[32] Fix | Delete

| Specifies the URL name used for accessing back-end pages.

[33] Fix | Delete

| For example: backend -> http://localhost/backend

[34] Fix | Delete

|

[35] Fix | Delete

*/

[36] Fix | Delete

[37] Fix | Delete

'backendUri' => '/[[admin_folder]]',

[38] Fix | Delete

[39] Fix | Delete

/*

[40] Fix | Delete

|--------------------------------------------------------------------------

[41] Fix | Delete

| Back-end force HTTPS security

[42] Fix | Delete

|--------------------------------------------------------------------------

[43] Fix | Delete

|

[44] Fix | Delete

| Use this setting to force a secure protocol when accessing any back-end

[45] Fix | Delete

| pages, including the authentication pages. This is usually handled by

[46] Fix | Delete

| web server config, but can be handled by the app for added security.

[47] Fix | Delete

|

[48] Fix | Delete

*/

[49] Fix | Delete

[50] Fix | Delete

'backendForceSecure' => false,

[51] Fix | Delete

[52] Fix | Delete

/*

[53] Fix | Delete

|--------------------------------------------------------------------------

[54] Fix | Delete

| Back-end login remember

[55] Fix | Delete

|--------------------------------------------------------------------------

[56] Fix | Delete

|

[57] Fix | Delete

| Define live duration of backend sessions:

[58] Fix | Delete

|

[59] Fix | Delete

| true - session never expire (cookie expiration in 5 years)

[60] Fix | Delete

|

[61] Fix | Delete

| false - session have a limited time (see session.lifetime)

[62] Fix | Delete

|

[63] Fix | Delete

| null - The form login display a checkbox that allow user to choose

[64] Fix | Delete

| wanted behavior

[65] Fix | Delete

|

[66] Fix | Delete

*/

[67] Fix | Delete

[68] Fix | Delete

'backendForceRemember' => true,

[69] Fix | Delete

[70] Fix | Delete

/*

[71] Fix | Delete

|--------------------------------------------------------------------------

[72] Fix | Delete

| Back-end timezone

[73] Fix | Delete

|--------------------------------------------------------------------------

[74] Fix | Delete

|

[75] Fix | Delete

| This acts as the default setting for a back-end user's timezone. This can

[76] Fix | Delete

| be changed by the user at any time using the backend preferences. All

[77] Fix | Delete

| dates displayed in the back-end will be converted to this timezone.

[78] Fix | Delete

|

[79] Fix | Delete

*/

[80] Fix | Delete

[81] Fix | Delete

'backendTimezone' => 'UTC',

[82] Fix | Delete

[83] Fix | Delete

/*

[84] Fix | Delete

|--------------------------------------------------------------------------

[85] Fix | Delete

| Back-end Skin

[86] Fix | Delete

|--------------------------------------------------------------------------

[87] Fix | Delete

|

[88] Fix | Delete

| Specifies the back-end skin to use.

[89] Fix | Delete

|

[90] Fix | Delete

*/

[91] Fix | Delete

[92] Fix | Delete

'backendSkin' => \Backend\Skins\Standard::class,

[93] Fix | Delete

[94] Fix | Delete

/*

[95] Fix | Delete

|--------------------------------------------------------------------------

[96] Fix | Delete

| Automatically run migrations on login

[97] Fix | Delete

|--------------------------------------------------------------------------

[98] Fix | Delete

|

[99] Fix | Delete

| If value is true, UpdateManager will be run on logging in to the backend.

[100] Fix | Delete

| It's recommended to set this value to 'null' in production enviroments

[101] Fix | Delete

| because it clears the cache every time a user logs in to the backend.

[102] Fix | Delete

| If set to null, this setting is enabled when debug mode (app.debug) is enabled

[103] Fix | Delete

| and disabled when debug mode is disabled.

[104] Fix | Delete

|

[105] Fix | Delete

*/

[106] Fix | Delete

[107] Fix | Delete

'runMigrationsOnLogin' => null,

[108] Fix | Delete

[109] Fix | Delete

/*

[110] Fix | Delete

|--------------------------------------------------------------------------

[111] Fix | Delete

| Determines which modules to load

[112] Fix | Delete

|--------------------------------------------------------------------------

[113] Fix | Delete

|

[114] Fix | Delete

| Specify which modules should be registered when using the application.

[115] Fix | Delete

|

[116] Fix | Delete

*/

[117] Fix | Delete

[118] Fix | Delete

'loadModules' => [

[119] Fix | Delete

'System',

[120] Fix | Delete

'Backend',

[121] Fix | Delete

'Cms',

[122] Fix | Delete

],

[123] Fix | Delete

[124] Fix | Delete

/*

[125] Fix | Delete

|--------------------------------------------------------------------------

[126] Fix | Delete

| Prevents application updates

[127] Fix | Delete

|--------------------------------------------------------------------------

[128] Fix | Delete

|

[129] Fix | Delete

| If using composer or git to download updates to the core files, set this

[130] Fix | Delete

| value to 'true' to prevent the update gateway from trying to download

[131] Fix | Delete

| these files again as part of the application update process. Plugins

[132] Fix | Delete

| and themes will still be downloaded.

[133] Fix | Delete

|

[134] Fix | Delete

*/

[135] Fix | Delete

[136] Fix | Delete

'disableCoreUpdates' => false,

[137] Fix | Delete

[138] Fix | Delete

/*

[139] Fix | Delete

|--------------------------------------------------------------------------

[140] Fix | Delete

| Specific plugins to disable

[141] Fix | Delete

|--------------------------------------------------------------------------

[142] Fix | Delete

|

[143] Fix | Delete

| Specify plugin codes which will always be disabled in the application.

[144] Fix | Delete

|

[145] Fix | Delete

*/

[146] Fix | Delete

[147] Fix | Delete

'disablePlugins' => [],

[148] Fix | Delete

[149] Fix | Delete

/*

[150] Fix | Delete

|--------------------------------------------------------------------------

[151] Fix | Delete

| Determines if the routing caching is enabled.

[152] Fix | Delete

|--------------------------------------------------------------------------

[153] Fix | Delete

|

[154] Fix | Delete

| If the caching is enabled, the page URL map is saved in the cache. If a page

[155] Fix | Delete

| URL was changed on the disk, the old URL value could be still saved in the cache.

[156] Fix | Delete

| To update the cache the back-end Clear Cache feature should be used. It is recommended

[157] Fix | Delete

| to disable the caching during the development, and enable it in the production mode.

[158] Fix | Delete

|

[159] Fix | Delete

*/

[160] Fix | Delete

[161] Fix | Delete

'enableRoutesCache' => env('ROUTES_CACHE', false),

[162] Fix | Delete

[163] Fix | Delete

/*

[164] Fix | Delete

|--------------------------------------------------------------------------

[165] Fix | Delete

| Time to live for the URL map.

[166] Fix | Delete

|--------------------------------------------------------------------------

[167] Fix | Delete

|

[168] Fix | Delete

| The URL map used in the CMS page routing process. By default

[169] Fix | Delete

| the map is updated every time when a page is saved in the back-end or when the

[170] Fix | Delete

| interval, in minutes, specified with the urlMapCacheTTL parameter expires.

[171] Fix | Delete

|

[172] Fix | Delete

*/

[173] Fix | Delete

[174] Fix | Delete

'urlCacheTtl' => 10,

[175] Fix | Delete

[176] Fix | Delete

/*

[177] Fix | Delete

|--------------------------------------------------------------------------

[178] Fix | Delete

| Time to live for parsed CMS objects.

[179] Fix | Delete

|--------------------------------------------------------------------------

[180] Fix | Delete

|

[181] Fix | Delete

| Specifies the number of minutes the CMS object cache lives. After the interval

[182] Fix | Delete

| is expired item are re-cached. Note that items are re-cached automatically when

[183] Fix | Delete

| the corresponding template file is modified.

[184] Fix | Delete

|

[185] Fix | Delete

*/

[186] Fix | Delete

[187] Fix | Delete

'parsedPageCacheTTL' => 10,

[188] Fix | Delete

[189] Fix | Delete

/*

[190] Fix | Delete

|--------------------------------------------------------------------------

[191] Fix | Delete

| Determines if the asset caching is enabled.

[192] Fix | Delete

|--------------------------------------------------------------------------

[193] Fix | Delete

|

[194] Fix | Delete

| If the caching is enabled, combined assets are cached. If a asset file

[195] Fix | Delete

| is changed on the disk, the old file contents could be still saved in the cache.

[196] Fix | Delete

| To update the cache the back-end Clear Cache feature should be used. It is recommended

[197] Fix | Delete

| to disable the caching during the development, and enable it in the production mode.

[198] Fix | Delete

|

[199] Fix | Delete

*/

[200] Fix | Delete

[201] Fix | Delete

'enableAssetCache' => env('ASSET_CACHE', false),

[202] Fix | Delete

[203] Fix | Delete

/*

[204] Fix | Delete

|--------------------------------------------------------------------------

[205] Fix | Delete

| Determines if the asset minification is enabled.

[206] Fix | Delete

|--------------------------------------------------------------------------

[207] Fix | Delete

|

[208] Fix | Delete

| If the minification is enabled, combined assets are compressed (minified).

[209] Fix | Delete

| It is recommended to disable the minification during development, and

[210] Fix | Delete

| enable it in production mode. If set to null, assets are minified

[211] Fix | Delete

| when debug mode (app.debug) is disabled.

[212] Fix | Delete

|

[213] Fix | Delete

*/

[214] Fix | Delete

[215] Fix | Delete

'enableAssetMinify' => null,

[216] Fix | Delete

[217] Fix | Delete

/*

[218] Fix | Delete

|--------------------------------------------------------------------------

[219] Fix | Delete

| Check import timestamps when combining assets

[220] Fix | Delete

|--------------------------------------------------------------------------

[221] Fix | Delete

|

[222] Fix | Delete

| If deep hashing is enabled, the combiner cache will be reset when a change

[223] Fix | Delete

| is detected on imported files, in addition to those referenced directly.

[224] Fix | Delete

| This will cause slower page performance. If set to null, deep hashing

[225] Fix | Delete

| is used when debug mode (app.debug) is enabled.

[226] Fix | Delete

|

[227] Fix | Delete

*/

[228] Fix | Delete

[229] Fix | Delete

'enableAssetDeepHashing' => null,

[230] Fix | Delete

[231] Fix | Delete

/*

[232] Fix | Delete

|--------------------------------------------------------------------------

[233] Fix | Delete

| Database-driven Themes

[234] Fix | Delete

|--------------------------------------------------------------------------

[235] Fix | Delete

|

[236] Fix | Delete

| Stores theme templates in the database instead of the filesystem.

[237] Fix | Delete

|

[238] Fix | Delete

| false - All theme templates are sourced from the filesystem.

[239] Fix | Delete

|

[240] Fix | Delete

| true - Source theme templates from the database with fallback to the filesytem.

[241] Fix | Delete

|

[242] Fix | Delete

| null - Setting equal to the inverse of app.debug: debug enabled, this disabled.

[243] Fix | Delete

|

[244] Fix | Delete

| The database layer stores all modified CMS files in the database. Files that are

[245] Fix | Delete

| not modified continue to be loaded from the filesystem. The `theme:sync $themeDir`

[246] Fix | Delete

| console command is available to populate the database from the filesystem with

[247] Fix | Delete

| the `--toFile` flag to sync in the other direction (database to filesystem) and

[248] Fix | Delete

| the `--paths="/path/to/file.md,/path/to/file2.md" flag to sync only specific files.

[249] Fix | Delete

|

[250] Fix | Delete

| Files modified in the database are cached to indicate that they should be loaded

[251] Fix | Delete

| from the database.

[252] Fix | Delete

|

[253] Fix | Delete

*/

[254] Fix | Delete

[255] Fix | Delete

'databaseTemplates' => env('DATABASE_TEMPLATES', false),

[256] Fix | Delete

[257] Fix | Delete

/*

[258] Fix | Delete

|--------------------------------------------------------------------------

[259] Fix | Delete

| Public plugins path

[260] Fix | Delete

|--------------------------------------------------------------------------

[261] Fix | Delete

|

[262] Fix | Delete

| Specifies the public plugins path relative to the application base URL,

[263] Fix | Delete

| or you can specify a full URL path.

[264] Fix | Delete

|

[265] Fix | Delete

*/

[266] Fix | Delete

[267] Fix | Delete

'pluginsPath' => '/plugins',

[268] Fix | Delete

[269] Fix | Delete

/*

[270] Fix | Delete

|--------------------------------------------------------------------------

[271] Fix | Delete

| Public themes path

[272] Fix | Delete

|--------------------------------------------------------------------------

[273] Fix | Delete

|

[274] Fix | Delete

| Specifies the public themes path relative to the application base URL,

[275] Fix | Delete

| or you can specify a full URL path.

[276] Fix | Delete

|

[277] Fix | Delete

*/

[278] Fix | Delete

[279] Fix | Delete

'themesPath' => '/themes',

[280] Fix | Delete

[281] Fix | Delete

/*

[282] Fix | Delete

|--------------------------------------------------------------------------

[283] Fix | Delete

| Resource storage

[284] Fix | Delete

|--------------------------------------------------------------------------

[285] Fix | Delete

|

[286] Fix | Delete

| Specifies the configuration for resource storage, such as media and

[287] Fix | Delete

| upload files. These resources are used:

[288] Fix | Delete

|

[289] Fix | Delete

| media - generated by the media manager.

[290] Fix | Delete

| uploads - generated by attachment model relationships.

[291] Fix | Delete

| resized - generated by System\Classes\ImageResizer or the resize() Twig filter

[292] Fix | Delete

|

[293] Fix | Delete

| For each resource you can specify:

[294] Fix | Delete

|

[295] Fix | Delete

| disk - filesystem disk, as specified in filesystems.php config.

[296] Fix | Delete

| folder - a folder prefix for storing all generated files inside.

[297] Fix | Delete

| path - the public path relative to the application base URL,

[298] Fix | Delete

| or you can specify a full URL path.

[299] Fix | Delete

|

[300] Fix | Delete

| Optionally, you can specify how long temporary URLs to protected files

[301] Fix | Delete

| in cloud storage (ex. AWS, RackSpace) are valid for by setting

[302] Fix | Delete

| temporaryUrlTTL to a value in seconds to define a validity period. This

[303] Fix | Delete

| is only used for the 'uploads' config when using a supported cloud disk

[304] Fix | Delete

|

[305] Fix | Delete

| NOTE: If you have installed Winter in a subfolder, are using local

[306] Fix | Delete

| storage and are not using a linkPolicy of 'force' you should include

[307] Fix | Delete

| the path to the subfolder in the `path` option for these storage

[308] Fix | Delete

| configurations.

[309] Fix | Delete

|

[310] Fix | Delete

| Example: Winter is installed under https://localhost/projects/winter.

[311] Fix | Delete

| You should then specify `/projects/winter/storage/app/uploads` as the

[312] Fix | Delete

| path for the uploads disk and `/projects/winter/storage/app/media` as

[313] Fix | Delete

| the path for the media disk.

[314] Fix | Delete

*/

[315] Fix | Delete

[316] Fix | Delete

'storage' => [

[317] Fix | Delete

'uploads' => [

[318] Fix | Delete

'disk' => 'local',

[319] Fix | Delete

'folder' => 'uploads',

[320] Fix | Delete

'path' => '/storage/app/uploads',

[321] Fix | Delete

'temporaryUrlTTL' => 3600,

[322] Fix | Delete

],

[323] Fix | Delete

'media' => [

[324] Fix | Delete

'disk' => 'local',

[325] Fix | Delete

'folder' => 'media',

[326] Fix | Delete

'path' => '/storage/app/media',

[327] Fix | Delete

],

[328] Fix | Delete

'resized' => [

[329] Fix | Delete

'disk' => 'local',

[330] Fix | Delete

'folder' => 'resized',

[331] Fix | Delete

'path' => '/storage/app/resized',

[332] Fix | Delete

],

[333] Fix | Delete

],

[334] Fix | Delete

[335] Fix | Delete

/*

[336] Fix | Delete

|--------------------------------------------------------------------------

[337] Fix | Delete

| Convert Line Endings

[338] Fix | Delete

|--------------------------------------------------------------------------

[339] Fix | Delete

|

[340] Fix | Delete

| Determines if Winter should convert line endings from the windows style

[341] Fix | Delete

| \r\n to the unix style \n.

[342] Fix | Delete

|

[343] Fix | Delete

*/

[344] Fix | Delete

[345] Fix | Delete

'convertLineEndings' => false,

[346] Fix | Delete

[347] Fix | Delete

/*

[348] Fix | Delete

|--------------------------------------------------------------------------

[349] Fix | Delete

| Linking policy

[350] Fix | Delete

|--------------------------------------------------------------------------

[351] Fix | Delete

|

[352] Fix | Delete

| Controls how URL links are generated throughout the application.

[353] Fix | Delete

|

[354] Fix | Delete

| detect - detect hostname and use the current schema

[355] Fix | Delete

| secure - detect hostname and force HTTPS schema

[356] Fix | Delete

| insecure - detect hostname and force HTTP schema

[357] Fix | Delete

| force - force hostname and schema using app.url config value

[358] Fix | Delete

|

[359] Fix | Delete

| NOTE: force will ensure that the app.url value is used as the host for

[360] Fix | Delete

| urls generated through the URL helpers which might have unintended

[361] Fix | Delete

| consequences for projects that support multiple hostnames.

[362] Fix | Delete

|

[363] Fix | Delete

*/

[364] Fix | Delete

[365] Fix | Delete

'linkPolicy' => env('LINK_POLICY', 'force'),

[366] Fix | Delete

[367] Fix | Delete

/*

[368] Fix | Delete

|--------------------------------------------------------------------------

[369] Fix | Delete

| Default permission mask

[370] Fix | Delete

|--------------------------------------------------------------------------

[371] Fix | Delete

|

[372] Fix | Delete

| Specifies a default file and folder permission for newly created objects.

[373] Fix | Delete

|

[374] Fix | Delete

*/

[375] Fix | Delete

[376] Fix | Delete

'defaultMask' => [

[377] Fix | Delete

'file' => null,

[378] Fix | Delete

'folder' => null,

[379] Fix | Delete

],

[380] Fix | Delete

[381] Fix | Delete

/*

[382] Fix | Delete

|--------------------------------------------------------------------------

[383] Fix | Delete

| Safe mode

[384] Fix | Delete

|--------------------------------------------------------------------------

[385] Fix | Delete

|

[386] Fix | Delete

| If safe mode is enabled, the PHP code section is disabled in the CMS

[387] Fix | Delete

| for security reasons. If set to null, safe mode is enabled when

[388] Fix | Delete

| debug mode (app.debug) is disabled.

[389] Fix | Delete

|

[390] Fix | Delete

*/

[391] Fix | Delete

[392] Fix | Delete

'enableSafeMode' => null,

[393] Fix | Delete

[394] Fix | Delete

/*

[395] Fix | Delete

|--------------------------------------------------------------------------

[396] Fix | Delete

| Cross Site Request Forgery (CSRF) Protection

[397] Fix | Delete

|--------------------------------------------------------------------------

[398] Fix | Delete

|

[399] Fix | Delete

| If the CSRF protection is enabled, all "postback" & AJAX requests are

[400] Fix | Delete

| checked for a valid security token.

[401] Fix | Delete

|

[402] Fix | Delete

*/

[403] Fix | Delete

[404] Fix | Delete

'enableCsrfProtection' => env('ENABLE_CSRF', true),

[405] Fix | Delete

[406] Fix | Delete

/*

[407] Fix | Delete

|--------------------------------------------------------------------------

[408] Fix | Delete

| Force bytecode invalidation

[409] Fix | Delete

|--------------------------------------------------------------------------

[410] Fix | Delete

|

[411] Fix | Delete

| When using OPcache with opcache.validate_timestamps set to 0 or APC

[412] Fix | Delete

| with apc.stat set to 0 and Twig cache enabled, clearing the template

[413] Fix | Delete

| cache won't update the cache, set to true to get around this.

[414] Fix | Delete

|

[415] Fix | Delete

*/

[416] Fix | Delete

[417] Fix | Delete

'forceBytecodeInvalidation' => true,

[418] Fix | Delete

[419] Fix | Delete

/*

[420] Fix | Delete

|--------------------------------------------------------------------------

[421] Fix | Delete

| Twig Strict Variables

[422] Fix | Delete

|--------------------------------------------------------------------------

[423] Fix | Delete

|

[424] Fix | Delete

| If strict_variables is disabled, Twig will silently ignore invalid

[425] Fix | Delete

| variables (variables and or attributes/methods that do not exist) and

[426] Fix | Delete

| replace them with a null value. When enabled, Twig throws an exception

[427] Fix | Delete

| instead. If set to null, it is enabled when debug mode (app.debug) is

[428] Fix | Delete

| enabled.

[429] Fix | Delete

|

[430] Fix | Delete

*/

[431] Fix | Delete

[432] Fix | Delete

'enableTwigStrictVariables' => false,

[433] Fix | Delete

[434] Fix | Delete

/*

[435] Fix | Delete

|--------------------------------------------------------------------------

[436] Fix | Delete

| Base Directory Restriction

[437] Fix | Delete

|--------------------------------------------------------------------------

[438] Fix | Delete

|

[439] Fix | Delete

| Restricts loading backend template and config files to within the base

[440] Fix | Delete

| directory of the application.

[441] Fix | Delete

|

[442] Fix | Delete

| WARNING: This should always be enabled for security reasons. However, in

[443] Fix | Delete

| some cases you may need to disable this; for instance when developing

[444] Fix | Delete

| plugins that are stored elsewhere in the filesystem for organizational

[445] Fix | Delete

| reasons and then symlinked into the application plugins/ directory.

[446] Fix | Delete

|

[447] Fix | Delete

| NEVER have this disabled in production.

[448] Fix | Delete

|

[449] Fix | Delete

*/

[450] Fix | Delete

[451] Fix | Delete

'restrictBaseDir' => env('RESTRICT_BASE_DIR', true),

[452] Fix | Delete

[453] Fix | Delete

/*

[454] Fix | Delete

|--------------------------------------------------------------------------

[455] Fix | Delete

| Backend Service Worker

[456] Fix | Delete

|--------------------------------------------------------------------------

[457] Fix | Delete

|

[458] Fix | Delete

| Allow plugins to run Service Workers in the backend.

[459] Fix | Delete

|

[460] Fix | Delete

| WARNING: This should always be disabled for security reasons as Service

[461] Fix | Delete

| Workers can be hijacked and used to run XSS into the backend. Turning

[462] Fix | Delete

| this feature on can create a conflict if you have a frontend Service

[463] Fix | Delete

| Worker running. The 'scope' needs to be correctly set and not have a

[464] Fix | Delete

| duplicate subfolder structure on the frontend, otherwise it will run

[465] Fix | Delete

| on both the frontend and backend of your website.

[466] Fix | Delete

|

[467] Fix | Delete

| true - allow service workers to run in the backend

[468] Fix | Delete

|

[469] Fix | Delete

| false - disallow service workers to run in the backend

[470] Fix | Delete

|

[471] Fix | Delete

*/

[472] Fix | Delete

[473] Fix | Delete

'enableBackendServiceWorkers' => false,

[474] Fix | Delete

];

[475] Fix | Delete

[476] Fix | Delete