Simple Page Sidebars

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

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

Processing form data without nonce verification.

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

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

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

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

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

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

The use of function wp_get_sidebars_widgets() is forbidden

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.

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.

Sanitization missing for register_setting().

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

Processing form data without nonce verification.

Setting `suppress_filters` to `true` is prohibited.

Tested up to: 6.7 < 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.