Emmet (ex-Zen Coding) for WordPress.
Prioritized issue groups from the latest Plugin Check scan
Security
86
2 issue groups
I18n
55
4 issue groups
Maintainability
17
8 issue groups
Repo Compliance
4
4 issue groups
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$form'.
Sample message
The $domain parameter must be a single text string literal. Found: $domain
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Missing $domain parameter in function call to __().
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
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.
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 plugin name includes a restricted term. Your chosen plugin name - "WP Emmet" - contains the restricted term "wp" which cannot be used at all in your plugin name.
Sample message
Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_enqueue_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development.
Sample message
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
The $text parameter must be a single text string literal. Found: $label
Sample message
Plugin name header in your readme is missing or invalid. Please update your readme with a valid plugin name header. Eg: "=== Example Name ==="
Sample message
Library files that are already in the WordPress core are not permitted.
Sample message
Tested up to: 4.1 < 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
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
One or more tags were ignored. The following tags are not permitted: "plugin", "wordpress"
Sample message
The readme short description contains unofficial language. It must be written in standard English.
Sample message
Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". 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.
Not analyzed yet.
First score snapshot
v0.3.4
37
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 37 | 162 | 154 | 8 | v0.3.4 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.