BuddyPress notification widget allow site admins to show BuddyPress user notification in widget.
Prioritized issue groups from the latest Plugin Check scan
Security
48
3 issue groups
Maintainability
32
10 issue groups
I18n
3
2 issue groups
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 '$alt'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$alt".
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "bpnw_load_template".
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "BuddyPress Notification Widget" - 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
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
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
Use placeholders and $wpdb->prepare(); found interpolated variable {$bp->core->table_name_notifications} at "DELETE FROM {$bp->core->table_name_notifications} WHERE user_id = %d "
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "BP_Notification_Shortcode_Helper".
Sample message
Resource version not set in call to wp_enqueue_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_enqueue_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
Mismatched text domain. Expected 'buddypress-notifications-widget' but got 'buddypress-notification-widget'.
Sample message
Your plugin has a different license declared in the readme file and plugin header. Please update your readme with a valid GPL license identifier.
Sample message
Plugin name "BuddyPress Notification Widget" is different from the name declared in plugin header "BuddyPress Notifications Widget".
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.
Potential connections found in static code analysis.
Outbound calls
2
External assets
0
Incoming endpoints
1
No external asset domains detected.
No public endpoints detected.
wp_ajax
First score snapshot
v1.3.3
39
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 39 | 85 | 54 | 31 | v1.3.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.