Remove Fields from woocommerce Checkout page
Category Scores
Issues to Review
Prioritized issue groups from the latest Plugin Check scan
I18n
47
2 issue groups
Maintainability
3
2 issue groups
Security
2
2 issue groups
Repo Compliance
1
1 issue group
ERRORI18nText Domain MismatchMismatched text domain. Expected 'remove-default-checkout-fields-for-woocommerce' but got 'Remove-Checkout-Fields'.46
- Category
- I18n
- Occurrences
- 46
- Severity
- error
Sample message
Mismatched text domain. Expected 'remove-default-checkout-fields-for-woocommerce' but got 'Remove-Checkout-Fields'.
ERRORMaintainabilityMissing direct file access protectionPHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;2
- Category
- Maintainability
- Occurrences
- 2
- Severity
- error
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
ERRORSecurityOutput is not escapedAll output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'wp_redirect'.1
- Category
- Security
- Occurrences
- 1
- Severity
- error
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'wp_redirect'.
WARNINGSecuritywp redirect wp redirectwp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.1
- Category
- Security
- Occurrences
- 1
- Severity
- warning
Sample message
wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.
WARNINGMaintainabilitymismatched plugin namePlugin name "Remove Checkout Fields for Woocommerce" is different from the name declared in plugin header "Remove Default Checkout Fields for Woocommerce".1
- Category
- Maintainability
- Occurrences
- 1
- Severity
- warning
Sample message
Plugin name "Remove Checkout Fields for Woocommerce" is different from the name declared in plugin header "Remove Default Checkout Fields for Woocommerce".
ERRORRepo Complianceoutdated tested upto headerTested up to: 6.7 < 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
- Category
- Repo Compliance
- Occurrences
- 1
- Severity
- error
Sample message
Tested up to: 6.7 < 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.
ERRORI18ntextdomain invalid formatThe "Text Domain" header in the plugin file should only contain lowercase letters, numbers, and hyphens. Found "Remove-Checkout-Fields".1
- Category
- I18n
- Occurrences
- 1
- Severity
- error
Sample message
The "Text Domain" header in the plugin file should only contain lowercase letters, numbers, and hyphens. Found "Remove-Checkout-Fields".
External Connections
Potential connections found in static code analysis.
Outbound calls
2
External assets
0
Incoming endpoints
0
Notable Domains
Platform / Reference Domains
External Asset Domains
No external asset domains detected.
Incoming Endpoints
No public endpoints detected.
Score History
First score snapshot
v1.5
88
Latest
- Findings
- 53
- Errors
- 51
- Warnings
- 2
- Check
- 2.0.0
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 88 | 53 | 51 | 2 | v1.5 | 2.0.0 |
Relationship Map
Author, categories, issues, domains, and nearby plugins.