A simple and easy way to Customize woocommerce, disable unwanted checkout feelds, free checkout, chenge WooCommerce button names and change colour sch …
Prioritized issue groups from the latest Plugin Check scan
Security
9
4 issue groups
Maintainability
9
6 issue groups
Repo Compliance
5
5 issue groups
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
Detected usage of a non-sanitized input variable: $_GET['tab']
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Woo Customize" - contains the restricted term "woo" and cannot be used to begin your plugin name. 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 name, such as "... for woo".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'home_url'.
Sample message
Using __FILE__ for menu slugs risks exposing filesystem structure.
Sample message
Resource version not set in call to wp_enqueue_style(). This means new versions of the style 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
Plugin name "Customizer for WooCommerce" is different from the name declared in plugin header "Woo Customize".
Sample message
Mismatched "Tested up to": 5.8 != 5.8.1. The "Tested up to" value in the readme file must match the "Tested up to" value in the plugin header. If the plugin header has a "Tested up to" value, it will override the readme value, which can cause confusion.
Sample message
Tested up to: 5.8 < 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
Mismatched Requires at least: 4.6 != 4.0. "Requires at least" needs to be exactly the same with that in your main plugin file's header.
Sample message
Mismatched Requires PHP: 5.5 != 5.4. "Requires PHP" needs to be exactly the same with that in your main plugin file's header.
Sample message
The "Short Description" section is too long and was truncated. A maximum of 150 characters is supported.
Sample message
Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.
Potential connections found in static code analysis.
Outbound calls
5
External assets
0
Incoming endpoints
0
No external asset domains detected.
No public endpoints detected.
First score snapshot
v1.0.7
72
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 72 | 23 | 10 | 13 | v1.0.7 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.