The Premmerce Product Filter for WooCommerce plugin is a professional tool for managing filters with perfect Ajax and unique SEO features.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
1,406
14 issue groups
Security
609
7 issue groups
I18n
268
4 issue groups
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$account_addon_ids".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '" <a href='{$skip_url}' class='button button-small button-secondary'>{$use_plugin_anonymously_text}</a>"'.
Sample message
Mismatched text domain. Expected 'premmerce-woocommerce-product-filter' but got 'premmerce-filter'.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "_fs_text".
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "FS_Admin_Menu_Manager".
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: "FS_API__ADDRESS".
Sample message
$_GET[$filterParam] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Detected usage of a non-sanitized input variable: $_GET[$filterParam]
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
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "filter_item_{$type}".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$message'.
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
Function "register_block_type()" requires WordPress 5.0.0, but your plugin minimum supported version is WordPress 4.8.0.
Sample message
Unescaped parameter $query used in $wpdb->get_col()\n$query assigned unsafely at line 57.
Sample message
Complex placeholders used for values in the query string in $wpdb->prepare() will NOT be quoted automagically. Found: %1$s.
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
Missing $domain parameter in function call to __().
Sample message
The $text parameter must be a single text string literal. Found: $text
Sample message
Attempting a database schema change is discouraged.
Sample message
Plugin Updater detected. These are not permitted in WordPress.org hosted plugins. Detected: class FS_Plugin_Updater
Sample message
Plugin Updater detected. Detected code which may be altering WordPress update routines. Detected: _site_transient_update_plugins
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
Found call to wp_enqueue_script() with external resource. Offloading scripts to your servers or any remote service is disallowed.
Not analyzed yet.
First score snapshot
v3.7.4
24
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 24 | 2,303 | 817 | 1,486 | v3.7.4 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.