A Typography Add-on for the Advanced Custom Fields Plugin.
Prioritized issue groups from the latest Plugin Check scan
I18n
234
3 issue groups
Security
190
3 issue groups
Maintainability
76
14 issue groups
Repo Compliance
2
2 issue groups
Sample message
Mismatched text domain. Expected 'acf-typography-field' but got 'acf'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$data_required'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "acf/create_field".
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "acf_typography_shortcode".
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "acf_field_Typography".
Sample message
The $text parameter must be a single text string literal. Found: ucwords(str_replace('_', ' ', $f))
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
Sanitization missing for register_setting().
Sample message
Plugin folders are deleted when upgraded. Do not save data to the plugin folder using fwrite(). Detected usage of function plugin_dir_path(). Use wp_upload_dir() to get the uploads directory path or save to the database instead.
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "YOUR_API_KEY".
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().
Sample message
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
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
The $text text string should have translatable content. Found: ''
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Advanced Custom Fields: Typography 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
Function "parse_blocks()" requires WordPress 5.0.0, but your plugin minimum supported version is WordPress 3.5.0.
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
One or more tags were ignored. Please limit your plugin to 5 tags.
Not analyzed yet.
First score snapshot
v3.2.3
33
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 33 | 502 | 445 | 57 | v3.2.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.