Automatically generate the code needed to implement Advanced Custom Fields in your themes.
Prioritized issue groups from the latest Plugin Check scan
Security
479
8 issue groups
Maintainability
36
9 issue groups
Repo Compliance
2
2 issue groups
I18n
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 '$args'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$args".
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Use placeholders and $wpdb->prepare(); found $field_group_post_obj
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
Processing form data without nonce verification.
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_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
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
Unescaped parameter $table used in $wpdb->get_results()\n$table assigned unsafely at line 127.
Sample message
Unescaped parameter $postmeta_table_name used in $wpdb->get_results()\n$postmeta_table_name assigned unsafely at line 111.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "acf/get_info".
Sample message
Detected usage of a non-sanitized input variable: $_GET["debug"]
Sample message
$_GET["debug"] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Library files that are already in the WordPress core are not permitted.
Sample message
Plugin name "ACF Theme Code for Advanced Custom Fields" is different from the name declared in plugin header "Advanced Custom Fields: Theme Code".
Sample message
Tested up to: 6.4 < 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
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Advanced Custom Fields: Theme Code" - 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
Function "wp_set_script_translations()" requires WordPress 5.0.0, but your plugin minimum supported version is WordPress 4.9.0.
Not analyzed yet.
First score snapshot
v2.5.6
40
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 40 | 518 | 478 | 40 | v2.5.6 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.