Prioritized issue groups from the latest Plugin Check scan
Security
42
7 issue groups
I18n
39
4 issue groups
Maintainability
24
10 issue groups
Supply Chain
1
1 issue group
Sample message
Mismatched text domain. Expected 'acf-image-aspect-ratio-crop' but got 'acf'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"<input type='hidden' name='aiarc_temp_post_id' value='$this->temp_post_id'>"'.
Sample message
$_GET['page'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Detected usage of meta_query, possible slow query.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Processing form data without nonce verification.
Sample message
Function "parse_blocks()" requires WordPress 5.0.0, but your plugin minimum supported version is WordPress 4.9.0.
Sample message
Detected usage of a non-sanitized input variable: $_GET['page']
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
error_log() found. Debug code should not normally be used in production.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "npx_acf_field_image_aspect_ratio_crop".
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wpml_object_id".
Sample message
print_r() found. Debug code should not normally be used in production.
Sample message
Processing form data without nonce verification.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Advanced Custom Fields: Image Aspect Ratio Crop 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
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
Detected usage of a possibly undefined superglobal array index: $_POST['acf']. Check that the array index exists before using it.
Sample message
unlink() is discouraged. Use wp_delete_file() to delete a file.
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
Multiple placeholders in translatable strings should be ordered. Expected "%1$d, %2$d", but got "%d, %d" in 'Image too small. Minimum image dimensions are %d×%d pixels.'.
Sample message
Hidden files are not permitted.
Sample message
Plugin name "Advanced Custom Fields: Image Aspect Ratio Crop Field" is different from the name declared in plugin header "Advanced Custom Fields: Image Aspect Ratio Crop".
Sample message
Tested up to: 6.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.
Not analyzed yet.
First score snapshot
v6.0.5
35
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 35 | 107 | 70 | 37 | v6.0.5 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.