Enhance TinyMCE visual editor with a dedicated stylesheet, a stylesheet shared with the frontend, and custom styles in the Formats dropdown.
Prioritized issue groups from the latest Plugin Check scan
Security
227
7 issue groups
I18n
134
4 issue groups
Maintainability
10
6 issue groups
Repo Compliance
2
2 issue groups
Sample message
The $domain parameter must be a single text string literal. Found: TCS_TEXTDOMAIN
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"$op_ct"'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Processing form data without nonce verification.
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
Detected usage of a possibly undefined superglobal array index: $_POST[$k]. Check that the array index exists before using it.
Sample message
$_POST[$k] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Multiple placeholders in translatable strings should be ordered. Expected "%1$s, %2$s", but got "%s, %s" in '%s Settings %s'.
Sample message
Detected usage of a non-sanitized input variable: $_POST[$k]
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
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().
Sample message
Resource version not set in call to wp_register_style(). This means new versions of the style may not always be loaded due to browser caching.
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
Using __FILE__ for menu slugs risks exposing filesystem structure.
Sample message
Your plugin has a different license declared in the readme file and plugin header. Please update your readme with a valid GPL license identifier.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Tested up to: 6.5 < 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
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
v1.1.5
39
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 39 | 373 | 297 | 76 | v1.1.5 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.