Shariff Wrapper

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

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

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

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

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

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

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

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

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

Processing form data without nonce verification.

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

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

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.

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

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: fopen().

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

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

rand() is discouraged. Use the far less predictable wp_rand() instead.

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

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.

Tested up to: 6.9 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.

Function "wp_add_privacy_policy_content()" requires WordPress 4.9.6, but your plugin minimum supported version is WordPress 4.9.0.