Ticket #29878: wp-config-sample.diff

wp-config-sample.php

@@ -66 +66 @@
  *
  * Change this to true to enable the display of notices during development.
  * It is strongly recommended that plugin and theme developers use WP_DEBUG
- * in their development environments.
+ * in their development environments. See additional debug options in the 
+ * advanced options section below.
  */
 define('WP_DEBUG', false);
 
+// ** Advanced Options - Only edit if you know what you're doing ** //
+
+/**
+ * Empty Trash
+ * 
+ * Controls the number of days before WordPress permanently deletes posts, 
+ * pages, attachments, and comments, from the trash bin. The default is 30 days:.
+ */
+// define( 'EMPTY_TRASH_DAYS', 30 );
+
+
+/**
+ * Language And Language Directory
+ * 
+ * WPLANG defines the name of the language translation (.mo) file. 
+ * WP_LANG_DIR defines what directory the WPLANG .mo file resides. 
+ * If WP_LANG_DIR is not defined WordPress looks first to wp-content/languages 
+ * and then wp-includes/languages for the .mo defined by WPLANG file.
+ */
+// define( 'WPLANG', 'de_DE' );
+// define( 'WP_LANG_DIR', dirname(__FILE__) . 'wordpress/languages' );
+
+
+/**
+ * Autosave Interval
+ *
+ * When editing a post, WordPress uses Ajax to auto-save revisions to the 
+ * post as you edit. You may want to increase this setting for longer delays 
+ * in between auto-saves, or decrease the setting to make sure you never lose 
+ * changes. The default is 60 seconds.
+ */
+// define( 'AUTOSAVE_INTERVAL', 60 ); // Seconds
+
+
+/**
+ * Post Revisions
+ *
+ * If you do not set this value, WordPress defaults WP_POST_REVISIONS to 
+ * true (enable post revisions). If you want to disable the awesome revisions 
+ * feature, use false, or use an integer to specify the maximum number of 
+ * revisions
+ */
+// define( 'WP_POST_REVISIONS', false );
+
+
+/**
+ * Disable File Editing
+ *
+ * Occasionally you may wish to disable the plugin or theme editor to 
+ * prevent overzealous users from being able to edit sensitive files and 
+ * potentially crash the site
+ */
+// define( 'DISALLOW_FILE_EDIT', true );
+
+
+/**
+ * Disable Plugin And Theme Updates And Installation
+ *
+ * This will block users being able to use the plugin and theme 
+ * installation/update functionality from the WordPress admin area. 
+ * Setting this constant also disables the Plugin and Theme editor
+ */
+// define( 'DISALLOW_FILE_MODS', true );
+
+
+/**
+ * Require SSL For Login
+ *
+ * FORCE_SSL_LOGIN is for when you want to secure logins so that passwords 
+ * are not sent in the clear, but you still want to allow non-SSL admin 
+ * sessions (since SSL can be slow).
+ */
+// define( 'FORCE_SSL_LOGIN', true );
+
+
+/**
+ * Require SSL For Admin
+ *
+ * FORCE_SSL_ADMIN is for when you want to secure logins and the admin area 
+ * so that both passwords and cookies are never sent in the clear. This is 
+ * the most secure option.
+ */
+// define( 'FORCE_SSL_LOGIN', true );
+
+
+/**
+ * Block External URL Requests
+ *
+ * Block external URL requests by defining WP_HTTP_BLOCK_EXTERNAL as true 
+ * and this will only allow localhost and your blog to make requests. The 
+ * constant WP_ACCESSIBLE_HOSTS will allow additional hosts to go through 
+ * for requests
+ */
+// define( 'WP_HTTP_BLOCK_EXTERNAL', true );
+// define( 'WP_ACCESSIBLE_HOSTS', 'api.wordpress.org,*.github.com' );
+
+
+/**
+ * Disable Auto Updates
+ *
+ * Disables all WordPress automatic updates
+ */
+// define( 'AUTOMATIC_UPDATER_DISABLED', true );
+
+
+/**
+ * Disable Core Updates
+ *
+ * The easiest way to manipulate core updates is with the WP_AUTO_UPDATE_CORE 
+ * constant. The value can be false to disable all core updates, true to include
+ * all updates and minor to enable for minor releases (default).
+ */
+// define( 'AUTOMATIC_UPDATER_DISABLED', 'minor' );
+
+
+/**
+ * Site URL
+ *
+ * Allows the WordPress address (URL) to be defined. The value defined is 
+ * the address where your WordPress core files reside. It should include 
+ * the http:// part too. Do not put a slash "/" at the end. Setting this 
+ * value in wp-config.php overrides the wp_options table value for siteurl 
+ * and overrides the WordPress address (URL) field in the 
+ * Administration > Settings > General panel when logging in using wp-login.php. 
+ * It will _not_ update your Home url
+ */
+// define( 'WP_SITEURL', 'http://example.com/wordpress' );
+
+
+/**
+ * Home URL
+ *
+ * Similar to WP_SITEURL, WP_HOME overrides the wp_options table value for 
+ * home but does not change it permanently. home is the address you want people 
+ * to type in their browser to reach your WordPress blog. It should include 
+ * the http:// part and should not have a slash "/" at the end
+ */
+// define( 'WP_HOME', 'http://example.com/wordpress' );
+
+
+/**
+ * Move Content Directory
+ *
+ * You can move the wp-content directory, which holds your themes, plugins, 
+ * and uploads, outside of the WordPress application directory. Set 
+ * WP_CONTENT_DIR to the full local path of this directory (no trailing slash)
+ */
+// define( 'WP_CONTENT_DIR', dirname(__FILE__) . '/blog/wp-content' );
+
+
+/**
+ * Move Plugins Directory
+ *
+ * Set WP_PLUGIN_DIR to the full local path of this directory (no trailing slash)
+ */
+// define( 'WP_PLUGIN_DIR', dirname(__FILE__) . '/blog/wp-content/plugins' );
+
+
+/**
+ * Move Uploads Directory
+ *
+ * This path can not be absolute. It is always relative to ABSPATH, therefore 
+ * does not require a leading slash.
+ */
+// define( 'UPLOADS', 'blog/wp-content/uploads' );
+
+
+/**
+ * Set Cookie Domain
+ *
+ * The domain set in the cookies for WordPress can be specified for those with 
+ * unusual domain setups. One reason is if subdomains are used to serve static 
+ * content. To prevent WordPress cookies from being sent with each request to 
+ * static content on your subdomain you can set the cookie domain to your 
+ * non-static domain only
+ */
+// define( 'COOKIE_DOMAIN', 'www.askapache.com' );
+
+
+/**
+ * Automatic Database Optimizing
+ *
+ * There is automatic database optimization support, which you can enable 
+ * by adding the following define to your wp-config.php file only when the 
+ * feature is required
+ */
+// define( 'WP_ALLOW_REPAIR', true );
+
+
+/**
+ * Script Debugging
+ *
+ * If you are planning on modifying some of WordPress' built-in JavaScript or 
+ * Cascading Style Sheets, you should add the following code to your config file
+ */
+// define( 'SCRIPT_DEBUG', true );
+
+
+/**
+ * Disable Javascript Concatenation
+ *
+ * To result in a faster administration area, all Javascript files are 
+ * concatenated into one URL. If Javascript is failing to work in your 
+ * administration area, you can try disabling this feature:
+ */
+// define( 'CONCATENATE_SCRIPTS', false );
+
+
+/**
+ * Increasing Memory
+ *
+ * The WP_MEMORY_LIMIT option allows you to specify the maximum amount of 
+ * memory that can be consumed by PHP. This setting may be necessary in the 
+ * event you receive a message such as "Allowed memory size of xxxxxx bytes 
+ * exhausted".
+ */
+// define( 'WP_MEMORY_LIMIT', '64M' );
+
+
+/**
+ * Increasing Memory In Admin
+ *
+ * When in the administration area, the memory can be increased or decreased 
+ * from the WP_MEMORY_LIMIT by defining WP_MAX_MEMORY_LIMIT
+ */
+// define( 'WP_MAX_MEMORY_LIMIT', '64M' );
+
+
+/**
+ * Save Queries
+ *
+ * The SAVEQUERIES definition saves the database queries to an array and 
+ * that array can be displayed to help analyze those queries. The information 
+ * saves each query, what function called it, and how long that query took 
+ * to execute.
+ */
+// define( 'SAVEQUERIES', true );
+
+
+/**
+ * Cache
+ *
+ * The WP_CACHE setting, if true, includes the wp-content/advanced-cache.php 
+ * script, when executing wp-settings.php.
+ */
+// define( 'WP_CACHE', true );
+
+
+/**
+ * Custom User and Usermeta Tables
+ *
+ * CUSTOM_USER_TABLE and CUSTOM_USER_META_TABLE are used to designate that the 
+ * user and usermeta tables normally utilized by WordPress are not used, 
+ * instead these values/tables are used to store your user information.
+ */
+// define( 'CUSTOM_USER_TABLE', $table_prefix.'my_users' );
+// define( 'CUSTOM_USER_META_TABLE', $table_prefix.'my_usermeta' );
+
+
+/**
+ * Enable Multisite
+ *
+ * WP_ALLOW_MULTISITE is a feature introduced in WordPress Version 3.0 to enable 
+ * multisite functionality previously achieved through WordPress MU. If this setting 
+ * is absent from wp-config.php it defaults to false.
+ */
+// define( 'WP_ALLOW_MULTISITE', true );
+
+
+/**
+ * Redirect Nonexistent Blogs
+ *
+ * NOBLOGREDIRECT can be used to redirect the browser if the visitor tries to 
+ * access a nonexistent blog
+ */
+// define( 'NOBLOGREDIRECT', 'http://example.com' );
+
+
+/**
+ * Override Default File Permissions
+ *
+ * The FS_CHMOD_DIR and FS_CHMOD_FILE define statements allow override of default 
+ * file permissions. These two variables were developed in response to the problem 
+ * of the core update function failing with hosts  running under suexec.
+ */
+// define( 'FS_CHMOD_DIR', ( 0755 & ~ umask() ) );
+// define( 'FS_CHMOD_FILE', ( 0644 & ~ umask() ) );
+
+
 /* That's all, stop editing! Happy blogging. */
 
 /** Absolute path to the WordPress directory. */