This plugin adds Polylang support for WordPress Customizer.
Prioritized issue groups from the latest Plugin Check scan
Security
19
7 issue groups
I18n
10
5 issue groups
Maintainability
6
5 issue groups
Repo Compliance
3
3 issue groups
Sample message
Processing form data without nonce verification.
Sample message
Mismatched text domain. Expected 'add-polylang-support-for-customizer' but got 'apsfc'.
Sample message
Processing form data without nonce verification.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$GLOBAL".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$message'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Detected usage of a non-sanitized input variable: $_REQUEST['lang']
Sample message
$_REQUEST['lang'] not unslashed before sanitization. Use wp_unslash() or similar
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
Sanitization missing for register_setting().
Sample message
var_dump() found. Debug code should not normally be used in production.
Sample message
rand() is discouraged. Use the far less predictable wp_rand() instead.
Sample message
Missing $domain parameter in function call to __().
Sample message
The $text parameter must be a single text string literal. Found: '<strong>Polylang</strong> plugin must be activated for <strong>Add Polylang support for Customizer</strong> plugin to work. Please <a href="' . admin_url('plugins.php') . '">activate it</a> now!'
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Tested up to: 6.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
The "Donate link" header in the readme file must be a valid URL.
Sample message
One or more tags were ignored. The following tags are not permitted: "plugin", "wordpress"
Sample message
The "Text Domain" header in the plugin file does not match the slug. Found "apsfc", expected "add-polylang-support-for-customizer".
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.4.5
48
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 48 | 38 | 18 | 20 | v1.4.5 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.