Build interactive family trees, create ancestor profiles, and display your genealogy data beautifully on any WordPress site.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
1,625
16 issue groups
Security
553
6 issue groups
I18n
5
2 issue groups
Performance
3
1 issue group
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$account_addon_ids".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '" <a href='{$skip_url}' class='button button-small button-secondary'>{$use_plugin_anonymously_text}</a>"'.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "_fs_text".
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "FS_Admin_Menu_Manager".
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "FS_API__ADDRESS".
Sample message
Detected usage of meta_query, possible slow query.
Sample message
Namespaces declared by a theme/plugin should start with the theme/plugin prefix. Found: "Zqe".
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$message'.
Sample message
Use of a direct database call is discouraged.
Sample message
Detected usage of tax_query, possible slow query.
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "colabaration".
Sample message
Processing form data without nonce verification.
Sample message
Processing form data without nonce verification.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
print_r() found. Debug code should not normally be used in production.
Sample message
$_POST['_inline_edit'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Missing $domain parameter in function call to __().
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
Using exclusionary parameters, like post__not_in, 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
Attempting a database schema change is discouraged.
Sample message
Plugin Updater detected. These are not permitted in WordPress.org hosted plugins. Detected: class FS_Plugin_Updater
Sample message
Plugin Updater detected. Detected code which may be altering WordPress update routines. Detected: _site_transient_update_plugins
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.
Potential connections found in static code analysis.
Outbound calls
218
External assets
3
Incoming endpoints
14
wp_ajax
wp_ajax
wp_ajax
wp_ajax
admin_post
admin_post
admin_post
wp_ajax
wp_ajax
wp_ajax
wp_ajax
wp_ajax
wp_ajax
wp_ajax
First score snapshot
v2.2.8
24
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 24 | 2,201 | 560 | 1,641 | v2.2.8 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.