by
Rahul Prajapati
1 (0 reviews)
RP Debug Log Viewer
Create custom debug logs, run validated PHP snippets, capture rich error context, and fix WordPress bugs fast — from your admin dashboard.
RP Debug Log Viewer ranks #65,853 among WordPress.org plugins with 1+ active installations, is #3,668 of 5,310 in the Utilities & Tools category, a 1/5 rating from 0 reviews, and was last updated Jul 18, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1.4)
v1.1.0
Current Version v1.1.0
Updated 3 months ago
Last Update on 18 Jul, 2026
Refreshed 1 week ago
Last Refreshed on
#3,668 of 5,310 in Utilities & Tools
Rank
#65,853
—
No change
Active Installs
1+
—
No change
KW Avg Position
99
3 worse
Downloads
296
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
52,916
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#65,853
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.0
- Last Updated
- Jul 18, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- Rahul Prajapati
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Elementor Website Builder – more than just a page builder
10M+ installs
#1
Contact Form 7
10M+ installs
#3
All-in-One WP Migration and Backup
5M+ installs
#10
UpdraftPlus: WP Backup & Migration Plugin
4M+ installs
#14
WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager
3M+ installs
#19
Hostinger Tools
3M+ installs
#20
WordPress Importer
2M+ installs
#23
WPS Hide Login
2M+ installs
#27
Frequently Asked Questions
Common questions about RP Debug Log Viewer
No. Calling any rp_dlv_*() function with a new log name automatically creates the file, registers it in the database, and adds it as a tab in the viewer. You can also create log files manually from the Log Viewer page using the "Create Custom Log File" form.
In wp-content/uploads/rp-debug-log-viewer/. Each file is named <log-name>.log. The directory is protected from direct browser access with an .htaccess file and an index.php guard.
Yes. The debug log is pre-registered and appears as the first tab in the viewer. It reads from the standard wp-content/debug.log file, and you can view, search, and download it like any other log. It cannot be cleared or deleted through the plugin, since wp-content/debug.log is owned by WordPress core and lives outside the plugin's own storage directory — this plugin never writes to it. To clear it, disable and re-enable WP_DEBUG_LOG in wp-config.php, or clear it manually via your host's file manager or SSH.
Yes. Go to RP Debug Log Viewer -> Configuration -> Tab Management and toggle the log to Inactive. All rp_dlv_*() calls targeting that log will be silently skipped until it is re-activated. The log file itself is preserved — only new writes are paused.
No. RP Debug Log Viewer is designed for zero frontend impact: CSS and JavaScript are loaded only on the plugin's own admin pages — never on the frontend or on unrelated admin screens. Log writes use file_put_contents() with FILE_APPEND, which is a single fast I/O operation. No external API calls, no remote assets, and no background processes.
Yes — with care. Toggle verbose debug logs to Inactive in Configuration so rp_dlv_debug() calls are skipped without touching your code. Keep info and error level logs active for ongoing monitoring. Avoid logging passwords, credit card numbers, or other sensitive personal data.
Yes, as long as RP Debug Log Viewer is loaded before your code runs. Hooking into plugins_loaded at priority 10 or later is the safest approach for plugins. For mu-plugins, the logging functions are available after all regular plugins have loaded.
Snippets are small pieces of PHP code you write and manage from RP Debug Log Viewer -> Snippets — no FTP, no functions.php edits. Use them for hooks, filters, actions, debugging helpers, temporary custom code, or testing a new feature before it goes into your theme or plugin. Only snippets marked Active are executed; everything else just sits safely in the database. Snippets run on every page load during plugins_loaded, so anything you'd normally put in functions.php works the same way.
You can't save broken code. Before a snippet is saved or activated, its code is run through PHP's own parser (without being executed). If there is a syntax error, the save is rejected and you see the exact problem and line number. If an already-active snippet fails at runtime (for example, it calls a function that doesn't exist), the error is caught, the snippet is automatically deactivated so it cannot crash subsequent requests, and an admin notice shows you what went wrong and where. As an emergency brake, adding define( 'RP_DLV_SNIPPETS_SAFE_MODE', true ); to wp-config.php disables all snippet execution instantly while keeping your snippets stored. Snippet management requires the manage_options capability (administrators only), and every action is nonce-protected.
The Snippets feature is intentionally PHP-only and focused on WordPress debugging and development. If you need to output CSS or JavaScript, you can still do it the WordPress way from a PHP snippet — for example, by hooking wp_enqueue_scripts or wp_head.
