Postie

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

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

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

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "DebugDump".

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

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

Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "fConnectivityException".

Using cURL functions is highly discouraged. Use wp_remote_get() instead.

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

unlink() is discouraged. Use wp_delete_file() to delete a file.

Detected usage of a non-sanitized input variable: $_ENV['HOST']

trigger_error() found. Debug code should not normally be used in production.

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

Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "DEFAULT_BR_TEXT".

Processing form data without nonce verification.

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().

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.

The $text parameter must be a single text string literal. Found: "Warning! Postie requires that PHP be verion 5.2 or higher. You have version " . phpversion()

print_r() found. Debug code should not normally be used in production.

Using exclusionary parameters, like exclude, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.

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 $checkExistingPostQuery

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