PHPCS Fixes #5
dshanskeAnnotations
10 errors and 10 warnings
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L10
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_option'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L39
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L39
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_the_title_rss'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L42
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L42
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_bloginfo_rss'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L45
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L45
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_wp_title_rss'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L52
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_feed_build_date'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L56
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'apply_filters'.
|
|
WordPress.Security.EscapeOutput.OutputNotEscaped:
templates/feed-rss2-comments.php#L62
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'apply_filters'.
|
|
WordPress.Security.NonceVerification.Recommended:
templates/reply-metabox.php#L12
Processing form data without nonce verification.
|
|
WordPress.Security.NonceVerification.Recommended:
templates/reply-metabox.php#L13
Processing form data without nonce verification.
|
|
WordPress.Security.NonceVerification.Missing:
includes/class-kind-metabox.php#L99
Processing form data without nonce verification.
|
|
WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_exclude:
includes/class-kind-taxonomy.php#L581
Using exclusionary parameters, like exclude, 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.
|
|
WordPress.Security.NonceVerification.Recommended:
includes/class-kind-taxonomy.php#L965
Processing form data without nonce verification.
|
|
WordPress.Security.NonceVerification.Recommended:
includes/class-kind-taxonomy.php#L966
Processing form data without nonce verification.
|
|
WordPress.Security.NonceVerification.Recommended:
includes/class-kind-taxonomy.php#L1158
Processing form data without nonce verification.
|
|
WordPress.Security.NonceVerification.Recommended:
includes/class-kind-taxonomy.php#L1158
Processing form data without nonce verification.
|
|
upgrade_notice_limit:
readme.txt#L1
The upgrade notice for "3.6.0" exceeds the limit of 300 characters.
|
|
upgrade_notice_limit:
readme.txt#L1
The upgrade notice for "3.1.0" exceeds the limit of 300 characters.
|