Improve WooCommerce UX with AJAX cart updates, quantity buttons, streamlined checkout, and more — for a faster, smoother buying experience.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
85
11 issue groups
Security
32
4 issue groups
I18n
6
3 issue groups
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "mh_wbu_all_options".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$cart_item'.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "MHCommon".
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$class".
Sample message
Processing form data without nonce verification.
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "WBU_BASE_FILE".
Sample message
Processing form data without nonce verification.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
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 non-sanitized input variable: $_POST['post_data']
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
Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_enqueue_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development.
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: "$this->common->getPluginAbbrev() . '_' . $alias".
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "wbu".
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
Multiple placeholders in translatable strings should be ordered. Expected "%1\$s, %2\$s", but got "%s, %s" in "You're using a limited version of %s. For more features and better support, please <a href='%s'>consider the premium version</a>.".
Sample message
The plugin slug includes a restricted term. Your plugin slug - "woo-better-usability" - 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".
Potential connections found in static code analysis.
Outbound calls
9
External assets
1
Incoming endpoints
6
wp_ajax
admin_post
admin_post
admin_post
wp_ajax
wp_ajax
4 score snapshots
v1.0.63
47
Latest
v1.0.62
47
Score
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 47 | 123 | 30 | 93 | v1.0.63 | 2.0.0 |
| 47 | 120 | 29 | 91 | v1.0.62 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.