Map your Gravity-Forms-generated posts to a custom post type and/or custom taxonomies.
Category Scores
Top Issues by Category
security24
i18n14
maintainability12
repo_compliance1
Issues Details
51 issues found in latest scan
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$message'.
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Mismatched text domain. Expected 'gravity-forms-custom-post-types' but got 'gravityforms'.
The $domain parameter must be a single text string literal. Found: self::$slug
Resource version not set in call to wp_register_script(). This means new versions of the script may not always be loaded due to browser caching.
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
The plugin name includes a restricted term. Your chosen plugin name - "Gravity Forms + Custom Post Types" - contains the restricted term "gravity-forms" 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 "gravity-forms" elsewhere in your plugin name, such as "... for gravity-forms".
The parameter "'orderby=name&hide_empty=0&fields=names'" at position #2 of get_terms() has been deprecated since WordPress version 4.5.0. Instead do not pass the parameter.
Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_register_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development.
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.
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.
| Code | Type | Message | Count |
|---|---|---|---|
| WordPress.Security.EscapeOutput.OutputNotEscaped | ERROR | All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$message'. | 14 |
| WordPress.Security.EscapeOutput.UnsafePrintingFunction | ERROR | All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'. | 10 |
| WordPress.WP.I18n.TextDomainMismatch | ERROR | Mismatched text domain. Expected 'gravity-forms-custom-post-types' but got 'gravityforms'. | 7 |
| WordPress.WP.I18n.NonSingularStringLiteralDomain | ERROR | The $domain parameter must be a single text string literal. Found: self::$slug | 6 |
| WordPress.WP.EnqueuedResourceParameters.MissingVersion | WARNING | Resource version not set in call to wp_register_script(). This means new versions of the script may not always be loaded due to browser caching. | 3 |
| missing_direct_file_access_protection | ERROR | PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit; | 3 |
| trademarked_term | WARNING | The plugin name includes a restricted term. Your chosen plugin name - "Gravity Forms + Custom Post Types" - contains the restricted term "gravity-forms" 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 "gravity-forms" elsewhere in your plugin name, such as "... for gravity-forms". | 3 |
| WordPress.WP.DeprecatedParameters.Get_termsParam2Found | ERROR | The parameter "'orderby=name&hide_empty=0&fields=names'" at position #2 of get_terms() has been deprecated since WordPress version 4.5.0. Instead do not pass the parameter. | 1 |
| WordPress.WP.EnqueuedResourceParameters.NoExplicitVersion | ERROR | Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_register_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development. | 1 |
| WordPress.WP.EnqueuedResourceParameters.NotInFooter | WARNING | 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. | 1 |
| WordPress.WP.I18n.MissingArgDomain | ERROR | Missing $domain parameter in function call to __(). | 1 |
| outdated_tested_upto_header | ERROR | 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. | 1 |
Latest Snapshot
Findings
51
Errors
44
Warnings
7
Score History
First score snapshot
First scan completed Jun 20, 2026
v3.1.31 · Plugin Check 2.0.0 · Model 2026.06-mvp-static-v2
Jun 20, 2026
v3.1.31
54
Latest
- Findings
- 51
- Errors
- 44
- Warnings
- 7
- Plugin Check
- 2.0.0
- Model
- 2026.06-mvp-static-v2
| Scan | Score | Findings | Errors | Warnings | Plugin | Plugin Check | Model |
|---|---|---|---|---|---|---|---|
| Jun 20, 2026Latest | 54 | 51 | 44 | 7 | v3.1.31 | 2.0.0 | 2026.06-mvp-static-v2 |