Highly Flexible WooCommerce to BuddyPress integration which puts site admins in the complete control.
Prioritized issue groups from the latest Plugin Check scan
Security
18
5 issue groups
I18n
17
4 issue groups
Maintainability
12
7 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 '"<div class='wrap pt-settings-page-wrap {$slug}'>"'.
Sample message
Mismatched text domain. Expected 'buddycommerce' but got 'buddypress-member-types-pro'.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "is_add_payment_method_page".
Sample message
Detected usage of a non-sanitized input variable: $_GET[$name]
Sample message
Missing $domain parameter in function call to __().
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
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$endpoint".
Sample message
Processing form data without nonce verification.
Sample message
Resource version not set in call to wp_register_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_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
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
error_log() found. Debug code should not normally be used in production.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
$_POST['key'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Plugin name "BuddyCommerce: WooCommerce and BuddyPress Integration" is different from the name declared in plugin header "BuddyCommerce".
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 name includes a restricted term. Your chosen plugin name - "BuddyCommerce: WooCommerce and BuddyPress Integration" - contains the restricted term "woocommerce" which cannot be used within in your plugin name, unless your plugin name 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 name.
Potential connections found in static code analysis.
Outbound calls
43
External assets
0
Incoming endpoints
1
No external asset domains detected.
No public endpoints detected.
wp_ajax
First score snapshot
v1.0.8
56
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 56 | 48 | 29 | 19 | v1.0.8 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.