Debug Bar Query Count vs WP Debugging — WordPress

Debug Bar Query Count Alert vs WP Debugging

Side-by-side comparison · 24 data points

Debug Bar Query Count Alert

5.0·2reviews·10+installs

wordpress

Change

1. Listing metadata

Field-level data

	Debug Bar Query Count Alert	WP Debugging
Tagline	—	—
Description	494 / 5000 chars10% used	2811 / 5000 chars56% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Matthew Boynes	Andy Fragen
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

Debug Bar Query Count Alert

WP Debugging

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Debug Bar Query Count Alert and WP Debugging
Metric	Debug Bar Query Count Alert	WP Debugging
Rating	5.0 ★	5.0 ★
Total reviews	2	★ 21
Active installs	10+	10,000+
Free plan	—	—

Keyword	Debug Bar Query Count Alert	WP Debugging
live support	Not ranked	#236

5. App details

Long-form description · keyword frequency

Debug Bar Query Count Alert

Replaces the default text in the Debug Bar button (which is “Debug Bar” by default in English) with the page’s query count and total sql time. The button will be red if there were more than 200 queries or they took more than 1 second to run, and orange if the page required more than 100 queries or took more than 0.5 seconds to run. Requires the Debug Bar plugin and for the constant SAVEQUERIES to be true. Inspired by the Admin Bar on WordPress.com VIP, which offers similar functionality.

Top keywords

bar4×4.30%
debug3×3.23%
debug bar3×3.23%
button2×2.15%
default2×2.15%
page2×2.15%
queries2×2.15%
run2×2.15%
took2×2.15%

WP Debugging

This plugin sets the following debug constants in wp-config.php on plugin activation and removes them on plugin deactivation. Any errors will result in a PHP Exception being thrown. Debug constants per Debugging in WordPress. Default settings: define( 'WP_DEBUG_LOG', true ); define( 'SCRIPT_DEBUG', true ); define( 'SAVEQUERIES', true ); @ini_set( ‘display_errors’, 1 ); is set when the plugin is active. WP_DEBUG is set to true when the plugin is first run, thereafter it can be turned off in the Settings. The Settings page allows the user to set the following. define( 'WP_DEBUG', true ); // Default on initial plugin installation. define( 'WP_DEBUG_DISPLAY', false ); // Default when not declared is true. define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true ); // WordPress 5.2 WSOD Override. When the plugin is deactivated best efforts are made to re-add pre-existing constants to their former state. When the plugin is activated the default settings and any saved settings are restored. This plugin uses the wp-cli/wp-config-transformer command for writing constants to wp-config.php. Debug Quick Look from Andrew Norcross is included with this plugin to assist in reading the debug.log file. If you already have this plugin installed you should delete it when WP Debugging is not active. Query Monitor and Debug Bar plugins are optional dependencies to aid in debugging and troubleshooting. The notice for installation will recur 45 days after being dismissed. If you have a non-standard location for your wp-config.php file you can use the filter wp_debugging_config_path to return the file path for your installation. The filter wp_debugging_add_constants allows the user to add constants to wp-config.php. The filter returns an array where the key is the name of the constant and the value is an array of data containing the value as a string and a boolean to indicate whether or not the value should be passed without quotes. $my_constants = [ 'my_test_constant' => [ 'value' => 'abc123', 'raw' => false, ], 'another_test_constant' => [ 'value' => 'true' ], ]; The value option contains the constant’s value as a string. The raw option means that instead of placing the value inside the config as a string it will become unquoted. The default is true. Set as false for non-boolean values. Example: add_filter( 'wp_debugging_add_constants', function( $added_constants ) { $my_constants = [ 'my_test_constant' => [ 'value' => '124xyz', 'raw' => false, ], 'another_test_constant' => [ 'value' => 'true' ], ]; return array_merge( $added_constants, $my_constants ); }, 10, 1 ); This will create the following constants. define( 'MY_TEST_CONSTANT', '124xyz' ); define( 'ANOTHER_TEST_CONSTANT', true ); Development PRs are welcome against the develop branch on GitHub.

Top keywords

constants12×2.79%
true9×2.09%
debug8×1.86%
define8×1.86%
constant'6×1.40%
debugging6×1.40%
test6×1.40%
test constant'6×1.40%
value6×1.40%
'wp5×1.16%
default5×1.16%
php5×1.16%

Frequently asked

Common questions about this comparison

Which has better reviews, Debug Bar Query Count Alert or WP Debugging?

Debug Bar Query Count Alert (5.0★, 2 reviews) and WP Debugging (5.0★, 21 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.

Should I choose Debug Bar Query Count Alert or WP Debugging?

AppRanks cannot separate these two on rating — both sit at 5.0★. WP Debugging does carry the larger published review base (21 vs 2). Read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Debug Bar Query Count Alert or WP Debugging?

Both apps are one-click installs from the WordPress Plugin Directory. WP Debugging has the deeper published review base (21 vs 2), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

Debug Bar Query Count Alert typically suits early-stage and growth-mode teams based on its published review base (2 reviews). WP Debugging typically suits early-stage and growth-mode teams based on its published review base (21 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between Debug Bar Query Count Alert and WP Debugging?

Migration support varies by app and category. Debug Bar Query Count Alert and WP Debugging both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from Debug Bar Query Count Alert" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

Debug Bar Query Count Alert vs WP Debugging

Debug Bar Query Count Alert

1. Listing metadata

2. Categories & rankings

WP Debugging

At a glance

AppRanks verdict

3. Search rankings

4. Activity in the last 90 days

Debug Bar Query Count Alert · 0 changes

WP Debugging · 1 changes

5. App details

Frequently asked

Which has better reviews, Debug Bar Query Count Alert or WP Debugging?

Should I choose Debug Bar Query Count Alert or WP Debugging?

Which is faster to set up, Debug Bar Query Count Alert or WP Debugging?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between Debug Bar Query Count Alert and WP Debugging?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons