Theme and plugin translation using Polylang for WordPress. Extension for Polylang plugin.
Prioritized issue groups from the latest Plugin Check scan
Security
89
8 issue groups
I18n
43
4 issue groups
Maintainability
31
7 issue groups
Repo Compliance
1
1 issue group
Sample message
Mismatched text domain. Expected 'theme-translation-for-polylang' but got 'polylang-tt'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"<div class=\"$class\"> <p>$this->plugin_name: $message</p></div>"'.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "convert_pll_to_polylang_pro".
Sample message
Processing form data without nonce verification.
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of a non-sanitized input variable: $_FILES["import_strings"]["tmp_name"]
Sample message
$_GET['_msg'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "pll_language_defined".
Sample message
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
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.
Sample message
Detected usage of a possibly undefined superglobal array index: $_FILES["import_strings"]["size"]. Check that the array index exists before using it.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Theme and plugin translation for Polylang (TTfP)" - contains the restricted term "plugin" which cannot be used at all in your plugin name.
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
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$theme".
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
The parameter "FALSE" at position #2 of load_plugin_textdomain() has been deprecated since WordPress version 2.7.0. Use "" instead.
Sample message
Tested up to: 6.6 < 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
The "Text Domain" header in the plugin file does not match the slug. Found "polylang-tt", expected "theme-translation-for-polylang".
Not analyzed yet.
First score snapshot
v3.4.9
40
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 40 | 164 | 102 | 62 | v3.4.9 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.