by Rahul Prajapati
0 (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.
Compatible with WP 7.0.2
v1.1.0
Current Version v1.1.0
Updated 15 hours ago
Last Update on 18 Jul, 2026
Refreshed 15 hours ago
Last Refreshed on
Rank
#62,322
—
No change
Active Installs
0+
—
No change
KW Avg Position
49
—
No change
Downloads
71
+26 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
34,567
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 10 more installs to reach 10+
Rank Changes
Current
#62,322
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
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 1 of 1| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| log viewer | 49 | — | Tag | 3 days ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
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.0.2
- PHP Version
- 7.4 or higher
- Author
- Rahul Prajapati
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- 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
7K+ installs
#2,742
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#989
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
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.
Yes. RP Debug Log Viewer does not modify WordPress constants like WP_DEBUG or WP_DEBUG_LOG. It operates independently using its own log files and does not conflict with Query Monitor, Debug Bar, or any other debugging tool.
All plugin data is cleaned up automatically: the custom database table is dropped, plugin options are removed, and all log files in wp-content/uploads/rp-debug-log-viewer/ are deleted. No orphaned data is left behind.
PHP 7.4 or higher. PHP 8.0, 8.1, 8.2, 8.3, and 8.4 are fully supported.