Source evidence

Error reporting always disabled by this plugin

Admin Custom Login · support · 2026-05-27T14:42:00+00:00

Admin Custom Login plugin evidence original source source API

complaintsentiment

highseverity

0.97relevance

1replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 28 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

24 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

emiel9d unresolved

Your plugin has 4 mentions of: error_reporting(0); Two of them cause all WordPress errors being supressed, even if WP_DEBUG is true. This makes it hard for developers like me to find issues, please fix this. The two mentions causing the issue are in: /admin-custom-login/init.php /admin-custom-login/login-form-screen.php There are two more, but they don’t seem to give any problem right now: /admin-custom-login/installation.php /admin-custom-login/includes/login-inline-css.php Thanks! Hi @emiel9d , Thank you very much for bringing this to our attention! You are completely correct. Hardcoding error_reporting(0); inside a plugin is bad practice as it overrides custom developer configurations and suppresses critical WordPress errors (like when WP_DEBUG is active), making debugging incredibly difficult. We have addressed this issue immediately. We went ahead and completely removed all 4 instances of error_reporting(0); across all the files you mentioned: init.php login-form-screen.php installation.php includes/login-inline-css.php These changes have been released in the latest version 3.6.6. Please update the plugin, and you should no longer experience forced error suppression. Thank you again for helping us make the plugin better and more developer-friendly!

Commercial Context

Opportunity

trust and abuse-prevention operations

Custom Login abuse-prevention assurance for keeping sites trusted, protected, and recoverable

Buyer: site owners, agencies, and maintenance teams

Wedge: test custom login lockouts, bot/spam defenses, risky access changes, and incident alerts

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Error reporting always disabled by this plugin: users show bugs, compatibility, support pain that may indicate a product gap.

Evidence quote: Error reporting always disabled by this plugin Your plugin has 4 mentions of: error_reporting(0); Two of them cause all WordPress errors being supressed, even if WP_DEBUG is true.

Affected feature: form

bugs compatibility support setup

Plugin

API

Admin Custom Login

20.0K active installs · 2.3M downloads · rating 92.0

admin login page custom admin login custom login custom login page customize wordpress login page

Comments

1 shown

Hari Maliya 2026-05-29T06:23:00+00:00

Hi @emiel9d , Thank you very much for bringing this to our attention! You are completely correct. Hardcoding error_reporting(0); inside a plugin is bad practice as it overrides custom developer configurations and suppresses critical WordPress errors (like when WP_DEBUG is active), making debugging incredibly difficult. We have addressed this issue immediately. We went ahead and completely removed all 4 instances of error_reporting(0); across all the files you mentioned: init.php login-form-screen.php installation.php includes/login-inline-css.php These changes have been released in the latest version 3.6.6. Please update the plugin, and you should no longer experience forced error suppression. Thank you again for helping us make the plugin better and more developer-friendly!