This plugin allows multilingual contact form 7 management using the polylang plugin.
Prioritized issue groups from the latest Plugin Check scan
Security
37
7 issue groups
Maintainability
30
15 issue groups
I18n
4
3 issue groups
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$button'.
Sample message
Processing form data without nonce verification.
Sample message
$_GET['locale'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Short PHP opening tag used with echo; expected "<?php echo $dismiss ..." but found "<?= $dismiss ..."
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "activate_cf7_polylang".
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$debug_msg_last_file".
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST['_wpcf7_lang']. Check that the array index exists before using it.
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
Detected usage of a non-sanitized input variable: $_GET['locale']
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "cf7pll_load_plugin_translation_resource".
Sample message
Processing form data without nonce verification.
Sample message
Mismatched text domain. Expected 'cf7-polylang' but got 'cf7_polylang'.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Contact Form 7 Polylang Module" - contains the restricted term "contact-form-7" and cannot be used to begin your plugin name. We disallow the use of certain terms in ways that are abused, or potentially infringe on and/or are misleading with regards to trademarks. You may use the term "contact-form-7" elsewhere in your plugin name, such as "... for contact-form-7".
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
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "PAnD".
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "WP_GURUS_DEBUG".
Sample message
debug_backtrace() found. Debug code should not normally be used in production.
Sample message
error_log() found. Debug code should not normally be used in production.
Sample message
print_r() found. Debug code should not normally be used in production.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
unlink() is discouraged. Use wp_delete_file() to delete a file.
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.
Not analyzed yet.
First score snapshot
v2.4.1
36
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 36 | 77 | 32 | 45 | v2.4.1 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.