Provides an electronic funds transfer payment method with Openpay for WooCommerce.
Prioritized issue groups from the latest Plugin Check scan
Security
51
3 issue groups
Maintainability
38
18 issue groups
I18n
35
3 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 '$category'.
Sample message
Mismatched text domain. Expected 'openpay-spei' but got 'openpay_spei'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$order'.
Sample message
File has mixed line endings; this may cause incorrect results
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Offloading images, js, css, and other scripts to your servers or any remote service is disallowed.
Sample message
The $text text string should have translatable content. Found: ''
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
error_log() found. Debug code should not normally be used in production.
Sample message
print_r() found. Debug code should not normally be used in production.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Missing $domain parameter in function call to __().
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Openpay SPEI Plugin" - contains the restricted term "plugin" which cannot be used at all in your plugin name.
Sample message
Using date_default_timezone_set() and similar isn't allowed, instead use WP internal timezone support.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
Sample message
Using cURL functions is highly discouraged. Use wp_remote_get() instead.
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
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
Tested up to: 6.4 < 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
41
External assets
4
Incoming endpoints
0
No public endpoints detected.
First score snapshot
v1.10.2
34
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 34 | 126 | 112 | 14 | v1.10.2 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.