Title: Clashlens – Conflict Detector Author: sungraizfaryad Published: 2026년 9월 4일 Last modified: 2026년 9월 4일 --- 플러그인 검색 ![](https://ps.w.org/clashlens/assets/banner-772x250.png?rev=3681639) ![](https://ps.w.org/clashlens/assets/icon-256x256.png?rev=3681639) # Clashlens – Conflict Detector 작성자: [sungraizfaryad](https://profiles.wordpress.org/sungraizfaryad/) [다운로드](https://downloads.wordpress.org/plugin/clashlens.1.0.0.zip) * [세부사항](https://ko.wordpress.org/plugins/clashlens/#description) * [평가](https://ko.wordpress.org/plugins/clashlens/#reviews) * [설치](https://ko.wordpress.org/plugins/clashlens/#installation) * [개발](https://ko.wordpress.org/plugins/clashlens/#developers) [지원](https://wordpress.org/support/plugin/clashlens/) ## 설명 Something on your site breaks. The slider stops moving, the checkout button does nothing, a page turns white. The usual advice is to deactivate every plugin and switch them back on one at a time, which means taking your live site apart while visitors are on it. Clashlens reads the evidence instead. One click scans your active plugins and gives you a severity-rated report: green when things look fine, red when something needs attention, and a named plugin wherever the data supports one. #### What Clashlens checks **Known incompatible plugin pairs.** Your active plugins are compared against a curated list of combinations known to clash: two SEO plugins competing over meta tags, two caching plugins writing conflicting output, duplicate SSL redirect handlers causing redirect loops, two page builders fighting over the editor. Each hit names both plugins and explains the problem in one sentence, so you know exactly which one to deactivate. Pairs that are merely redundant rather than harmful are marked as such and never inflate your overall status. **Dangerous overrides and jQuery conflicts.** Every PHP file of every active plugin is scanned for calls that commonly break other plugins: `remove_all_actions`, `remove_all_filters`, deregistering jQuery, or dequeuing core styles. A plugin that deregisters jQuery is one of the most common reasons a slider, lightbox, or form suddenly stops working. Scanning is capped per plugin so it stays fast on large sites. **PHP errors grouped by plugin.** Clashlens reads your debug.log and attributes fatal errors, warnings and notices to the plugin that produced them, over the last 7 days. A plugin generating 50 or more errors in a single day is flagged critical. Only the tail of the log is read, so even a multi-gigabyte debug.log will not exhaust memory. **Hook collisions.** Hooks where three or more plugins registered callbacks at the same priority are listed as investigation starting points. Common core lifecycle hooks are excluded because crowding there is completely normal, and this check deliberately never rates your site critical on its own. #### Who it is for Site owners debugging a broken page, developers taking over an unfamiliar site, agencies auditing client installs before an update, and anyone who has ever lost an afternoon to plugin compatibility troubleshooting. #### What it will not do Clashlens never deactivates, modifies, or repairs anything. It reports what it finds and leaves every decision to you. It also cannot see JavaScript errors that happen in the visitor’s browser, and because the scan runs in the admin area, hooks that plugins register only on front-end requests are invisible to the hook collision check. Both are on the roadmap. #### Privacy Clashlens sends nothing anywhere. No external requests, no tracking, no analytics. Scan results are stored in your own database and removed when you uninstall the plugin. ## 스크린샷 [⌊The scan report, showing overall severity and per-check findings with the responsible plugins named.⌉⌊The scan report, showing overall severity and per-check findings with the responsible plugins named.⌉[ The scan report, showing overall severity and per-check findings with the responsible plugins named. [⌊The starting screen. One button runs the scan; nothing is checked until you ask for it.⌉⌊The starting screen. One button runs the scan; nothing is checked until you ask for it.⌉[ The starting screen. One button runs the scan; nothing is checked until you ask for it. ## 설치 1. Upload `clashlens` to `/wp-content/plugins/`, or install it from Plugins Add New. 2. Activate the plugin through the Plugins screen. 3. Go to Settings Clashlens and click **Run Scan**. Results stay stored until you run the next scan, so you can close the page and come back to them. ## FAQ ### Does it deactivate or fix conflicts automatically? No. It reports conflicts so you can investigate and decide. Automatic deactivation on a live site would be far too risky. ### My slider stopped working after installing a plugin. Will this find the cause? Often, yes. The most common cause is a plugin deregistering or dequeuing jQuery, which Clashlens reports by name under Dangerous Overrides. If the conflict also produces PHP errors, those get attributed to the responsible plugin too. What it cannot yet see is a JavaScript error occurring in the visitor’s browser, since that never reaches the server. ### The hook collision section shows results. Is my site broken? Not necessarily. Congested hooks are potential conflict points, not confirmed bugs. Use them as a starting point for investigation. This detector never rates your site critical on its own. ### I get “No debug.log found”. What should I do? Enable `WP_DEBUG_LOG` in your wp-config.php, let the site run for a while, then scan again. Without a log there is nothing for the error detector to read. ### Are front-end hooks covered? The scan runs in an admin context, so hooks that plugins register only on front- end requests are not visible to the hook collision detector. The other three checks are unaffected. Front-end analysis is planned for a future version. ### Can I add my own known conflict pairs? Yes. Use the `clashlens_known_conflicts` filter in a custom plugin or mu-plugin. Each entry is `[ 'slug-a', 'slug-b', 'Explanation', 'warning' ]` and the fourth element is optional, either `'warning'` or `'info'`, defaulting to `'warning'`. ### Does it slow down my site? No. Nothing runs on the front end and nothing runs on a schedule. Code executes only while you are on the Clashlens settings page and you press Run Scan. ### What are the requirements? WordPress 6.0 or newer and PHP 8.0 or newer. ## 후기 이 플러그인에 대한 평가가 없습니다. ## 기여자 & 개발자 “Clashlens – Conflict Detector”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다. 기여자 * [ sungraizfaryad ](https://profiles.wordpress.org/sungraizfaryad/) [자국어로 “Clashlens – Conflict Detector”(을)를 번역하세요.](https://translate.wordpress.org/projects/wp-plugins/clashlens) ### 개발에 관심이 있으십니까? [코드 탐색하기](https://plugins.trac.wordpress.org/browser/clashlens/)는, [SVN 저장소](https://plugins.svn.wordpress.org/clashlens/) 를 확인하시거나, [개발 기록](https://plugins.trac.wordpress.org/log/clashlens/)을 [RSS](https://plugins.trac.wordpress.org/log/clashlens/?limit=100&mode=stop_on_copy&format=rss) 로 구독하세요. ## 변경이력 #### 1.0.0 * Initial release. ## 기초 * 버전 **1.0.0** * 최근 업데이트: **2일 전** * 활성화된 설치 **10보다 적음** * 워드프레스 버전 ** 6.0 또는 그 이상 ** * 다음까지 시험됨: **7.1** * PHP 버전 ** 8.0 또는 그 이상 ** * 언어 * [English (US)](https://wordpress.org/plugins/clashlens/) * 태그: * [compatibility](https://ko.wordpress.org/plugins/tags/compatibility/)[debug](https://ko.wordpress.org/plugins/tags/debug/) [plugin conflict](https://ko.wordpress.org/plugins/tags/plugin-conflict/)[site health](https://ko.wordpress.org/plugins/tags/site-health/) [troubleshooting](https://ko.wordpress.org/plugins/tags/troubleshooting/) * [고급 보기](https://ko.wordpress.org/plugins/clashlens/advanced/) ## 평점 아직 제출된 리뷰가 없습니다. [Your review](https://wordpress.org/support/plugin/clashlens/reviews/#new-post) [모든 리뷰 보기](https://wordpress.org/support/plugin/clashlens/reviews/) ## 기여자 * [ sungraizfaryad ](https://profiles.wordpress.org/sungraizfaryad/) ## 지원 할 말 있으신가요? 도움이 필요하신가요? [지원 포럼 보기](https://wordpress.org/support/plugin/clashlens/)