Advanced Custom Fields: Limiter Field

Sample message

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

Sample message

Mismatched text domain. Expected 'advanced-custom-fields-limiter-field' but got 'acf'.

Sample message

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

Sample message

In footer ($in_footer) is not set explicitly wp_register_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.

Sample message

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

Sample message

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

Sample message

The plugin name includes a restricted term. Your chosen plugin name - "Advanced Custom Fields: Limiter Field" - contains the restricted term "advanced-custom-fields" and cannot be used to begin your plugin name. 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 "advanced-custom-fields" elsewhere in your plugin name, such as "... for advanced-custom-fields".

Sample message

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

Sample message

Plugin name "Advanced Custom Fields: Limiter Field" is different from the name declared in plugin header "Advanced Custom Fields: Limiter".

Sample message

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