BuddyPress Profile Completion Plugin allows site admins to force BuddyPress site members to fill all required profile fields, upload profile photo and …
Prioritized issue groups from the latest Plugin Check scan
Maintainability
24
10 issue groups
Security
23
8 issue groups
I18n
9
1 issue group
Repo Compliance
2
2 issue groups
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"<div class='wrap pt-settings-page-wrap {$slug}'>"'.
Sample message
Mismatched text domain. Expected 'buddypress-profile-completion' but got 'bp-profile-completion'.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "bp_force_profile_completion_skip_check".
Sample message
Namespaces declared by a theme/plugin should start with the theme/plugin prefix. Found: "BP_Profile_Completion\Admin".
Sample message
Use placeholders and $wpdb->prepare(); found interpolated variable {$fields_list} at "SELECT field_id, value FROM {$table} WHERE user_id = %d AND field_id IN {$fields_list} GROUP BY field_id"
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "BuddyPress Profile Completion" - contains the restricted term "buddypress" 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 "buddypress" elsewhere in your plugin name, such as "... for buddypress".
Sample message
Unescaped parameter $query used in $wpdb->get_results()\n$query assigned unsafely at line 374.
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
Use placeholders and $wpdb->prepare(); found $query
Sample message
Processing form data without nonce verification.
Sample message
Resource version not set in call to wp_register_script(). This means new versions of the script may not always be loaded due to browser caching.
Sample message
In footer ($in_footer) is not set explicitly wp_register_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Sample message
Function "sanitize_textarea_field()" requires WordPress 4.7.0, but your plugin minimum supported version is WordPress 4.5.0.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "BP_Profile_Completion".
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "bp_profile_completion".
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: $_POST['key']
Sample message
$_POST['key'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Tested up to: 6.3 < 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 "Short Description" section is too long and was truncated. A maximum of 150 characters is supported.
Potential connections found in static code analysis.
Outbound calls
7
External assets
0
Incoming endpoints
1
No external asset domains detected.
No public endpoints detected.
wp_ajax
First score snapshot
v1.1.0
40
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 40 | 58 | 28 | 30 | v1.1.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.