Pageviews

Sample message

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

Sample message

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

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

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

Sample message

Unescaped parameter $post_type_in used in $wpdb->get_col()\n$post_type_in assigned unsafely at line 63.

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

Use placeholders and $wpdb->prepare(); found interpolated variable {$post_type_in} at "SELECT ID FROM $wpdb->posts WHERE ID > %d AND post_type IN ({$post_type_in}) ORDER BY ID ASC LIMIT %d;"

Sample message

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

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.