Configuration and debug log
Two pages in an application’s WordPress group work on wp-config.php: Configuration for its settings, and Debug log for WordPress’s debug switches and the log they write.
Configuration
Section titled “Configuration”WordPress › Configuration lists every constant (define()) and variable set in wp-config.php with a plain value, in a table with its Name, Value and Type. Changes apply immediately.
Values are shown as they are stored, including the database name, user and password and the security keys. Everyone who can manage the application can open this page, so give access only to people you trust with the site.
Add a setting
Section titled “Add a setting”- Click Add option.
- Enter the Name, for example
WP_MEMORY_LIMIT. Use letters, numbers and underscores. - Choose the Type: Constant or Variable.
- Choose the Value type: Text, Boolean, Number or Null.
- Enter the Value and click Add.
If a setting with that name already exists, the panel says so. Edit the existing one instead.
Edit or delete a setting
Section titled “Edit or delete a setting”- Click the pencil icon, change the Value or Value type, and click Update. The name and type can’t be changed; delete the setting and add it again instead.
- Click the cross, tick “Yes, I understand and want to remove this option.” and click Delete option.
Changing a database setting such as DB_PASSWORD, or table_prefix, shows a warning: a wrong value takes the website offline until it is corrected.
Some entries can’t be edited or deleted here, and their buttons are greyed out: settings whose value is not a plain value (for example one built from another constant or a function call), and settings defined more than once. Change those in wp-config.php with the file manager.
If someone else changed wp-config.php since you opened the page, saving fails with “wp-config.php changed. Reload it before saving.” Reload the page and make your change again.
Debug log
Section titled “Debug log”WordPress › Debug log has three switches. Each one applies as soon as you turn it.
| Switch | What it does |
|---|---|
| WordPress debug mode | Turns on WordPress’s diagnostic reporting (WP_DEBUG). The other two switches only have an effect while this one is on. |
| Debug log | Writes errors from WordPress, plugins and themes to wp-content/debug.log (WP_DEBUG_LOG). |
| Display debug errors | Shows errors in the pages visitors see (WP_DEBUG_DISPLAY). |
Read the log
Section titled “Read the log”Below the switches, the WordPress debug log shows the latest 512 KB of wp-content/debug.log. It refreshes on its own about every 30 seconds while the window is in front.
- Filter by All, Errors or Warnings, or type in Filter lines to search.
- Use the buttons to refresh, copy, download the log as a
.txtfile, or wrap long lines. - Click the bin icon and confirm Clear log to empty it. New errors keep being recorded.
While logging is off, the viewer says WordPress debug logging is off. Turn on Debug log to start capturing errors.
If WP_DEBUG_LOG in wp-config.php points to a file outside the application’s folder, the panel can’t show it and says “The configured debug log is outside this application’s managed directory.” Set Debug log off and on again, or change WP_DEBUG_LOG to true, to write to wp-content/debug.log.