Compliant and accessible cookie banner.
Prioritized issue groups from the latest Plugin Check scan
Security
106
7 issue groups
Maintainability
29
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 '$_SERVER['SERVER_NAME']'.
Sample message
Detected usage of a non-sanitized input variable: $_POST[$i][$multi_number]['id_uniq']
Sample message
$_POST[$i][$multi_number]['id_uniq'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$WidgetAreaName".
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST[$i][$multi_number]['id_uniq']. Check that the array index exists before using it.
Sample message
Processing form data without nonce verification.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "_tarteaucitron_admin_bar_css".
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
Function "get_current_screen()" requires WordPress 3.1.0, but your plugin minimum supported version is WordPress 2.8.0.
Sample message
Processing form data without nonce verification.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
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
Scripts must be registered/enqueued via wp_enqueue_script()
Sample message
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
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.
Not analyzed yet.
First score snapshot
v1.33.0
41
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 41 | 136 | 44 | 92 | v1.33.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.