Setup individual charges for each payment method in WooCommerce.
Prioritized issue groups from the latest Plugin Check scan
Security
68
7 issue groups
Maintainability
19
7 issue groups
I18n
8
3 issue groups
Repo Compliance
1
1 issue group
Sample message
Processing form data without nonce verification.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$current_section'.
Sample message
Processing form data without nonce verification.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wcml_raw_price_amount".
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
Detected usage of a possibly undefined superglobal array index: $_POST[$prefix . '_pay4pay_charges_fixed']. Check that the array index exists before using it.
Sample message
$_POST[$prefix . '_pay4pay_item_title'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$current_section".
Sample message
Detected usage of a non-sanitized input variable: $_POST[$prefix . '_pay4pay_tax_class']
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_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
Mismatched text domain. Expected 'woocommerce-pay-for-payment' but got 'pay4pay'.
Sample message
Multiple placeholders in translatable strings should be ordered. Expected "%1$s, %2$s, %3$s, %4$s", but got "%s, %s, %s, %s" in 'To fix the issue, contact the plugin author either on %sGithub%s or %sWordPress.org%s and provide following information:'.
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 - "woocommerce-pay-for-payment" - contains the restricted term "woocommerce" which cannot be used within in your plugin slug, unless your plugin slug contains one of the allowed patterns: "for woocommerce", "with woocommerce", "using woocommerce", or "and woocommerce". The term must still not appear anywhere else in your plugin slug.
Not analyzed yet.
First score snapshot
v2.2.2
41
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 41 | 96 | 29 | 67 | v2.2.2 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.