Add multiple custom payment gateways to WooCommerce e-commerce plugin.
Prioritized issue groups from the latest Plugin Check scan
I18n
136
6 issue groups
Security
57
5 issue groups
Maintainability
38
10 issue groups
Supply Chain
1
1 issue group
Sample message
The $domain parameter must be a single text string literal. Found: $endpoint
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"3. Commit changes: git add . && git commit -m \"Bump version to $newVersion\"\n"'.
Sample message
Missing $domain parameter in function call to _e().
Sample message
The $text parameter must be a single text string literal. Found: $args['description']
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$content".
Sample message
Function "get_user_locale()" requires WordPress 4.7.0, but your plugin minimum supported version is WordPress 4.0.0.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "findFile".
Sample message
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Detected usage of a non-sanitized input variable: $_COOKIE[$cookie_name]
Sample message
$_COOKIE[$cookie_name] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "Functions::get_plugin_slug('-template')".
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
The use of function eval() is forbidden
Sample message
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "http_headers_useragent".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$name'.
Sample message
In footer ($in_footer) is not set explicitly wp_register_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Sample message
The $text text string should have translatable content. Found: ''
Sample message
Hidden files are not permitted.
Sample message
Tested up to: 6.9 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.
Sample message
The plugin slug includes a restricted term. Your plugin slug - "woo-custom-gateway" - contains the restricted term "woo" and cannot be used to begin your plugin slug. We disallow the use of certain terms in ways that are abused, or potentially infringe on and/or are misleading with regards to trademarks. You may use the term "woo" elsewhere in your plugin slug, such as "... for woo".
Not analyzed yet.
First score snapshot
v1.6.6
35
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 35 | 233 | 202 | 31 | v1.6.6 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.