A Table Field Add-on for the Advanced Custom Fields and Secure Custom Fields Plugin.
Prioritized issue groups from the latest Plugin Check scan
I18n
7
2 issue groups
Maintainability
3
3 issue groups
Security
1
1 issue group
Repo Compliance
1
1 issue group
Sample message
Mismatched text domain. Expected 'advanced-custom-fields-table-field' but got 'polylang-pro'.
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
trigger_error() found. Debug code should not normally be used in production.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$e'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Tested up to: 6.9 < 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 slug includes a restricted term. Your plugin slug - "advanced-custom-fields-table-field" - contains the restricted term "advanced-custom-fields" and cannot be used to begin your plugin slug. 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 slug, such as "... for advanced-custom-fields".
Not analyzed yet.
First score snapshot
v1.3.35
92
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 92 | 12 | 9 | 3 | v1.3.35 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.