Force Authentification Before Checkout for WooCommerce

Sample message

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"<strong>$plugin_name</strong>"'.

Sample message

Mismatched text domain. Expected 'woo-force-authentification-before-checkout' but got 'wc-force-auth'.

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

Processing form data without nonce verification.

Sample message

A function call to esc_html__() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.

Sample message

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

Sample message

The "Text Domain" header in the plugin file does not match the slug. Found "wc-force-auth", expected "woo-force-authentification-before-checkout".

Sample message

The plugin slug includes a restricted term. Your plugin slug - "woo-force-authentification-before-checkout" - contains the restricted term "woo" and cannot be used to begin your plugin slug. We disallow the use of certain terms in ways that are abused, or potentially infringe on and/or are misleading with regards to trademarks. You may use the term "woo" elsewhere in your plugin slug, such as "... for woo".