Custom Global Variables

Sample message

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$i'.

Sample message

Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$cgv".

Sample message

Detected usage of a non-sanitized input variable: $_POST['vars']

Sample message

$_POST['vars'] not unslashed before sanitization. Use wp_unslash() or similar

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

Detected usage of a possibly undefined superglobal array index: $_REQUEST['cgv_nonce']. Check that the array index exists before using it.

Sample message

strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.

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

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;

Sample message

Tested up to: 6.1 < 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.