root / drupal7 / sites / settings.global.php @ 4da4932d
| 1 | 85ad3d82 | Assos Assos | <?php
|
|---|---|---|---|
| 2 | |||
| 3 | /**
|
||
| 4 | * @file
|
||
| 5 | * Drupal site-specific configuration file.
|
||
| 6 | *
|
||
| 7 | * IMPORTANT NOTE:
|
||
| 8 | * This file may have been set to read-only by the Drupal installation program.
|
||
| 9 | * If you make changes to this file, be sure to protect it again after making
|
||
| 10 | * your modifications. Failure to remove write permissions to this file is a
|
||
| 11 | * security risk.
|
||
| 12 | *
|
||
| 13 | * The configuration file to be loaded is based upon the rules below. However
|
||
| 14 | * if the multisite aliasing file named sites/sites.php is present, it will be
|
||
| 15 | * loaded, and the aliases in the array $sites will override the default
|
||
| 16 | * directory rules below. See sites/example.sites.php for more information about
|
||
| 17 | * aliases.
|
||
| 18 | *
|
||
| 19 | * The configuration directory will be discovered by stripping the website's
|
||
| 20 | * hostname from left to right and pathname from right to left. The first
|
||
| 21 | * configuration file found will be used and any others will be ignored. If no
|
||
| 22 | * other configuration file is found then the default configuration file at
|
||
| 23 | * 'sites/default' will be used.
|
||
| 24 | *
|
||
| 25 | * For example, for a fictitious site installed at
|
||
| 26 | * http://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
|
||
| 27 | * for in the following directories:
|
||
| 28 | *
|
||
| 29 | * - sites/8080.www.drupal.org.mysite.test
|
||
| 30 | * - sites/www.drupal.org.mysite.test
|
||
| 31 | * - sites/drupal.org.mysite.test
|
||
| 32 | * - sites/org.mysite.test
|
||
| 33 | *
|
||
| 34 | * - sites/8080.www.drupal.org.mysite
|
||
| 35 | * - sites/www.drupal.org.mysite
|
||
| 36 | * - sites/drupal.org.mysite
|
||
| 37 | * - sites/org.mysite
|
||
| 38 | *
|
||
| 39 | * - sites/8080.www.drupal.org
|
||
| 40 | * - sites/www.drupal.org
|
||
| 41 | * - sites/drupal.org
|
||
| 42 | * - sites/org
|
||
| 43 | *
|
||
| 44 | * - sites/default
|
||
| 45 | *
|
||
| 46 | * Note that if you are installing on a non-standard port number, prefix the
|
||
| 47 | * hostname with that number. For example,
|
||
| 48 | * http://www.drupal.org:8080/mysite/test/ could be loaded from
|
||
| 49 | * sites/8080.www.drupal.org.mysite.test/.
|
||
| 50 | *
|
||
| 51 | * @see example.sites.php
|
||
| 52 | * @see conf_path()
|
||
| 53 | */
|
||
| 54 | |||
| 55 | /**
|
||
| 56 | * Database settings:
|
||
| 57 | *
|
||
| 58 | * The $databases array specifies the database connection or
|
||
| 59 | * connections that Drupal may use. Drupal is able to connect
|
||
| 60 | * to multiple databases, including multiple types of databases,
|
||
| 61 | * during the same request.
|
||
| 62 | *
|
||
| 63 | * Each database connection is specified as an array of settings,
|
||
| 64 | * similar to the following:
|
||
| 65 | * @code
|
||
| 66 | * array(
|
||
| 67 | * 'driver' => 'mysql',
|
||
| 68 | * 'database' => 'databasename',
|
||
| 69 | * 'username' => 'username',
|
||
| 70 | * 'password' => 'password',
|
||
| 71 | * 'host' => 'localhost',
|
||
| 72 | * 'port' => 3306,
|
||
| 73 | * 'prefix' => 'myprefix_',
|
||
| 74 | * 'collation' => 'utf8_general_ci',
|
||
| 75 | * );
|
||
| 76 | * @endcode
|
||
| 77 | *
|
||
| 78 | * The "driver" property indicates what Drupal database driver the
|
||
| 79 | * connection should use. This is usually the same as the name of the
|
||
| 80 | * database type, such as mysql or sqlite, but not always. The other
|
||
| 81 | * properties will vary depending on the driver. For SQLite, you must
|
||
| 82 | * specify a database file name in a directory that is writable by the
|
||
| 83 | * webserver. For most other drivers, you must specify a
|
||
| 84 | * username, password, host, and database name.
|
||
| 85 | *
|
||
| 86 | * Some database engines support transactions. In order to enable
|
||
| 87 | * transaction support for a given database, set the 'transactions' key
|
||
| 88 | * to TRUE. To disable it, set it to FALSE. Note that the default value
|
||
| 89 | * varies by driver. For MySQL, the default is FALSE since MyISAM tables
|
||
| 90 | * do not support transactions.
|
||
| 91 | *
|
||
| 92 | * For each database, you may optionally specify multiple "target" databases.
|
||
| 93 | * A target database allows Drupal to try to send certain queries to a
|
||
| 94 | * different database if it can but fall back to the default connection if not.
|
||
| 95 | * That is useful for master/slave replication, as Drupal may try to connect
|
||
| 96 | * to a slave server when appropriate and if one is not available will simply
|
||
| 97 | * fall back to the single master server.
|
||
| 98 | *
|
||
| 99 | * The general format for the $databases array is as follows:
|
||
| 100 | * @code
|
||
| 101 | * $databases['default']['default'] = $info_array;
|
||
| 102 | * $databases['default']['slave'][] = $info_array;
|
||
| 103 | * $databases['default']['slave'][] = $info_array;
|
||
| 104 | * $databases['extra']['default'] = $info_array;
|
||
| 105 | * @endcode
|
||
| 106 | *
|
||
| 107 | * In the above example, $info_array is an array of settings described above.
|
||
| 108 | * The first line sets a "default" database that has one master database
|
||
| 109 | * (the second level default). The second and third lines create an array
|
||
| 110 | * of potential slave databases. Drupal will select one at random for a given
|
||
| 111 | * request as needed. The fourth line creates a new database with a name of
|
||
| 112 | * "extra".
|
||
| 113 | *
|
||
| 114 | * For a single database configuration, the following is sufficient:
|
||
| 115 | * @code
|
||
| 116 | * $databases['default']['default'] = array(
|
||
| 117 | * 'driver' => 'mysql',
|
||
| 118 | * 'database' => 'databasename',
|
||
| 119 | * 'username' => 'username',
|
||
| 120 | * 'password' => 'password',
|
||
| 121 | * 'host' => 'localhost',
|
||
| 122 | * 'prefix' => 'main_',
|
||
| 123 | * 'collation' => 'utf8_general_ci',
|
||
| 124 | * );
|
||
| 125 | * @endcode
|
||
| 126 | *
|
||
| 127 | * You can optionally set prefixes for some or all database table names
|
||
| 128 | * by using the 'prefix' setting. If a prefix is specified, the table
|
||
| 129 | * name will be prepended with its value. Be sure to use valid database
|
||
| 130 | * characters only, usually alphanumeric and underscore. If no prefixes
|
||
| 131 | * are desired, leave it as an empty string ''.
|
||
| 132 | *
|
||
| 133 | * To have all database names prefixed, set 'prefix' as a string:
|
||
| 134 | * @code
|
||
| 135 | * 'prefix' => 'main_',
|
||
| 136 | * @endcode
|
||
| 137 | * To provide prefixes for specific tables, set 'prefix' as an array.
|
||
| 138 | * The array's keys are the table names and the values are the prefixes.
|
||
| 139 | * The 'default' element is mandatory and holds the prefix for any tables
|
||
| 140 | * not specified elsewhere in the array. Example:
|
||
| 141 | * @code
|
||
| 142 | * 'prefix' => array(
|
||
| 143 | * 'default' => 'main_',
|
||
| 144 | * 'users' => 'shared_',
|
||
| 145 | * 'sessions' => 'shared_',
|
||
| 146 | * 'role' => 'shared_',
|
||
| 147 | * 'authmap' => 'shared_',
|
||
| 148 | * ),
|
||
| 149 | * @endcode
|
||
| 150 | * You can also use a reference to a schema/database as a prefix. This may be
|
||
| 151 | * useful if your Drupal installation exists in a schema that is not the default
|
||
| 152 | * or you want to access several databases from the same code base at the same
|
||
| 153 | * time.
|
||
| 154 | * Example:
|
||
| 155 | * @code
|
||
| 156 | * 'prefix' => array(
|
||
| 157 | * 'default' => 'main.',
|
||
| 158 | * 'users' => 'shared.',
|
||
| 159 | * 'sessions' => 'shared.',
|
||
| 160 | * 'role' => 'shared.',
|
||
| 161 | * 'authmap' => 'shared.',
|
||
| 162 | * );
|
||
| 163 | * @endcode
|
||
| 164 | * NOTE: MySQL and SQLite's definition of a schema is a database.
|
||
| 165 | *
|
||
| 166 | * Advanced users can add or override initial commands to execute when
|
||
| 167 | * connecting to the database server, as well as PDO connection settings. For
|
||
| 168 | * example, to enable MySQL SELECT queries to exceed the max_join_size system
|
||
| 169 | * variable, and to reduce the database connection timeout to 5 seconds:
|
||
| 170 | *
|
||
| 171 | * @code
|
||
| 172 | * $databases['default']['default'] = array(
|
||
| 173 | * 'init_commands' => array(
|
||
| 174 | * 'big_selects' => 'SET SQL_BIG_SELECTS=1',
|
||
| 175 | * ),
|
||
| 176 | * 'pdo' => array(
|
||
| 177 | * PDO::ATTR_TIMEOUT => 5,
|
||
| 178 | * ),
|
||
| 179 | * );
|
||
| 180 | * @endcode
|
||
| 181 | *
|
||
| 182 | * WARNING: These defaults are designed for database portability. Changing them
|
||
| 183 | * may cause unexpected behavior, including potential data loss.
|
||
| 184 | *
|
||
| 185 | * @see DatabaseConnection_mysql::__construct
|
||
| 186 | * @see DatabaseConnection_pgsql::__construct
|
||
| 187 | * @see DatabaseConnection_sqlite::__construct
|
||
| 188 | *
|
||
| 189 | * Database configuration format:
|
||
| 190 | * @code
|
||
| 191 | * $databases['default']['default'] = array(
|
||
| 192 | * 'driver' => 'mysql',
|
||
| 193 | * 'database' => 'databasename',
|
||
| 194 | * 'username' => 'username',
|
||
| 195 | * 'password' => 'password',
|
||
| 196 | * 'host' => 'localhost',
|
||
| 197 | * 'prefix' => '',
|
||
| 198 | * );
|
||
| 199 | * $databases['default']['default'] = array(
|
||
| 200 | * 'driver' => 'pgsql',
|
||
| 201 | * 'database' => 'databasename',
|
||
| 202 | * 'username' => 'username',
|
||
| 203 | * 'password' => 'password',
|
||
| 204 | * 'host' => 'localhost',
|
||
| 205 | * 'prefix' => '',
|
||
| 206 | * );
|
||
| 207 | * $databases['default']['default'] = array(
|
||
| 208 | * 'driver' => 'sqlite',
|
||
| 209 | * 'database' => '/path/to/databasefilename',
|
||
| 210 | * );
|
||
| 211 | * @endcode
|
||
| 212 | */
|
||
| 213 | |||
| 214 | /**
|
||
| 215 | * Access control for update.php script.
|
||
| 216 | *
|
||
| 217 | * If you are updating your Drupal installation using the update.php script but
|
||
| 218 | * are not logged in using either an account with the "Administer software
|
||
| 219 | * updates" permission or the site maintenance account (the account that was
|
||
| 220 | * created during installation), you will need to modify the access check
|
||
| 221 | * statement below. Change the FALSE to a TRUE to disable the access check.
|
||
| 222 | * After finishing the upgrade, be sure to open this file again and change the
|
||
| 223 | * TRUE back to a FALSE!
|
||
| 224 | */
|
||
| 225 | $update_free_access = FALSE; |
||
| 226 | |||
| 227 | /**
|
||
| 228 | * Salt for one-time login links and cancel links, form tokens, etc.
|
||
| 229 | *
|
||
| 230 | * This variable will be set to a random value by the installer. All one-time
|
||
| 231 | * login links will be invalidated if the value is changed. Note that if your
|
||
| 232 | * site is deployed on a cluster of web servers, you must ensure that this
|
||
| 233 | * variable has the same value on each server. If this variable is empty, a hash
|
||
| 234 | * of the serialized database credentials will be used as a fallback salt.
|
||
| 235 | *
|
||
| 236 | * For enhanced security, you may set this variable to a value using the
|
||
| 237 | * contents of a file outside your docroot that is never saved together
|
||
| 238 | * with any backups of your Drupal files and database.
|
||
| 239 | *
|
||
| 240 | * Example:
|
||
| 241 | * $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
|
||
| 242 | *
|
||
| 243 | */
|
||
| 244 | $drupal_hash_salt = ''; |
||
| 245 | |||
| 246 | /**
|
||
| 247 | * Base URL (optional).
|
||
| 248 | *
|
||
| 249 | * If Drupal is generating incorrect URLs on your site, which could
|
||
| 250 | * be in HTML headers (links to CSS and JS files) or visible links on pages
|
||
| 251 | * (such as in menus), uncomment the Base URL statement below (remove the
|
||
| 252 | * leading hash sign) and fill in the absolute URL to your Drupal installation.
|
||
| 253 | *
|
||
| 254 | * You might also want to force users to use a given domain.
|
||
| 255 | * See the .htaccess file for more information.
|
||
| 256 | *
|
||
| 257 | * Examples:
|
||
| 258 | * $base_url = 'http://www.example.com';
|
||
| 259 | * $base_url = 'http://www.example.com:8888';
|
||
| 260 | * $base_url = 'http://www.example.com/drupal';
|
||
| 261 | * $base_url = 'https://www.example.com:8888/drupal';
|
||
| 262 | *
|
||
| 263 | * It is not allowed to have a trailing slash; Drupal will add it
|
||
| 264 | * for you.
|
||
| 265 | */
|
||
| 266 | |||
| 267 | /**
|
||
| 268 | * PHP settings:
|
||
| 269 | *
|
||
| 270 | * To see what PHP settings are possible, including whether they can be set at
|
||
| 271 | * runtime (by using ini_set()), read the PHP documentation:
|
||
| 272 | * http://www.php.net/manual/en/ini.list.php
|
||
| 273 | * See drupal_environment_initialize() in includes/bootstrap.inc for required
|
||
| 274 | * runtime settings and the .htaccess file for non-runtime settings. Settings
|
||
| 275 | * defined there should not be duplicated here so as to avoid conflict issues.
|
||
| 276 | */
|
||
| 277 | |||
| 278 | /**
|
||
| 279 | * Some distributions of Linux (most notably Debian) ship their PHP
|
||
| 280 | * installations with garbage collection (gc) disabled. Since Drupal depends on
|
||
| 281 | * PHP's garbage collection for clearing sessions, ensure that garbage
|
||
| 282 | * collection occurs by using the most common settings.
|
||
| 283 | */
|
||
| 284 | ini_set('session.gc_probability', 1); |
||
| 285 | ini_set('session.gc_divisor', 100); |
||
| 286 | |||
| 287 | /**
|
||
| 288 | * Set session lifetime (in seconds), i.e. the time from the user's last visit
|
||
| 289 | * to the active session may be deleted by the session garbage collector. When
|
||
| 290 | * a session is deleted, authenticated users are logged out, and the contents
|
||
| 291 | * of the user's $_SESSION variable is discarded.
|
||
| 292 | */
|
||
| 293 | ini_set('session.gc_maxlifetime', 200000); |
||
| 294 | |||
| 295 | /**
|
||
| 296 | * Set session cookie lifetime (in seconds), i.e. the time from the session is
|
||
| 297 | * created to the cookie expires, i.e. when the browser is expected to discard
|
||
| 298 | * the cookie. The value 0 means "until the browser is closed".
|
||
| 299 | */
|
||
| 300 | ini_set('session.cookie_lifetime', 2000000); |
||
| 301 | |||
| 302 | /**
|
||
| 303 | * If you encounter a situation where users post a large amount of text, and
|
||
| 304 | * the result is stripped out upon viewing but can still be edited, Drupal's
|
||
| 305 | * output filter may not have sufficient memory to process it. If you
|
||
| 306 | * experience this issue, you may wish to uncomment the following two lines
|
||
| 307 | * and increase the limits of these variables. For more information, see
|
||
| 308 | * http://php.net/manual/en/pcre.configuration.php.
|
||
| 309 | */
|
||
| 310 | # ini_set('pcre.backtrack_limit', 200000);
|
||
| 311 | # ini_set('pcre.recursion_limit', 200000);
|
||
| 312 | |||
| 313 | /**
|
||
| 314 | * Drupal automatically generates a unique session cookie name for each site
|
||
| 315 | * based on its full domain name. If you have multiple domains pointing at the
|
||
| 316 | * same Drupal site, you can either redirect them all to a single domain (see
|
||
| 317 | * comment in .htaccess), or uncomment the line below and specify their shared
|
||
| 318 | * base domain. Doing so assures that users remain logged in as they cross
|
||
| 319 | * between your various domains. Make sure to always start the $cookie_domain
|
||
| 320 | * with a leading dot, as per RFC 2109.
|
||
| 321 | */
|
||
| 322 | # $cookie_domain = '.example.com';
|
||
| 323 | |||
| 324 | /**
|
||
| 325 | * Variable overrides:
|
||
| 326 | *
|
||
| 327 | * To override specific entries in the 'variable' table for this site,
|
||
| 328 | * set them here. You usually don't need to use this feature. This is
|
||
| 329 | * useful in a configuration file for a vhost or directory, rather than
|
||
| 330 | * the default settings.php. Any configuration setting from the 'variable'
|
||
| 331 | * table can be given a new value. Note that any values you provide in
|
||
| 332 | * these variable overrides will not be modifiable from the Drupal
|
||
| 333 | * administration interface.
|
||
| 334 | *
|
||
| 335 | * The following overrides are examples:
|
||
| 336 | * - site_name: Defines the site's name.
|
||
| 337 | * - theme_default: Defines the default theme for this site.
|
||
| 338 | * - anonymous: Defines the human-readable name of anonymous users.
|
||
| 339 | * Remove the leading hash signs to enable.
|
||
| 340 | */
|
||
| 341 | # $conf['site_name'] = 'My Drupal site';
|
||
| 342 | # $conf['theme_default'] = 'garland';
|
||
| 343 | # $conf['anonymous'] = 'Visitor';
|
||
| 344 | |||
| 345 | /**
|
||
| 346 | * A custom theme can be set for the offline page. This applies when the site
|
||
| 347 | * is explicitly set to maintenance mode through the administration page or when
|
||
| 348 | * the database is inactive due to an error. It can be set through the
|
||
| 349 | * 'maintenance_theme' key. The template file should also be copied into the
|
||
| 350 | * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
|
||
| 351 | * Note: This setting does not apply to installation and update pages.
|
||
| 352 | */
|
||
| 353 | # $conf['maintenance_theme'] = 'bartik';
|
||
| 354 | |||
| 355 | /**
|
||
| 356 | * Reverse Proxy Configuration:
|
||
| 357 | *
|
||
| 358 | * Reverse proxy servers are often used to enhance the performance
|
||
| 359 | * of heavily visited sites and may also provide other site caching,
|
||
| 360 | * security, or encryption benefits. In an environment where Drupal
|
||
| 361 | * is behind a reverse proxy, the real IP address of the client should
|
||
| 362 | * be determined such that the correct client IP address is available
|
||
| 363 | * to Drupal's logging, statistics, and access management systems. In
|
||
| 364 | * the most simple scenario, the proxy server will add an
|
||
| 365 | * X-Forwarded-For header to the request that contains the client IP
|
||
| 366 | * address. However, HTTP headers are vulnerable to spoofing, where a
|
||
| 367 | * malicious client could bypass restrictions by setting the
|
||
| 368 | * X-Forwarded-For header directly. Therefore, Drupal's proxy
|
||
| 369 | * configuration requires the IP addresses of all remote proxies to be
|
||
| 370 | * specified in $conf['reverse_proxy_addresses'] to work correctly.
|
||
| 371 | *
|
||
| 372 | * Enable this setting to get Drupal to determine the client IP from
|
||
| 373 | * the X-Forwarded-For header (or $conf['reverse_proxy_header'] if set).
|
||
| 374 | * If you are unsure about this setting, do not have a reverse proxy,
|
||
| 375 | * or Drupal operates in a shared hosting environment, this setting
|
||
| 376 | * should remain commented out.
|
||
| 377 | *
|
||
| 378 | * In order for this setting to be used you must specify every possible
|
||
| 379 | * reverse proxy IP address in $conf['reverse_proxy_addresses'].
|
||
| 380 | * If a complete list of reverse proxies is not available in your
|
||
| 381 | * environment (for example, if you use a CDN) you may set the
|
||
| 382 | * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
|
||
| 383 | * Be aware, however, that it is likely that this would allow IP
|
||
| 384 | * address spoofing unless more advanced precautions are taken.
|
||
| 385 | */
|
||
| 386 | # $conf['reverse_proxy'] = TRUE;
|
||
| 387 | |||
| 388 | /**
|
||
| 389 | * Specify every reverse proxy IP address in your environment.
|
||
| 390 | * This setting is required if $conf['reverse_proxy'] is TRUE.
|
||
| 391 | */
|
||
| 392 | # $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
|
||
| 393 | |||
| 394 | /**
|
||
| 395 | * Set this value if your proxy server sends the client IP in a header
|
||
| 396 | * other than X-Forwarded-For.
|
||
| 397 | */
|
||
| 398 | # $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
|
||
| 399 | |||
| 400 | /**
|
||
| 401 | * Page caching:
|
||
| 402 | *
|
||
| 403 | * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
|
||
| 404 | * views. This tells a HTTP proxy that it may return a page from its local
|
||
| 405 | * cache without contacting the web server, if the user sends the same Cookie
|
||
| 406 | * header as the user who originally requested the cached page. Without "Vary:
|
||
| 407 | * Cookie", authenticated users would also be served the anonymous page from
|
||
| 408 | * the cache. If the site has mostly anonymous users except a few known
|
||
| 409 | * editors/administrators, the Vary header can be omitted. This allows for
|
||
| 410 | * better caching in HTTP proxies (including reverse proxies), i.e. even if
|
||
| 411 | * clients send different cookies, they still get content served from the cache.
|
||
| 412 | * However, authenticated users should access the site directly (i.e. not use an
|
||
| 413 | * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
|
||
| 414 | * getting cached pages from the proxy.
|
||
| 415 | */
|
||
| 416 | # $conf['omit_vary_cookie'] = TRUE;
|
||
| 417 | |||
| 418 | /**
|
||
| 419 | * CSS/JS aggregated file gzip compression:
|
||
| 420 | *
|
||
| 421 | * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
|
||
| 422 | * store a gzip compressed (.gz) copy of the aggregated files. If this file is
|
||
| 423 | * available then rewrite rules in the default .htaccess file will serve these
|
||
| 424 | * files to browsers that accept gzip encoded content. This allows pages to load
|
||
| 425 | * faster for these users and has minimal impact on server load. If you are
|
||
| 426 | * using a webserver other than Apache httpd, or a caching reverse proxy that is
|
||
| 427 | * configured to cache and compress these files itself you may want to uncomment
|
||
| 428 | * one or both of the below lines, which will prevent gzip files being stored.
|
||
| 429 | */
|
||
| 430 | # $conf['css_gzip_compression'] = FALSE;
|
||
| 431 | # $conf['js_gzip_compression'] = FALSE;
|
||
| 432 | |||
| 433 | /**
|
||
| 434 | * String overrides:
|
||
| 435 | *
|
||
| 436 | * To override specific strings on your site with or without enabling the Locale
|
||
| 437 | * module, add an entry to this list. This functionality allows you to change
|
||
| 438 | * a small number of your site's default English language interface strings.
|
||
| 439 | *
|
||
| 440 | * Remove the leading hash signs to enable.
|
||
| 441 | */
|
||
| 442 | # $conf['locale_custom_strings_en'][''] = array(
|
||
| 443 | # 'forum' => 'Discussion board',
|
||
| 444 | # '@count min' => '@count minutes',
|
||
| 445 | # );
|
||
| 446 | |||
| 447 | /**
|
||
| 448 | *
|
||
| 449 | * IP blocking:
|
||
| 450 | *
|
||
| 451 | * To bypass database queries for denied IP addresses, use this setting.
|
||
| 452 | * Drupal queries the {blocked_ips} table by default on every page request
|
||
| 453 | * for both authenticated and anonymous users. This allows the system to
|
||
| 454 | * block IP addresses from within the administrative interface and before any
|
||
| 455 | * modules are loaded. However on high traffic websites you may want to avoid
|
||
| 456 | * this query, allowing you to bypass database access altogether for anonymous
|
||
| 457 | * users under certain caching configurations.
|
||
| 458 | *
|
||
| 459 | * If using this setting, you will need to add back any IP addresses which
|
||
| 460 | * you may have blocked via the administrative interface. Each element of this
|
||
| 461 | * array represents a blocked IP address. Uncommenting the array and leaving it
|
||
| 462 | * empty will have the effect of disabling IP blocking on your site.
|
||
| 463 | *
|
||
| 464 | * Remove the leading hash signs to enable.
|
||
| 465 | */
|
||
| 466 | # $conf['blocked_ips'] = array(
|
||
| 467 | # 'a.b.c.d',
|
||
| 468 | # );
|
||
| 469 | |||
| 470 | /**
|
||
| 471 | * Fast 404 pages:
|
||
| 472 | *
|
||
| 473 | * Drupal can generate fully themed 404 pages. However, some of these responses
|
||
| 474 | * are for images or other resource files that are not displayed to the user.
|
||
| 475 | * This can waste bandwidth, and also generate server load.
|
||
| 476 | *
|
||
| 477 | * The options below return a simple, fast 404 page for URLs matching a
|
||
| 478 | * specific pattern:
|
||
| 479 | * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
|
||
| 480 | * such as images generated by image styles, or dynamically-resized images.
|
||
| 481 | * If you need to add more paths, you can add '|path' to the expression.
|
||
| 482 | * - 404_fast_paths: A regular expression to match paths that should return a
|
||
| 483 | * simple 404 page, rather than the fully themed 404 page. If you don't have
|
||
| 484 | * any aliases ending in htm or html you can add '|s?html?' to the expression.
|
||
| 485 | * - 404_fast_html: The html to return for simple 404 pages.
|
||
| 486 | *
|
||
| 487 | * Add leading hash signs if you would like to disable this functionality.
|
||
| 488 | */
|
||
| 489 | $conf['404_fast_paths_exclude'] = '/\/(?:styles)\//'; |
||
| 490 | $conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i'; |
||
| 491 | $conf['404_fast_html'] = '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>404 Not Found</title></head><body><h1>Not Found</h1><p>The requested URL "@path" was not found on this server.</p></body></html>'; |
||
| 492 | |||
| 493 | /**
|
||
| 494 | * By default the page request process will return a fast 404 page for missing
|
||
| 495 | * files if they match the regular expression set in '404_fast_paths' and not
|
||
| 496 | * '404_fast_paths_exclude' above. 404 errors will simultaneously be logged in
|
||
| 497 | * the Drupal system log.
|
||
| 498 | *
|
||
| 499 | * You can choose to return a fast 404 page earlier for missing pages (as soon
|
||
| 500 | * as settings.php is loaded) by uncommenting the line below. This speeds up
|
||
| 501 | * server response time when loading 404 error pages and prevents the 404 error
|
||
| 502 | * from being logged in the Drupal system log. In order to prevent valid pages
|
||
| 503 | * such as image styles and other generated content that may match the
|
||
| 504 | * '404_fast_html' regular expression from returning 404 errors, it is necessary
|
||
| 505 | * to add them to the '404_fast_paths_exclude' regular expression above. Make
|
||
| 506 | * sure that you understand the effects of this feature before uncommenting the
|
||
| 507 | * line below.
|
||
| 508 | */
|
||
| 509 | # drupal_fast_404();
|
||
| 510 | |||
| 511 | /**
|
||
| 512 | * External access proxy settings:
|
||
| 513 | *
|
||
| 514 | * If your site must access the Internet via a web proxy then you can enter
|
||
| 515 | * the proxy settings here. Currently only basic authentication is supported
|
||
| 516 | * by using the username and password variables. The proxy_user_agent variable
|
||
| 517 | * can be set to NULL for proxies that require no User-Agent header or to a
|
||
| 518 | * non-empty string for proxies that limit requests to a specific agent. The
|
||
| 519 | * proxy_exceptions variable is an array of host names to be accessed directly,
|
||
| 520 | * not via proxy.
|
||
| 521 | */
|
||
| 522 | # $conf['proxy_server'] = '';
|
||
| 523 | # $conf['proxy_port'] = 8080;
|
||
| 524 | # $conf['proxy_username'] = '';
|
||
| 525 | # $conf['proxy_password'] = '';
|
||
| 526 | # $conf['proxy_user_agent'] = '';
|
||
| 527 | # $conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
|
||
| 528 | |||
| 529 | /**
|
||
| 530 | * Authorized file system operations:
|
||
| 531 | *
|
||
| 532 | * The Update manager module included with Drupal provides a mechanism for
|
||
| 533 | * site administrators to securely install missing updates for the site
|
||
| 534 | * directly through the web user interface. On securely-configured servers,
|
||
| 535 | * the Update manager will require the administrator to provide SSH or FTP
|
||
| 536 | * credentials before allowing the installation to proceed; this allows the
|
||
| 537 | * site to update the new files as the user who owns all the Drupal files,
|
||
| 538 | * instead of as the user the webserver is running as. On servers where the
|
||
| 539 | * webserver user is itself the owner of the Drupal files, the administrator
|
||
| 540 | * will not be prompted for SSH or FTP credentials (note that these server
|
||
| 541 | * setups are common on shared hosting, but are inherently insecure).
|
||
| 542 | *
|
||
| 543 | * Some sites might wish to disable the above functionality, and only update
|
||
| 544 | * the code directly via SSH or FTP themselves. This setting completely
|
||
| 545 | * disables all functionality related to these authorized file operations.
|
||
| 546 | *
|
||
| 547 | * @see http://drupal.org/node/244924
|
||
| 548 | *
|
||
| 549 | * Remove the leading hash signs to disable.
|
||
| 550 | */
|
||
| 551 | $conf['allow_authorize_operations'] = FALSE; |