If you get "Fatal Error: Allowed memory size exhausted," try increasing the limit:
define( 'WP_MEMORY_LIMIT', '256M' );
In simple terms, wp-config.php stores the details that tell WordPress:
Where is it located?
By default, it sits in the root directory of your WordPress installation, right alongside folders like wp-content and wp-admin.
If you want, I can:
Which of those would you like next?
The Ultimate Guide to wp-config.php: Unlocking the Power of Your WordPress Site
As a WordPress user, you're likely familiar with the concept of configuration files. One of the most critical configuration files in WordPress is the wp-config.php file. This file is the backbone of your WordPress site, containing essential settings and information that determine how your site functions. In this article, we'll dive into the world of wp-config.php, exploring its purpose, contents, and how to edit it to unlock the full potential of your WordPress site.
What is wp-config.php?
The wp-config.php file is a PHP file located in the root directory of your WordPress installation. It's a configuration file that contains vital information about your WordPress site, such as database credentials, table prefix, and security settings. When you install WordPress, the wp-config.php file is created automatically, providing a default set of settings that allow your site to function.
Contents of wp-config.php
The wp-config.php file contains several key pieces of information, including:
Default wp-config.php File
Here's an example of a default wp-config.php file:
<?php
/**
* The base configuration file for WordPress
*
* @package WordPress
*/
// ** MySQL settings ** //
/** The name of the database for WordPress */
define( 'DB_NAME', 'wordpress' );
/** MySQL database username */
define( 'DB_USER', 'wordpressuser' );
/** MySQL database password */
define( 'DB_PASSWORD', 'wordpresspassword' );
/** MySQL hostname */
define( 'DB_HOST', 'localhost' );
/** Database Charset to use */
define( 'DB_CHARSET', 'utf8mb4' );
/** The Database Collate type */
define( 'DB_COLLATE', '' );
/**#@+
* Authentication Unique Keys and Salts
*
* Change these to different unique phrases!
* You can generate these using the @link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service
*/
define( 'AUTH_KEY', 'your-auth-key' );
define( 'SECURE_AUTH_KEY', 'your-secure-auth-key' );
define( 'LOGGED_IN_KEY', 'your-logged-in-key' );
define( 'AUTH_SALT', 'your-auth-salt' );
define( 'SECURE_AUTH_SALT', 'your-secure-auth-salt' );
define( 'LOGGED_IN_SALT', 'your-logged-in-salt' );
define( 'HASH_SALT', 'your-hash-salt' );
/**
* WordPress Database Table prefix
*
* You can have multiple installations in one database if you give each
* a unique prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';
/**
* For developers: WordPress debugging mode
*
* Change this to true to enable display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* @link https://codex.wordpress.org/Debugging_in_WordPress
*/
define( 'WP_DEBUG', false );
/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) )
define( 'ABSPATH', dirname( __FILE__ ) . '/' );
/** Sets up WordPress vars and included files. */
require_once( ABSPATH . 'wp-settings.php' );
Editing wp-config.php
Editing the wp-config.php file can seem daunting, but it's a necessary task to customize your WordPress site. Here are some common reasons to edit the file: wp config.php
Best Practices for Editing wp-config.php
When editing the wp-config.php file, follow these best practices:
Common wp-config.php Hacks
Here are some common wp-config.php hacks to improve your WordPress site:
Conclusion
To understand the power of wp-config.php, one must understand the WordPress loading sequence. When a user visits a WordPress site, the server executes index.php, which loads wp-blog-header.php. This immediately attempts to locate wp-config.php.
WordPress searches for the file in the following order: If you get "Fatal Error: Allowed memory size
If the file is not found, WordPress triggers the installation process (famous "5-minute install") to generate it.
Technical Note: Placing wp-config.php one directory above the web root (public_html) is a security best practice. If the web server configuration fails and exposes PHP files as plain text, the database credentials remain outside the publicly accessible web folder.
The configuration file allows for overrides of default PHP and WordPress limits.
The database settings section contains the following elements:
Example:
define( 'DB_NAME', 'mywordpressdb' );
/** The following settings are required by WordPress **/
define( 'DB_USER', 'mywordpressuser' );
define( 'DB_PASSWORD', 'mywordpresspassword' );
define( 'DB_HOST', 'localhost' );
define( 'DB_CHARSET', 'utf8mb4' );
define( 'DB_COLLATE', '' );
Add this crontab-friendly line to auto-repair tables:
define( 'WP_ALLOW_REPAIR', true );
(Remember to disable it after use!)