WP Protect Content

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

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

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

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

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

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

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

Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.

The "Short Description" section is too long and was truncated. A maximum of 150 characters is supported.

The plugin name includes a restricted term. Your plugin name - "WP Protect Content" - 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.