Button visually impaired

Sample message

Mismatched text domain. Expected 'button-visually-impaired' but got 'bvi'.

Sample message

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$args['after_title']'.

Sample message

All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.

Sample message

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;

Sample message

strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.

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

Resource version not set in call to wp_register_style(). This means new versions of the style may not always be loaded due to browser caching.

Sample message

A function call to __() 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

Translatable string should not be wrapped in HTML. Found: '<div class="notice notice-error is-dismissible"><p>Для работы плагина Button visually impaired требуется минимум версия <strong>%1$s</strong> PHP. У Вас <strong>%2$s</strong>PHP версия.</p></div>'

Sample message

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