Multi Currency, Currency Switcher, Exchange Rates for WooCommerce – Mudra

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.

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

Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wc_price_args".

Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "raw_woocommerce_price".

Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "formatted_woocommerce_price".

The plugin name includes a restricted term. Your chosen plugin name - "Multi Currency, Currency Switcher, Exchange Rates for WooCommerce - Mudra" - contains the restricted term "woocommerce" which cannot be used within in your plugin name, unless your plugin name ends with "for woocommerce". The term must still not appear anywhere else in your name.

The plugin name includes a restricted term. Your chosen plugin name - "Multi Currency, Currency Switcher, Exchange Rates for WooCommerce - Mudra" - contains the restricted term "woocommerce" which cannot be used within in your plugin name, unless your plugin name ends with "for woocommerce". The term must still not appear anywhere else in your name.

The plugin slug includes a restricted term. Your plugin slug - "woo-exchange-rate" - 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".

wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" 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.

wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" 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.