Payoneer Checkout for WooCommerce - Build beautiful checkout flows + manage payments in one place
Prioritized issue groups from the latest Plugin Check scan
Security
112
5 issue groups
Maintainability
94
15 issue groups
I18n
6
4 issue groups
Repo Compliance
1
1 issue group
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"Data contains no expected `{$key}` element."'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "$action".
Sample message
Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
Processing form data without nonce verification.
Sample message
Mismatched text domain. Expected 'payoneer-checkout' but got 'syde-payment-gateway'.
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
print_r() found. Debug code should not normally be used in production.
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a non-sanitized input variable: $_REQUEST['_ajax_nonce']
Sample message
$_REQUEST['_ajax_nonce'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fread().
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
Detected usage of meta_query, possible slow query.
Sample message
var_export() found. Debug code should not normally be used in production.
Sample message
rand() is discouraged. Use the far less predictable wp_rand() instead.
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
A "translators:" comment must be a "/* */" style comment. Docblock comments will not be picked up by the tools to generate a ".pot" file.
Sample message
The "/vendor" directory using composer exists, but "composer.json" file is missing.
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.
Potential connections found in static code analysis.
Outbound calls
91
External assets
2
Incoming endpoints
3
wp_ajax
wp_ajax
wp_ajax
3 score snapshots
v3.5.10
33
Latest
v3.5.9
34
Score
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 33 | 213 | 168 | 45 | v3.5.10 | 2.0.0 |
| 34 | 209 | 168 | 41 | v3.5.9 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.