Debug options

Enable Debug

Enabling WordPress debugging is crucial for identifying and resolving issues during development. With debugging enabled, WordPress logs errors, warnings, and notices, helping developers detect bugs, compatibility issues, and deprecated functions.

To enable debug you would need to setup FPT or FPT plugin and locate wp-config.php and edit WordPress files. Or you can just do one click in DevKit. Once debug is enabled you will get a clear message what is wrong on your website.

It is disabled by default, as debugging adds extra load to the server and can display warning messages on the website, disrupting the visitor experience.

To enable it navigate to

  1. Settings Tab
  2. Enable debug
1
2
Screenshot 2025 03 13 at 19.17.25

Debug Settings

  1. Create log file
  2. Error log file path
  3. Error log file path – Folder
  4. Error log file path – File name
  5. Display error messages
  6. Enable JS errors
  7. Save queries in global
1
2
3
4
5
6
7
Screenshot 2025 03 13 at 19.03.13

Create error log

For detailed information the best practice is to read a log to understand what and also when something went wrong. Problem with error log is that it can be on several places based on server or WordPress setup.

Error path log

If you do not prefer WordPress default error log path DevKit offers option to change it. You can add custom Folder name and Custom File name to save it.

If you do not want to use FTP to open your debug log you can use our Error Log feature to read it inside Devkit.

View Error Log Feature

Display Error Messages

is another companion to WP_DEBUG that controls whether debug messages are shown inside the HTML of pages or not. The default is ‘true’ which shows errors and warnings as they are generated. Setting this to false will hide all errors. This should be used in conjunction with WP_DEBUG_LOG so that errors can be reviewed later.

Enable JS Errors

SCRIPT_DEBUG is a related constant that will force WordPress to use the “dev” versions of core CSS and JavaScript files rather than the minified versions that are normally loaded. This is useful when you are testing modifications to any built-in .js or .css files. Default is false.

Save queries in global

The SAVEQUERIES definition saves the database queries to an array and that array can be displayed to help analyze those queries. The constant defined as true causes each query to be saved, how long that query took to execute, and what function called it.

in WordPress can be beneficial for several reasons, particularly for developers and administrators who need to debug or optimize their WordPress site:

  1. Debugging: When developing a WordPress site, it’s common to encounter issues related to database queries. By saving queries in the $wpdb->queries array, developers can easily review the query history to debug issues. This can be particularly useful for identifying slow queries or queries that are causing errors.
  2. Performance Analysis: Performance optimization is a critical aspect of maintaining a WordPress site. By examining the queries stored in the $wpdb->queries array, developers can identify inefficient queries that might be slowing down the site. This allows for targeted optimization, such as adding indexes to the database or rewriting the queries for efficiency.
  3. Understanding WordPress Internals: For those looking to deepen their understanding of how WordPress interacts with its database, examining the $wpdb->queries array can provide valuable insights. It can reveal how WordPress constructs its queries and how various plugins and themes interact with the database.
  4. Plugin and Theme Development: Developers creating plugins and themes can use the $wpdb->queries array to ensure that their code is making efficient database queries. This is especially important for plugins and themes that will be distributed widely, as inefficient database interactions can significantly impact the performance of sites using them.
  5. Compliance and Logging: For certain types of sites, particularly those dealing with sensitive data or requiring high levels of auditing, logging all database queries can be a compliance requirement. The $wpdb->queries array can be a part of a broader logging strategy.

However, it’s important to note that storing every query in the $wpdb->queries array can have a performance impact, especially on sites with high traffic or numerous database interactions. Therefore, it’s generally recommended to enable this feature only during development or debugging sessions, not in a production environment.

For more debugging info visit

WordPress Codes

Debug Types

Error logs can be massive. To assist you, you can either view all logs if needed or focus on a specific group.

  1. All
  2. Deprecated
  3. Warning
  4. Notice
  5. Error
1
2
3
4
5
Screenshot 2025 03 13 at 19.03.13

Note: In case you are asking why they are not separated per each single option, previously, each option was separated, but for a better experience, we have now grouped them. This allows you to focus on a group with a single click, without the need to toggle each option individually.