· 8 years ago · May 05, 2018, 03:16 PM
1<?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$databases = array (
214 'default' =>
215 array (
216 'default' =>
217 array (
218
219 'username' => 'root',
220 'password' => '',
221 'host' => 'localhost',
222 'database' => 'jiip_drupal',
223
224 'port' => '',
225 'driver' => 'mysql',
226 'prefix' => 'jiip_',
227
228 ),
229 ),
230);
231
232/**
233 * Access control for update.php script.
234 *
235 * If you are updating your Drupal installation using the update.php script but
236 * are not logged in using either an account with the "Administer software
237 * updates" permission or the site maintenance account (the account that was
238 * created during installation), you will need to modify the access check
239 * statement below. Change the FALSE to a TRUE to disable the access check.
240 * After finishing the upgrade, be sure to open this file again and change the
241 * TRUE back to a FALSE!
242 */
243$update_free_access = FALSE;
244
245/**
246 * Salt for one-time login links and cancel links, form tokens, etc.
247 *
248 * This variable will be set to a random value by the installer. All one-time
249 * login links will be invalidated if the value is changed. Note that if your
250 * site is deployed on a cluster of web servers, you must ensure that this
251 * variable has the same value on each server. If this variable is empty, a hash
252 * of the serialized database credentials will be used as a fallback salt.
253 *
254 * For enhanced security, you may set this variable to a value using the
255 * contents of a file outside your docroot that is never saved together
256 * with any backups of your Drupal files and database.
257 *
258 * Example:
259 * $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
260 *
261 */
262$drupal_hash_salt = '_Xxguy_IVAOJmX1VCTiUzhezzhL2nFvZYJ3ZQ4OILc0';
263
264/**
265 * Base URL (optional).
266 *
267 * If Drupal is generating incorrect URLs on your site, which could
268 * be in HTML headers (links to CSS and JS files) or visible links on pages
269 * (such as in menus), uncomment the Base URL statement below (remove the
270 * leading hash sign) and fill in the absolute URL to your Drupal installation.
271 *
272 * You might also want to force users to use a given domain.
273 * See the .htaccess file for more information.
274 *
275 * Examples:
276 * $base_url = 'http://www.example.com';
277 * $base_url = 'http://www.example.com:8888';
278 * $base_url = 'http://www.example.com/drupal';
279 * $base_url = 'https://www.example.com:8888/drupal';
280 *
281 * It is not allowed to have a trailing slash; Drupal will add it
282 * for you.
283 */
284# $base_url = 'http://www.example.com'; // NO trailing slash!
285
286/**
287 * PHP settings:
288 *
289 * To see what PHP settings are possible, including whether they can be set at
290 * runtime (by using ini_set()), read the PHP documentation:
291 * http://www.php.net/manual/ini.list.php
292 * See drupal_environment_initialize() in includes/bootstrap.inc for required
293 * runtime settings and the .htaccess file for non-runtime settings. Settings
294 * defined there should not be duplicated here so as to avoid conflict issues.
295 */
296
297/**
298 * Some distributions of Linux (most notably Debian) ship their PHP
299 * installations with garbage collection (gc) disabled. Since Drupal depends on
300 * PHP's garbage collection for clearing sessions, ensure that garbage
301 * collection occurs by using the most common settings.
302 */
303ini_set('session.gc_probability', 1);
304ini_set('session.gc_divisor', 100);
305
306/**
307 * Set session lifetime (in seconds), i.e. the time from the user's last visit
308 * to the active session may be deleted by the session garbage collector. When
309 * a session is deleted, authenticated users are logged out, and the contents
310 * of the user's $_SESSION variable is discarded.
311 */
312ini_set('session.gc_maxlifetime', 200000);
313
314/**
315 * Set session cookie lifetime (in seconds), i.e. the time from the session is
316 * created to the cookie expires, i.e. when the browser is expected to discard
317 * the cookie. The value 0 means "until the browser is closed".
318 */
319ini_set('session.cookie_lifetime', 2000000);
320
321/**
322 * If you encounter a situation where users post a large amount of text, and
323 * the result is stripped out upon viewing but can still be edited, Drupal's
324 * output filter may not have sufficient memory to process it. If you
325 * experience this issue, you may wish to uncomment the following two lines
326 * and increase the limits of these variables. For more information, see
327 * http://php.net/manual/pcre.configuration.php.
328 */
329# ini_set('pcre.backtrack_limit', 200000);
330# ini_set('pcre.recursion_limit', 200000);
331
332/**
333 * Drupal automatically generates a unique session cookie name for each site
334 * based on its full domain name. If you have multiple domains pointing at the
335 * same Drupal site, you can either redirect them all to a single domain (see
336 * comment in .htaccess), or uncomment the line below and specify their shared
337 * base domain. Doing so assures that users remain logged in as they cross
338 * between your various domains. Make sure to always start the $cookie_domain
339 * with a leading dot, as per RFC 2109.
340 */
341# $cookie_domain = '.example.com';
342
343/**
344 * Variable overrides:
345 *
346 * To override specific entries in the 'variable' table for this site,
347 * set them here. You usually don't need to use this feature. This is
348 * useful in a configuration file for a vhost or directory, rather than
349 * the default settings.php. Any configuration setting from the 'variable'
350 * table can be given a new value. Note that any values you provide in
351 * these variable overrides will not be modifiable from the Drupal
352 * administration interface.
353 *
354 * The following overrides are examples:
355 * - site_name: Defines the site's name.
356 * - theme_default: Defines the default theme for this site.
357 * - anonymous: Defines the human-readable name of anonymous users.
358 * Remove the leading hash signs to enable.
359 */
360# $conf['site_name'] = 'My Drupal site';
361# $conf['theme_default'] = 'garland';
362# $conf['anonymous'] = 'Visitor';
363
364/**
365 * A custom theme can be set for the offline page. This applies when the site
366 * is explicitly set to maintenance mode through the administration page or when
367 * the database is inactive due to an error. It can be set through the
368 * 'maintenance_theme' key. The template file should also be copied into the
369 * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
370 * Note: This setting does not apply to installation and update pages.
371 */
372# $conf['maintenance_theme'] = 'bartik';
373
374/**
375 * Reverse Proxy Configuration:
376 *
377 * Reverse proxy servers are often used to enhance the performance
378 * of heavily visited sites and may also provide other site caching,
379 * security, or encryption benefits. In an environment where Drupal
380 * is behind a reverse proxy, the real IP address of the client should
381 * be determined such that the correct client IP address is available
382 * to Drupal's logging, statistics, and access management systems. In
383 * the most simple scenario, the proxy server will add an
384 * X-Forwarded-For header to the request that contains the client IP
385 * address. However, HTTP headers are vulnerable to spoofing, where a
386 * malicious client could bypass restrictions by setting the
387 * X-Forwarded-For header directly. Therefore, Drupal's proxy
388 * configuration requires the IP addresses of all remote proxies to be
389 * specified in $conf['reverse_proxy_addresses'] to work correctly.
390 *
391 * Enable this setting to get Drupal to determine the client IP from
392 * the X-Forwarded-For header (or $conf['reverse_proxy_header'] if set).
393 * If you are unsure about this setting, do not have a reverse proxy,
394 * or Drupal operates in a shared hosting environment, this setting
395 * should remain commented out.
396 *
397 * In order for this setting to be used you must specify every possible
398 * reverse proxy IP address in $conf['reverse_proxy_addresses'].
399 * If a complete list of reverse proxies is not available in your
400 * environment (for example, if you use a CDN) you may set the
401 * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
402 * Be aware, however, that it is likely that this would allow IP
403 * address spoofing unless more advanced precautions are taken.
404 */
405# $conf['reverse_proxy'] = TRUE;
406
407/**
408 * Specify every reverse proxy IP address in your environment.
409 * This setting is required if $conf['reverse_proxy'] is TRUE.
410 */
411# $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
412
413/**
414 * Set this value if your proxy server sends the client IP in a header
415 * other than X-Forwarded-For.
416 */
417# $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
418
419/**
420 * Page caching:
421 *
422 * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
423 * views. This tells a HTTP proxy that it may return a page from its local
424 * cache without contacting the web server, if the user sends the same Cookie
425 * header as the user who originally requested the cached page. Without "Vary:
426 * Cookie", authenticated users would also be served the anonymous page from
427 * the cache. If the site has mostly anonymous users except a few known
428 * editors/administrators, the Vary header can be omitted. This allows for
429 * better caching in HTTP proxies (including reverse proxies), i.e. even if
430 * clients send different cookies, they still get content served from the cache.
431 * However, authenticated users should access the site directly (i.e. not use an
432 * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
433 * getting cached pages from the proxy.
434 */
435# $conf['omit_vary_cookie'] = TRUE;
436
437/**
438 * CSS/JS aggregated file gzip compression:
439 *
440 * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
441 * store a gzip compressed (.gz) copy of the aggregated files. If this file is
442 * available then rewrite rules in the default .htaccess file will serve these
443 * files to browsers that accept gzip encoded content. This allows pages to load
444 * faster for these users and has minimal impact on server load. If you are
445 * using a webserver other than Apache httpd, or a caching reverse proxy that is
446 * configured to cache and compress these files itself you may want to uncomment
447 * one or both of the below lines, which will prevent gzip files being stored.
448 */
449# $conf['css_gzip_compression'] = FALSE;
450# $conf['js_gzip_compression'] = FALSE;
451
452/**
453 * String overrides:
454 *
455 * To override specific strings on your site with or without enabling the Locale
456 * module, add an entry to this list. This functionality allows you to change
457 * a small number of your site's default English language interface strings.
458 *
459 * Remove the leading hash signs to enable.
460 */
461# $conf['locale_custom_strings_en'][''] = array(
462# 'forum' => 'Discussion board',
463# '@count min' => '@count minutes',
464# );
465
466/**
467 *
468 * IP blocking:
469 *
470 * To bypass database queries for denied IP addresses, use this setting.
471 * Drupal queries the {blocked_ips} table by default on every page request
472 * for both authenticated and anonymous users. This allows the system to
473 * block IP addresses from within the administrative interface and before any
474 * modules are loaded. However on high traffic websites you may want to avoid
475 * this query, allowing you to bypass database access altogether for anonymous
476 * users under certain caching configurations.
477 *
478 * If using this setting, you will need to add back any IP addresses which
479 * you may have blocked via the administrative interface. Each element of this
480 * array represents a blocked IP address. Uncommenting the array and leaving it
481 * empty will have the effect of disabling IP blocking on your site.
482 *
483 * Remove the leading hash signs to enable.
484 */
485# $conf['blocked_ips'] = array(
486# 'a.b.c.d',
487# );
488
489/**
490 * Fast 404 pages:
491 *
492 * Drupal can generate fully themed 404 pages. However, some of these responses
493 * are for images or other resource files that are not displayed to the user.
494 * This can waste bandwidth, and also generate server load.
495 *
496 * The options below return a simple, fast 404 page for URLs matching a
497 * specific pattern:
498 * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
499 * such as images generated by image styles, or dynamically-resized images.
500 * If you need to add more paths, you can add '|path' to the expression.
501 * - 404_fast_paths: A regular expression to match paths that should return a
502 * simple 404 page, rather than the fully themed 404 page. If you don't have
503 * any aliases ending in htm or html you can add '|s?html?' to the expression.
504 * - 404_fast_html: The html to return for simple 404 pages.
505 *
506 * Add leading hash signs if you would like to disable this functionality.
507 */
508$conf['404_fast_paths_exclude'] = '/\/(?:styles)\//';
509$conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
510$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>';
511
512/**
513 * By default the page request process will return a fast 404 page for missing
514 * files if they match the regular expression set in '404_fast_paths' and not
515 * '404_fast_paths_exclude' above. 404 errors will simultaneously be logged in
516 * the Drupal system log.
517 *
518 * You can choose to return a fast 404 page earlier for missing pages (as soon
519 * as settings.php is loaded) by uncommenting the line below. This speeds up
520 * server response time when loading 404 error pages and prevents the 404 error
521 * from being logged in the Drupal system log. In order to prevent valid pages
522 * such as image styles and other generated content that may match the
523 * '404_fast_html' regular expression from returning 404 errors, it is necessary
524 * to add them to the '404_fast_paths_exclude' regular expression above. Make
525 * sure that you understand the effects of this feature before uncommenting the
526 * line below.
527 */
528# drupal_fast_404();
529
530/**
531 * External access proxy settings:
532 *
533 * If your site must access the Internet via a web proxy then you can enter
534 * the proxy settings here. Currently only basic authentication is supported
535 * by using the username and password variables. The proxy_user_agent variable
536 * can be set to NULL for proxies that require no User-Agent header or to a
537 * non-empty string for proxies that limit requests to a specific agent. The
538 * proxy_exceptions variable is an array of host names to be accessed directly,
539 * not via proxy.
540 */
541# $conf['proxy_server'] = '';
542# $conf['proxy_port'] = 8080;
543# $conf['proxy_username'] = '';
544# $conf['proxy_password'] = '';
545# $conf['proxy_user_agent'] = '';
546# $conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
547
548/**
549 * Authorized file system operations:
550 *
551 * The Update manager module included with Drupal provides a mechanism for
552 * site administrators to securely install missing updates for the site
553 * directly through the web user interface. On securely-configured servers,
554 * the Update manager will require the administrator to provide SSH or FTP
555 * credentials before allowing the installation to proceed; this allows the
556 * site to update the new files as the user who owns all the Drupal files,
557 * instead of as the user the webserver is running as. On servers where the
558 * webserver user is itself the owner of the Drupal files, the administrator
559 * will not be prompted for SSH or FTP credentials (note that these server
560 * setups are common on shared hosting, but are inherently insecure).
561 *
562 * Some sites might wish to disable the above functionality, and only update
563 * the code directly via SSH or FTP themselves. This setting completely
564 * disables all functionality related to these authorized file operations.
565 *
566 * @see http://drupal.org/node/244924
567 *
568 * Remove the leading hash signs to disable.
569 */
570# $conf['allow_authorize_operations'] = FALSE;
571ini_set('memory_limit', '128M');
572ini_set('upload_max_filesize','128M');
573ini_set('post_mqx_size', '128M');
574
575
576error_reporting(E_ALL);
577ini_set('display_errors', TRUE);
578ini_set('display_startup_errors', TRUE);