WPIntell

Source evidence

Warning message recommendation will cause PHP error

Plugin Check (PCP) · support · 2026-06-03T09:13:00+00:00

complaintsentiment
highseverity
0.85relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 31 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Anthony Hortin unresolved
Hi, I was running a plugin through this plugin checker and it produced a WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound warning message for a variable. It seems the only way to satisfy/resolve this error warning is by prefixing the global variable name with the Text Domain specified in the plugin. The issue with this is that Text Domains are typically either a single word, or multiple words separated by hyphens. In my case, the Text Domain was set to display-page-template-name . If I update the variable name to be prefixed with the Text Domain, such as $display-page-template-name_return_string , you end up with a PHP fatal error due to the hyphens. So at the moment, it doesn’t seem that you’re able to satisfy this requirement if your Text Domain is multiple words (separated by hyphens).

Comments

0 shown

No comments were stored for this source.