theme/plugin prefix error
-
Hi there,
I have a question about the 1.7.0 update which is listing a number of new errors (below) referring to “theme/plugin prefix”.
Can’t seem to find anywhere that has a specific answer and haven’t been able to work it out !
What would be the “plugin prefix” for a plugin named “My Plugin” ?
Do I need a line of code to set the “plugin prefix” ?
It would be useful if PCP stated what the “theme/plugin prefix” was so you can work out what is wrong.ERRORS:
WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedClassFound
Classes declared by a theme/plugin should start with the theme/plugin prefix.WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound
Global variables defined by a theme/plugin should start with the theme/plugin prefix.
-
Answering my own question…
Turned out the problem was PCP wasn’t able to traverse this one plugin. I realised this when I moved to a different plugin.
The “plugin prefix” for a plugin named “My Plugin” is “my_plugin”.
The WordPress documentation (below) does not include the “theme/plugin prefix” requirement.
https://developer.wordpress.org/plugins/plugin-basics/best-practices/
This document says…
“All globally accessible code should be prefixed with a unique identifier…
In order to prevent conflicts with other plugins, your prefix should be at least 4 letters long, though we recommend 5″
So according to WP it doesn’t need to be the “theme/plugin prefix”.
https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/
In this document there is no mention of using a prefix for globals.
This shows that PCP is not presently aligned with WP best practice.
Clearly a prefix is required and at least 4-5 letters would be my choice rather than the “theme/plugin prefix” which is now causing me problems.
You must be logged in to reply to this topic.
