Comments – wpDiscuz

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

$_COOKIE["comment_author_email_" . COOKIEHASH] not unslashed before sanitization. Use wp_unslash() or similar

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

Detected usage of a possibly undefined superglobal array index: $_FILES[self::INPUT_NAME]. Check that the array index exists before using it.

The $text parameter must be a single text string literal. Found: !empty($currentUser->ID) ? "wpdiscuz-comment-message-auth" : "wpdiscuz-comment-message-unauth"

Missing $domain parameter in function call to __().

Processing form data without nonce verification.

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.

Detected usage of a non-sanitized input variable: $_COOKIE["comment_author_email_" . COOKIEHASH]

Processing form data without nonce verification.

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

Mismatched text domain. Expected 'wpdiscuz' but got "default".

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

File contains UTF-8 byte order mark, which may corrupt your application

date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.

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.

parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.

Detected usage of meta_query, possible slow query.

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.

File has mixed line endings; this may cause incorrect results

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

Use of a direct database call is discouraged.

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

Use placeholders and $wpdb->prepare(); found $sql

Multiple placeholders in translatable strings should be ordered. Expected "%1\$s, %2\$s", but got "%s, %s" in "<strong>%s</strong> in these <strong>%s</strong> accept reviews.".