Page Tagger

Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "PageTagger".

Unescaped parameter $cptSql used in $wpdb->get_var($wpdb->prepare( "SELECT COUNT(*) FROM $wpdb->term_relationships, $wpdb->posts WHERE $wpdb->posts.ID = $wpdb->term_relationships.object_id AND $wpdb->posts.post_status != 'draft' AND (post_type = 'post' OR post_type = 'page' $cptSql) AND term_taxonomy_id = %d", $term ))\n$cptSql assigned unsafely at line 167:\n $cptSql = ' OR ' . $cptSql\n$cptSql assigned unsafely at line 165:\n $cptSql = '' . implode(' OR ', $this->_get_custom_post_types_sql())

Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.

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.

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "_page_tagger_min_version_notice".

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.

Tested up to: 3.4 < 6.8. 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.

Missing "License". Please update your readme with a valid GPLv2 (or later) compatible license.

Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_register_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development.

Missing $domain parameter in function call to __().