CallPage – Callback Widget

Sample message

The $domain parameter must be a single text string literal. Found: $this->plugin_name

Sample message

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

Sample message

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

Sample message

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

Sample message

Processing form data without nonce verification.

Sample message

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

Sample message

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

Sample message

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.

Sample message

Plugin name "CallPage - Callback Widget" is different from the name declared in plugin header "Callpage - Callback for Wordpress".

Sample message

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.