Type in Hindi inside WordPress. Hello -> हेलो. WPHindi helps you save time by letting you type inside Classic Editor and Gutenberg in Hindi.
Category Scores
Issues to Review
Prioritized issue groups from the latest Plugin Check scan
Maintainability
14
7 issue groups
Repo Compliance
2
2 issue groups
WARNINGMaintainabilityNot In FooterIn 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.3
- Category
- Maintainability
- Occurrences
- 3
- Severity
- warning
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.
WARNINGMaintainabilitytrademarked termThe plugin name includes a restricted term. Your chosen plugin name - "WPHindi - Type in Hindi in WordPress" - contains the restricted term "wordpress" which cannot be used at all in your plugin name.3
- Category
- Maintainability
- Occurrences
- 3
- Severity
- warning
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "WPHindi - Type in Hindi in WordPress" - contains the restricted term "wordpress" which cannot be used at all in your plugin name.
ERRORMaintainabilityOffloaded ContentFound call to wp_enqueue_script() with external resource. Offloading scripts to your servers or any remote service is disallowed.2
- Category
- Maintainability
- Occurrences
- 2
- Severity
- error
Sample message
Found call to wp_enqueue_script() with external resource. Offloading scripts to your servers or any remote service is disallowed.
WARNINGMaintainabilityMissing VersionResource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.2
- Category
- Maintainability
- Occurrences
- 2
- Severity
- warning
Sample message
Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.
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;
WARNINGMaintainabilityNon-prefixed classClasses declared by a theme/plugin should start with the theme/plugin prefix. Found: "Zozuk_Transliterator".1
- Category
- Maintainability
- Occurrences
- 1
- Severity
- warning
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "Zozuk_Transliterator".
ERRORMaintainabilityno stable tagInvalid or missing Stable Tag. Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.1
- Category
- Maintainability
- Occurrences
- 1
- Severity
- error
Sample message
Invalid or missing Stable Tag. Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.
ERRORRepo Complianceoutdated tested upto headerTested up to: 5.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.1
- Category
- Repo Compliance
- Occurrences
- 1
- Severity
- error
Sample message
Tested up to: 5.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.
ERRORRepo Complianceplugin header no licenseMissing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.1
- Category
- Repo Compliance
- Occurrences
- 1
- Severity
- error
Sample message
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
External Connections
Potential connections found in static code analysis.
Outbound calls
10
External assets
2
Incoming endpoints
0
Notable Domains
External Asset Domains
Incoming Endpoints
No public endpoints detected.
Score History
First score snapshot
v2.3.1
95
Latest
- Findings
- 16
- Errors
- 7
- Warnings
- 9
- Check
- 2.0.0
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 95 | 16 | 7 | 9 | v2.3.1 | 2.0.0 |
Relationship Map
Author, categories, issues, domains, and nearby plugins.