Premmerce User Roles

Sample message

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

Sample message

Detected usage of a non-sanitized input variable: $_GET['delete_role']

Sample message

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

Sample message

Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().

Sample message

Processing form data without nonce verification.

Sample message

wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.

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 "wp_get_update_php_url()" requires WordPress 5.1.0, but your plugin minimum supported version is WordPress 4.8.0.

Sample message

Attempting a database schema change is discouraged.

Sample message

Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "fs_plugins_api".

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

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

Short PHP opening tag used with echo; expected "<?php echo __ ..." but found "<?= __ ..."

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.