Restrict access to any WooCommerce product, depending on the ownership and/or purchase of other required products.
Prioritized issue groups from the latest Plugin Check scan
Security
61
6 issue groups
I18n
23
3 issue groups
Maintainability
18
11 issue groups
Repo Compliance
2
2 issue groups
Sample message
Processing form data without nonce verification.
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
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$product_category'.
Sample message
Detected usage of a non-sanitized input variable: $_POST['dependency_notice']
Sample message
$_POST['dependency_notice'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "WC_PD_Core_Compatibility".
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "WooCommerce Product Dependencies" - 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.
Sample message
Use placeholders and $wpdb->prepare(); found $customer_data
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wc_pd_dependency_relationship".
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$product_object".
Sample message
The parameter "array( 'get' => 'all' )" at position #2 of get_terms() has been deprecated since WordPress version 4.5.0. Instead do not pass the parameter.
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
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
Detected usage of tax_query, possible slow query.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "WC_Product_Dependencies".
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
The $text text string should have translatable content. Found: '%s'
Sample message
Your plugin has a different license declared in the readme file and plugin header. Please update your readme with a valid GPL license identifier.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Tested up to: 6.6 < 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.
Not analyzed yet.
First score snapshot
v2.0.1
39
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 39 | 104 | 44 | 60 | v2.0.1 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.