Debug Bar Constants


Debug Bar Constants adds three new panels to the Debug Bar that display the defined constants available to you as a developer for the current request:

  • WP Constants
  • WP Class Constants
  • PHP Constants


This plugin requires the Debug Bar plugin to be installed and activated.

Also note that this plugin should be used solely for debugging and/or in a development environment and is not intended for use on a production site.

If you like this plugin, please rate and/or review it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the Support Forum or in the GitHub repository.


  • Debug Bar displaying WP Constants
  • Debug Bar displaying WP Class Constants
  • Debug Bar displaying PHP Constants


  1. Install Debug Bar if not already installed (
  2. Extract the .zip file for this plugin and upload its contents to the /wp-content/plugins/ directory. Alternatively, you can install directly from the Plugin directory within your WordPress Install.
  3. Activate the plugin through the “Plugins” menu in WordPress.

Don’t use this plugin on a live site. This plugin is only intended to be used for development purposes.


Can it be used on live site ?

PLEASE DON’T! Amongst the defined constants are your database credentials, so you really do not want to do this.
This plugin is only meant to be used for development purposes.

What are constants ?


A constant is an identifier (name) for a simple value. As the name suggests, that value cannot change during the execution of the script. A constant is case-sensitive by default. By convention, constant identifiers are always uppercase.

Like super globals, the scope of a constant is global. You can access constants anywhere in your script without regard to scope. For more information on scope, read the manual section on variable scope.

I don’t see my constants in the WP Constants list. What gives ?

Congratulations! Sounds like you’re practicing lean programming (or something is going wrong… 😉 ).

The constants you see are the ones available in the current request. If you define constants in a conditionally included file – for instance you only include the file when on a certain page -, these constants will not be available if the conditions have not been met.

The number of constants is different on each page/most pages. How come ?

See the previous question.

What are class constants ?


It is possible to define constant values on a per-class basis remaining the same and unchangeable. Constants differ from normal variables in that you don’t use the $ symbol to declare or use them.

The value must be a constant expression, not (for example) a variable, a property, a result of a mathematical operation, or a function call.

Why do plugins and themes use class constants instead of normal constants ?

It’s good coding practice to avoid littering the global namespace with your own variables and constants. This is a good way to avoid this.

Why is it useful to have insight into the defined class constants ?

If your plugin/theme interacts with other plugins and/or themes, you may want to use their constants.
Example: A plugin might have their version number saved as a class constant (good practice!). On your part, your plugin may have been set up to only work if the related plugin has been upgraded to version x. In that case, you may want to check other plugins version number before your plugin interacts with it.

Don’t forget to always check whether the class constant exists before you use it! It may not be available on all pages and surely not on all WP installs.

if( defined( 'class_name::constant_name' ) ) {
    // Your code here
I don’t see my class in the WP Class Constants list. What gives ?
  • Depending on how lean you’ve programmed your plugin/theme, your class may not be included (and therefore not be declared) for the page you are viewing.
  • The name of your class may be the same as the name of one of the native/extension PHP classes. PHP is normally configured with a limited number of Extensions. A large number of the available extensions declare classes when they are loaded and the WP Class Constants list is filtered for these classes. It’s good practice not to use the names of those PHP native/extension classes for your own classes. Try renaming your class. If that doesn’t work, please let me know and I’ll have a look at it.
Why are *all* native/extension PHP Classes filtered out – and not just the ones for the extensions loaded on my server -, you ask ?

Easy: It’s bad practise to name your class the same as one of the PHP native/extension classes.

In general, when you’re developing a plugin/theme, you are developing for an unknown group of other people with unknown server configurations – including which extensions are(n’t) installed -, so you should always make sure that your class will not interfere with any of the PHP native/extension classes.

I see some PHP classes and their constants in the WP Class Constants list. What gives ?

I’ve tried to exclude all PHP classes from this list, however, I might have missed some. Also some new extensions and/or classes may have been introduced in PHP since the last version of this plugin was released.
Please let me know which one(s) you found and I’ll add it/them to the exclusion list.

Why won’t the plugin activate ?

Have you read what it says in the beautifully red bar at the top of your plugins page ? As it says there, the Debug Bar plugin needs to be active for this plugin to work. If the Debug Bar plugin is not active, this plugin will automatically de-activate itself.

Contributors & Developers

“Debug Bar Constants” is open source software. The following people have contributed to this plugin.


“Debug Bar Constants” has been translated into Dutch. Thank you to the translators for their contributions.

Translate “Debug Bar Constants” into your language.

Interested in development?

Browse the code or subscribe to the development log by RSS.


1.6.1 (2016-04-15)

  • Get the leaner loading of text domains right (at last).

1.6.0 (2016-04-12)

  • Hard-coded the text domains for compatibility with GlotPress.
  • Make loading of text-domain compatible with use of the plugin in the must-use plugins directory.
  • Updated the pretty print class to v1.6.0.
  • Minor housekeeping.
  • Tested & found compatible WP 4.5. (2016-01-13)

  • Fix very minor layout inconsistency in combination with Twenty-Sixteen theme.
  • Updated the pretty print class to v1.5.2. (2016-01-10)

  • Fix weird table layout on front-end in combination with Twenty-Sixteen theme.
  • Leaner loading of text domains. (2015-12-07)

  • Fix typo.

1.5 (2015-12-05)

  • Updated PHP Classes list for PHP7.
  • Fixed (some) links to PHP manual resulting in 404s.
  • Tested & found compatible with WP 4.4.

1.4 (2015-04-18)

  • Updated the pretty print class to v1.5.0 which now allows for limiting of the recursion depth.
  • Tested & found compatible with WP 4.2.
  • Minor tidying up.
  • Updated language files.

1.3.1 (2014-09-05)

  • Fix compatibility with the Plugin Dependencies plugin.
  • Tested & found compatible with WP 4.0.

1.3 (2013-12-02)

  • Moved pretty print class to separate repository as several plugins are using it now. (2013-11-30)

  • Fixed minor HTML validation issue.
  • Fixed auto-disable message display in case the Debug Bar Plugin is not activated.
  • Changed style and script file names to comply with current guidelines (.min).
  • Tested with WP 3.8-beta1. (2013-10-01)

1.2.1 (2013-05-27)

1.2 (2013-05-05)

  • [New!] Added a panel for Class Constants.
  • [Fix] Some left over references to functions not in this plugin.
  • Headers for the PHP Constants now link to their PHP manual page.
  • Moved more output rendering to the pretty-output class and applied a higher level of abstraction.

1.1 (2013-04-30) / not released

  • [New!] Added auto-deactivation if the Debug Bar plugin is not active.
  • [Fix] Removed js debug alert (oops..).
  • [Fix] Adjusted the sorting to be case-insensitive.
  • [Fix] Some small-HTML/CSS tweaks.
  • Added object output helper method.

1.0 (2013-04-28)

  • Initial release.