WP Disable Site Health

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

Your plugin has a different license declared in the readme file and plugin header. Please update your readme with a valid GPL license identifier.

Mismatched Stable Tag: 4.5 != 1.0. Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.

The plugin name includes a restricted term. Your plugin name - "WP Disable Site Health" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress.

The plugin name includes a restricted term. Your plugin name - "WP Disable Site Health" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress.

The plugin slug includes a restricted term. Your plugin slug - "wp-disable-site-health" - contains the restricted term "wp" which can be used within the plugin slug, as long as you don't use the full name in the plugin name. For example: You can use WP but not WordPress.

wp_redirect() found. Using wp_safe_redirect(), along with the &quot;allowed_redirect_hosts&quot; filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.