by
Som Shrestha
0 (0 reviews)
TroubleLens – Conflict Detector
Find plugin and theme conflicts by switching things off for yourself only. Your visitors keep seeing the site exactly as it is.
TroubleLens ranks #64,535 among WordPress.org plugins with 0+ active installations, is #4,324 of 4,976 in the Utilities & Tools category, and was last updated Sep 22, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.1
v1.0.1
Current Version v1.0.1
Updated 5 hours ago
Last Update on 22 Sep, 2026
Refreshed 10 hours ago
Last Refreshed on
#4,324 of 4,976 in Utilities & Tools
Actively maintained
Rank
#64,535
—
No change
Active Installs
0+
—
No change
KW Avg Position
162
—
No change
Downloads
12
—
Total downloads
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
32,868
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 9 more installs to reach 10+
Rank Changes
Current
#64,535
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%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.1
- Last Updated
- Sep 22, 2026
- Requires WP
- 6.4+
- Tested Up To
- 7.1.1
- PHP Version
- N/A
- Author
- Som Shrestha
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
6K+ installs
#2,758
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,008
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
3M+ installs
#15
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 TroubleLens – Conflict Detector
No. A troubleshooting session applies to requests that carry your session cookie. Every other request — every visitor, bot, cron run and other logged-in user — loads the site normally.
The session only affects you, so a mistake stays with you. If you switch off something your admin screens need, the recovery link on the troubleshooting screen ends the session before any plugin loads, so it works even when the site is returning a fatal error.
In order of how little needs to be working: use the recovery link shown on the troubleshooting screen; clear this site's cookies in your browser; wait for the session to expire; add define( 'TROUBLELENS_DISABLE', true ); to wp-config.php; or delete wp-content/mu-plugins/troublelens-conflict-detector-loader.php. Deactivating the plugin does the last two for you.
No. The session is tied to your user account, and a request that is not you ends it. This is deliberate: it is what stops a leaked cookie applying to anybody else.
Must-use plugins load before any code that could filter them, including this one. The same is true of drop-ins like object-cache.php. The overview screen lists them so you know what is outside the test.
Because they declare that they require it. WordPress deactivates dependents when a dependency goes, and a session does the same, or those plugins would be running against something that is not there — producing an error that looks exactly like the conflict you are hunting. The screen tells you which ones went and why.
You can deactivate a plugin you have not hidden. What is blocked is a plugin deactivating itself, which many do when a dependency is missing. Without that block, hiding WooCommerce for your own session would make its extensions switch themselves off for every visitor.
On multisite, only network administrators can start a session, and only the current site's own active plugins can be switched off. Network-activated plugins are listed and flagged but cannot be toggled.
From the WordPress debug log, when WP_DEBUG_LOG is enabled, and from the extensions WordPress itself paused after catching a fatal error. The plugin will not enable debugging for you, because that means editing wp-config.php. The diagnostics screen lists exactly what this approach cannot see. Built to be extended The screens, the diagnostics, the findings and the report are all open to a plugin that wants to add to them, through documented filters and actions with tests that prove each one fires. Whatever an add-on contributes to a report is redacted along with everything else, and a finding it adds carries the observations behind it like any other. See docs/EXTENDING.md in the plugin folder. Credits The icons and the two illustrations in this plugin were generated with AI rather than taken from an icon set, so nothing here carries a third party licence. They are distributed under the same GPLv2 or later as the rest of the plugin.
