JS/ CSS exclusions don't need (or accept) wildcards/ regex patterns. #9
Annotations
6 errors and 10 warnings
WordPress.WP.I18n.MissingTranslatorsComment:
classes/autoptimizeConfig.php#L368
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.
|
WordPress.WP.I18n.MissingTranslatorsComment:
classes/autoptimizeCriticalCSSBase.php#L362
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.
|
WordPress.WP.I18n.MissingTranslatorsComment:
classes/autoptimizeMain.php#L760
A function call to esc_html__() 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.
|
stable_tag_mismatch:
readme.txt#L1
The Stable Tag in your readme file does not match the version in your main plugin file.
|
localhost_code_detected:
classes/autoptimizeCache.php#L1
Do not use Localhost/127.0.0.1 in your code.
|
Plugin Checker
Process completed with exit code 1.
|
WordPress.WP.EnqueuedResourceParameters.MissingVersion:
classes/autoptimizeConfig.php#L742
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.
|
WordPress.WP.EnqueuedResourceParameters.MissingVersion:
classes/autoptimizeConfig.php#L747
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
|
WordPress.WP.EnqueuedResourceParameters.MissingVersion:
classes/autoptimizeConfig.php#L748
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
|
WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_exclude:
classes/autoptimizeCriticalCSSSettingsAjax.php#L261
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.
|
WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_exclude:
classes/autoptimizeCriticalCSSSettingsAjax.php#L275
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.WP.EnqueuedResourceParameters.NotInFooter:
classes/autoptimizeExitSurvey.php#L24
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.
|
WordPress.WP.EnqueuedResourceParameters.MissingVersion:
classes/autoptimizeCriticalCSSSettings.php#L96
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
|
WordPress.WP.EnqueuedResourceParameters.MissingVersion:
classes/autoptimizeCriticalCSSSettings.php#L97
Resource version not set in call to wp_enqueue_style(). This means new versions of the style may not always be loaded due to browser caching.
|
WordPress.WP.EnqueuedResourceParameters.MissingVersion:
classes/autoptimizeCriticalCSSSettings.php#L100
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.
|
WordPress.WP.EnqueuedResourceParameters.NotInFooter:
classes/autoptimizeCriticalCSSSettings.php#L100
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.
|