Easily manage your BuddyPress Activity Stream by filtering specific activity types, setting default filters, and enabling public Custom Post Types (CP …
Prioritized issue groups from the latest Plugin Check scan
Security
60
6 issue groups
Maintainability
22
10 issue groups
I18n
5
2 issue groups
Repo Compliance
3
3 issue groups
Sample message
Processing form data without nonce verification.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$bg_color'.
Sample message
Processing form data without nonce verification.
Sample message
$_COOKIE['bp-activity-filter'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
error_log() found. Debug code should not normally be used in production.
Sample message
Detected usage of a non-sanitized input variable: $_POST['bp_activity_filter_cpt_settings']
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.
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
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Detected usage of meta_key, possible slow query.
Sample message
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "BuddyPress Activity Filter" - 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
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
Detected usage of meta_query, possible slow query.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$self".
Sample message
debug_backtrace() found. Debug code should not normally be used in production.
Sample message
Hidden files are not permitted.
Sample message
Tested up to: 6.8 < 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 "Short Description" section is too long and was truncated. A maximum of 150 characters is supported.
Sample message
The upgrade notice for "4.0.0" exceeds the limit of 300 characters.
Potential connections found in static code analysis.
Outbound calls
45
External assets
0
Incoming endpoints
0
No external asset domains detected.
No public endpoints detected.
First score snapshot
v3.2.0
35
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 35 | 91 | 25 | 66 | v3.2.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.