Improve your web typography with: hyphenation, space control, intelligent character replacement, and CSS hooks.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
112
15 issue groups
Security
6
2 issue groups
I18n
5
2 issue groups
Repo Compliance
1
1 issue group
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$__composer_autoload_files".
Sample message
The $domain parameter must be a single text string literal. Found: $this->textdomain
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 '"Invalid fixer group {$group}."'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$err'.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().
Sample message
Library files that are already in the WordPress core are not permitted.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "wp-Typography" - contains the restricted term "wp" which cannot be used at all in your plugin name.
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
set_error_handler() found. Debug code should not normally be used in production.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
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
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "humbug_phpscoper_expose_class".
Sample message
error_reporting() can lead to full path disclosure.
Sample message
Editor blocks must define "apiVersion" 3 or higher in block.json for WordPress 7.0+ iframe editor compatibility.
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.
Not analyzed yet.
First score snapshot
v5.11.0
67
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 67 | 124 | 91 | 33 | v5.11.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.