by Tiago Neto
1 (0 reviews)
Admin Debug Tools
Admin Debug Tools makes it easy to manage your site's logs and debug settings directly from the dashboard, without needing to edit backend files.
Tested up to WP 6.7 (Current: 6.9)
v1.0.0
Current Version v1.0.0
Updated 1 year ago
Last Update on 15 Jan, 2025
Synced 7 hours ago
Last Synced on
Rank
#40,802
+2472 this week
Active Installs
10+
-23.1%
KW Avg Position
N/A
—
No change
Downloads
692
+2 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 20
10+
20+
15,633
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 6 more installs to reach 20+
Rank Changes
Current
#40,802
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%)
Tracked Keywords
Showing 0 of 0| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| No keyword data available yet. | ||||
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.0.0
- Last Updated
- Jan 15, 2025
- Requires WP
- 6.0+
- Tested Up To
- 6.7
- PHP Version
- 8.0 or higher
- Author
- Tiago Neto
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
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,736
Master Addons For Elementor - White Label, Free Widgets, Hover Effects, Conditions, & Animations
40K+ installs
#929
Query Monitor - The developer tools panel for WordPress
200K+ installs
#255
Header and Footer Scripts
200K+ installs
#258
Performance Lab
200K+ installs
#267
Frequently Asked Questions
Common questions about Admin Debug Tools
The main reason is that the default WP_DEBUG_LOG constant saves the log file in the wp-content directory, which is publicly accessible. This can expose sensitive information about your site and server, such as file paths, database credentials, and other details that could be used by malicious actors.
To secure the debug log file, you can:
Change the location of the log file to a non-public directory (you can do this on Admin Debug Tools's Config screen);
Restrict access to the log file using server configuration (e.g., .htaccess, nginx.conf) - You will need assistance from your hosting to do this.;
What if my debug.log file is HUGE?
Debug log files can grow very large over time, especially on high-traffic sites or sites with many errors and warnings. Admin Debug Tools was built from the beggining having that in mind and, by default, will not load the entire log file at once, but only the last 1000 lines.
The code is also optimized to avoid memory issues when loading large log files, but if you're experiencing performance issues, you can:
To secure the debug log file, you can:
Change the location of the log file to a non-public directory (you can do this on Admin Debug Tools's Config screen);
Restrict access to the log file using server configuration (e.g., .htaccess, nginx.conf) - You will need assistance from your hosting to do this.;
What if my debug.log file is HUGE?
Debug log files can grow very large over time, especially on high-traffic sites or sites with many errors and warnings. Admin Debug Tools was built from the beggining having that in mind and, by default, will not load the entire log file at once, but only the last 1000 lines.
The code is also optimized to avoid memory issues when loading large log files, but if you're experiencing performance issues, you can:
How to fix the error "The wp-config.php is not writable"?
Admin Debug Tools needs write access to your wp-config.php file to enable and disable debug mode. If you're seeing the error "The wp-config.php is not writable", you need to give write permissions to the file yourself or ask your hosting provider to do it for you.
You can change the permissions of the wp-config.php file using an FTP client, a file manager in your hosting control panel, or via SSH. The file should have the permissions set to 644 or 640.
Using SSH:
Connect to your server via SSH:
Open your terminal (Mac/Linux) or Command Prompt (Windows).
Use the ssh command to connect to your server. Replace username and hostname with your actual SSH username and server hostname.
ssh username@hostname
Navigate to your WordPress directory:
Use the cd command to change to the directory where your WordPress installation is located.
cd /path/to/your/wordpress/directory
Check the existing permissions of wp-config.php:
Use the ls -l command to list the file permissions.
ls -l wp-config.php
The output will show the current permissions. For example:
-rw-r--r-- 1 username group 1234 Jan 01 12:34 wp-config.php
Update the permissions of wp-config.php:
Use the chmod command to change the file permissions to 644 or 640.
chmod 644 wp-config.php
Or, to set the permissions to 640:
chmod 640 wp-config.php
Verify the updated permissions:
Use the ls -l command again to confirm the changes.
ls -l wp-config.php
The output should now reflect the updated permissions. For example:
-rw-r--r-- 1 username group 1234 Jan 01 12:34 wp-config.php
What users can access Admin Debug Tools?
By default, only users with the manage_options capability can access the Debug Log screen. This includes Administrators and Super Admins on multisite networks.
But you can change this by using the wp_debug_assistant_capability filter. Here's an example of how you can change the capability to edit_posts:
Admin Debug Tools needs write access to your wp-config.php file to enable and disable debug mode. If you're seeing the error "The wp-config.php is not writable", you need to give write permissions to the file yourself or ask your hosting provider to do it for you.
You can change the permissions of the wp-config.php file using an FTP client, a file manager in your hosting control panel, or via SSH. The file should have the permissions set to 644 or 640.
Using SSH:
Connect to your server via SSH:
Open your terminal (Mac/Linux) or Command Prompt (Windows).
Use the ssh command to connect to your server. Replace username and hostname with your actual SSH username and server hostname.
ssh username@hostname
Navigate to your WordPress directory:
Use the cd command to change to the directory where your WordPress installation is located.
cd /path/to/your/wordpress/directory
Check the existing permissions of wp-config.php:
Use the ls -l command to list the file permissions.
ls -l wp-config.php
The output will show the current permissions. For example:
-rw-r--r-- 1 username group 1234 Jan 01 12:34 wp-config.php
Update the permissions of wp-config.php:
Use the chmod command to change the file permissions to 644 or 640.
chmod 644 wp-config.php
Or, to set the permissions to 640:
chmod 640 wp-config.php
Verify the updated permissions:
Use the ls -l command again to confirm the changes.
ls -l wp-config.php
The output should now reflect the updated permissions. For example:
-rw-r--r-- 1 username group 1234 Jan 01 12:34 wp-config.php
What users can access Admin Debug Tools?
By default, only users with the manage_options capability can access the Debug Log screen. This includes Administrators and Super Admins on multisite networks.
But you can change this by using the wp_debug_assistant_capability filter. Here's an example of how you can change the capability to edit_posts: