A field for Advanced Custom Fields which allows you to create a field where users can select terms or taxonommies flexibly.
Prioritized issue groups from the latest Plugin Check scan
Security
42
2 issue groups
Maintainability
20
8 issue groups
I18n
8
1 issue group
Repo Compliance
1
1 issue group
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$field['name']'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Mismatched text domain. Expected 'acf-advanced-taxonomy-selector' but got 'acf'.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "acf/create_field".
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "acfatf_load_textdomain".
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "acf_field_advanced_taxonomy_selector".
Sample message
The parameter "array( 'hide_empty' => false )" at position #2 of get_terms() has been deprecated since WordPress version 4.5.0. Instead do not pass the parameter.
Sample message
Plugin name "ACF: Advanced Taxonomy Selector" is different from the name declared in plugin header "Advanced Custom Fields: Advanced Taxonomy Selector".
Sample message
Tested up to: 5.1 < 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 plugin name includes a restricted term. Your chosen plugin name - "Advanced Custom Fields: Advanced Taxonomy Selector" - 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
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.
Potential connections found in static code analysis.
Outbound calls
3
External assets
0
Incoming endpoints
0
No external asset domains detected.
No public endpoints detected.
First score snapshot
v3.1.0
41
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 41 | 71 | 56 | 15 | v3.1.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.