What It Does
Config Manager provides a GUI for toggling and editing common wp-config.php constants like WP_DEBUG, WP_MEMORY_LIMIT, WP_POST_REVISIONS, and more. It reads the current wp-config.php file, shows each constant's runtime value vs. WordPress default, and lets you add, update, or remove constants without touching a text editor. A backup of wp-config.php is created before the first change.
Features
- Visual editor for 18 wp-config.php constants across 7 categories (debugging, performance, content, security, updates, environment, Redis)
- Shows current value, WordPress default, and recommended value for each constant
- Add new constants, update existing values, or remove (comment out) constants
- Automatic wp-config.php backup before first modification
- Normalizes malformed wp-config.php formatting (fixes multi-define lines, missing newlines)
- Extensible via wpmultitool_config_constants filter — add your own constants to the manager
- Redis auto-detection — tests common hostnames (127.0.0.1, localhost, redis, wp-test-redis) to find a working Redis server
- Real-time updates via DataStar SSE — no page reloads needed
- Constants are categorized: debugging, performance, content, security, updates, environment, redis
- Two tiers: "essential" constants shown by default, "advanced" and "redis" available for power users
- Fires wpmultitool_before_config_update and wpmultitool_after_config_update action hooks for developers
How to Use
-
Navigate to Config Manager
Go to WP Multitool > Config Manager in the WordPress admin menu.
-
Review current constants
Each row shows a constant name, its description, current status (whether it exists in wp-config.php or is using the WordPress default), and the current value.
-
Add a new constant
For constants not yet in wp-config.php, select your desired value from the dropdown or input field and click "Add". The constant will be inserted before the "That's all, stop editing" comment.
-
Update an existing constant
Change the value in the dropdown/input and click "Update". The file is modified in place.
-
Remove a constant
Click "Remove" to comment out the constant in wp-config.php. The line is preserved as a comment, not deleted.
Settings
| Setting | Default | Description |
|---|---|---|
| Managed Constants | 18 built-in constants |
The set of constants that appear in the manager. Extendable via the wpmultitool_config_constants filter. |
FAQ
Can I break my site with Config Manager?
It is unlikely but possible. The module creates a backup before the first change and validates values before saving. However, setting WP_DEBUG_DISPLAY to true on a production site will expose error messages to visitors, and incorrect memory limit values could cause issues.
Why can't I edit a specific constant?
Config Manager manages a predefined set of 18 constants. You can add custom constants using the wpmultitool_config_constants filter in your theme's functions.php or a custom plugin.
What happens when I "Remove" a constant?
The define() line is commented out (prefixed with //), not deleted. WordPress will then use its built-in default value for that constant.
Where is the backup stored?
The backup is saved as wp-config.php.backup in the WordPress root directory. Only one backup is kept — it is created before the very first change and not overwritten on subsequent changes.
Does it support Redis configuration?
Yes. It can manage WP_REDIS_HOST, WP_REDIS_PORT, and WP_REDIS_DATABASE constants, and includes auto-detection that tests common Redis hostnames to find a working connection.
What if wp-config.php is not writable?
If the file is not writable, the interface will display current values in read-only mode. The Add/Update/Remove buttons will not appear.
Ready to optimize your WordPress site?
Join developers using WP Multitool to debug, optimize, and maintain WordPress.
Get WP Multitool