Custom Post Type Sticky

Sample message

Mismatched text domain. Expected 'custom-post-type-sticky' but got 'cpt_sticky'.

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 $sticky_posts at "SELECT COUNT( 1 ) FROM $wpdb->posts WHERE post_type = %s AND post_status NOT IN ('trash', 'auto-draft') AND ID IN ($sticky_posts)"

Sample message

The parameter "FALSE" at position #2 of load_plugin_textdomain() has been deprecated since WordPress version 2.7.0. Use "" instead.

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

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

Sample message

Plugin name "Custom Post Type Sticky" is different from the name declared in plugin header "Custom post type sticky".

Sample message

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;