Don’t abbreviate variable names unnecessarily let the code be unambiguous and self-documenting. Use lowercase letters in variable, action/filter, and function names (never camelCase). For that reason, require is generally the better choice as it will throw a Fatal Error if the file cannot be found.
When using include, PHP will throw a warning when the file is not found but will continue execution, which will almost certainly lead to other errors/warnings/notices being thrown if your application depends on the file loaded, potentially leading to security leaks.
It is strongly recommended to use require for unconditional includes. There should only be one space between the path and the include/require keywords. See Data Validation in the Plugin Handbook for further details.īecause include and require are language constructs, they do not need parentheses around the path, so those shouldn’t be used. Text that goes into HTML or XML attributes should be escaped so that single or double quotes do not end the attribute value and invalidate the HTML, causing a security issue. You should almost never have to escape quotes in a string, because you can just alternate your quoting style, like so: echo 'Link name' If you’re not evaluating anything in the string, use single quotes. Use single and double quotes when appropriate. When embedding multi-line PHP snippets within an HTML block, the PHP open and close tags must be on a line by themselves. If you want to automatically check your code against this standard, you can use the official WordPress Coding Standards tooling, which is run using PHP_CodeSniffer. While not all code may fully comply with these standards (yet), all newly committed and/or updated code should fully comply with these coding standards.Īlso see the PHP Inline Documentation Standards for further guidelines. While themes and plugins may choose to follow a different coding style, these coding standards are not just about code style, but also encompass established best practices regarding interoperability, translatability, and security in the WordPress ecosystem, so, even when using a different code style, we recommend you still adhere to the WordPress Coding Standards in regard to these best practices.
They are mandatory for WordPress Core and we encourage you to use them for your themes and plugins as well. These PHP coding standards are intended for the WordPress community as a whole. Self-Explanatory Flag Values for Function Arguments.Error Control Operator Increment/decrement operators.Only One Object Structure (Class/Interface/Trait) per File.Declare Statements, Namespace, and Import Statements.
0 kommentar(er)
