Page Restrict for WooCommerce

Mismatched text domain. Expected 'page-restrict-for-woocommerce' but got 'page_restrict_domain'.

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

Use placeholders and $wpdb->prepare(); found $r

Unescaped parameter $user_id used in $wpdb->get_results("SELECT * FROM `".$wpdb->usermeta."` WHERE meta_key LIKE 'prwc_view_count_%' AND user_id=".$user_id)\n$user_id used without escaping.

Use placeholders and $wpdb->prepare(); found $user_id

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.

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.

Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". 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.

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

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