by sonu8755 1 (0 reviews)

Logtern – Debug Log Viewer

Name: Logtern – Debug Log Viewer
Author: sonu8755

View, search, filter, and manage the WordPress debug.log file directly from your dashboard — no FTP or file manager required.

Logtern ranks #55,901 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 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7 (Current: 7.1.4)

v1.0.0 Current Version v1.0.0

Updated 3 months ago Last Update on 27 Jul, 2026

Refreshed 1 week ago Last Refreshed on

#3,668 of 5,310 in Utilities & Tools

View on WordPress.org

Rank

#55,901

— No change

Active Installs

-85.7%

KW Avg Position

N/A

— No change

Downloads

220

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

42,964

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

Upgrade to Pro

Need 7 more installs to reach 10+

Rank Changes

Current #55,901

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Jul 27, 2026
Requires WP: 6.0+
Tested Up To: 7
PHP Version: 7.4 or higher
Author: sonu8755

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

Debug log debug developer error log log

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar 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

Contact Form 7

10M+ installs

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

View all Utilities-and-tools plugins

Frequently Asked Questions

Common questions about Logtern – Debug Log Viewer

By default in wp-content/debug.log, once WP_DEBUG and WP_DEBUG_LOG are enabled. Because that default path is publicly guessable, Logtern's toggle instead points the log at a randomly named file under uploads/logtern/, protected from direct HTTP access. If you already define WP_DEBUG_LOG as a custom file path, Logtern reads and manages that file instead and the toggle preserves your custom path. The exact file currently in use is always shown in the Log File card on the dashboard, next to a Copy button.

Only users with the manage_options capability (administrators). On multisite, only network administrators. Debug logs can contain sensitive information, so the capability is also filterable via logtern_capability if you need to restrict it further.

Only when you use the debug toggle, and only the WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY constants. Defines are located with PHP's tokenizer, so commented-out lines are never mistaken for real ones; the result is re-verified before saving, and the file is swapped in atomically with its permissions preserved. If anything looks unsafe, the plugin refuses to write and tells you. If wp-config.php is not writable, the toggle is disabled and everything else keeps working.

Yes. Logtern never loads the whole file: it seeks to the end and reads only the last lines you asked for, and downloads are streamed in chunks.

Not when you enable logging through Logtern: the file gets an unguessable random name inside a directory protected by .htaccess and web.config deny rules that the plugin creates. A pre-existing wp-content/debug.log from before you installed Logtern may still be reachable on some servers, though — download what you need, clear it, and let Logtern's toggle set up the protected location. Disabling debug logging when you are done is good practice either way.

Logtern cleans up after itself completely: the debug constants it manages in wp-config.php are reverted (WP_DEBUG is turned off; a WP_DEBUG_LOG value pointing at the plugin's protected directory is reset to the WordPress default, while custom paths are left untouched), the uploads/logtern/ directory — including its log files — is deleted, and the plugin's per-user settings are removed. Download any log you want to keep before uninstalling.

No. There is no tracking, no external requests, and no data leaves your server.