WP Post Redirect

Sample message

All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.

Sample message

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

Sample message

$_GET['q'] not unslashed before sanitization. Use wp_unslash() or similar

Sample message

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

Sample message

The plugin name includes a restricted term. Your chosen plugin name - "WP Post Redirect" - contains the restricted term "wp" which cannot be used at all in your plugin name.

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

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

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

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.