Leadster

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.

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

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

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

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

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

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

$_POST[&quot;leadster_nonce&quot;] not unslashed before sanitization. Use wp_unslash() or similar

Processing form data without nonce verification.

Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.