Makes BuddyPress's invitation features more powerful.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
97
15 issue groups
Security
61
4 issue groups
Repo Compliance
3
3 issue groups
Performance
1
1 issue group
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "accept_email_invite_before".
Sample message
Detected usage of a non-sanitized input variable: $_COOKIE['invite-anyone']
Sample message
$_GET[$this->get_order_key] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Function "get_user_count()" requires WordPress 4.8.0, but your plugin minimum supported version is WordPress 3.2.0.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST['friend_action']. Check that the array index exists before using it.
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
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "BBG_CPT_Pag".
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$cloudsponge_integration".
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "BP_INVITE_ANYONE_DB_VER".
Sample message
Unescaped parameter $table_contents_sql used in $wpdb->get_results()\n$table_contents_sql assigned unsafely at line 1024.
Sample message
Detected usage of meta_key, possible slow query.
Sample message
Detected usage of tax_query, possible slow query.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "bp_get_new_group_invite_member_list".
Sample message
Detected usage of meta_value, possible slow query.
Sample message
Using exclusionary parameters, like exclude, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.
Sample message
Application files are not permitted.
Sample message
Library files that are already in the WordPress core are not permitted.
Sample message
The "/vendor" directory using composer exists, but "composer.json" file is missing.
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
One or more tags were ignored. Please limit your plugin to 5 tags.
Sample message
The readme short description contains unofficial language. It must be written in standard English.
Potential connections found in static code analysis.
Outbound calls
19
External assets
0
Incoming endpoints
2
No external asset domains detected.
No public endpoints detected.
wp_ajax
wp_ajax
First score snapshot
v1.4.10
40
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 40 | 162 | 32 | 130 | v1.4.10 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.