Skip to content

Fixes in the documentation #831

Fixes in the documentation

Fixes in the documentation #831

Triggered via push May 25, 2026 20:39
Status Success
Total duration 2m 39s
Artifacts 1

plugin-check.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound: includes/Frontend/Output.php#L149
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::MSLS_ALTERNATE_LINKS_ARR_HOOK".
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound: includes/Frontend/Output.php#L146
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::MSLS_ALTERNATE_LINKS_DEFAULT_HOOK".
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound: includes/Frontend/Output.php#L130
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::MSLS_ALTERNATE_LINKS_HOOK".
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound: includes/Frontend/Output.php#L101
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::MSLS_GET_HOOK".
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound: includes/Frontend/Widget.php#L58
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::MSLS_ALTERNATIVE_CONTENT_HOOK".
WordPress.NamingConventions.PrefixAllGlobals.DynamicHooknameFound: includes/Frontend/Map/HrefLang.php#L69
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "self::MSLS_HEAD_HREFLANG_HOOK".
WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in: includes/RestApi/RestApi.php#L409
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.
WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in: includes/Admin/CustomFilter.php#L89
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.
WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in: includes/Admin/TranslationPicker/Table.php#L182
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.
PluginCheck.CodeAnalysis.DiscouragedFunctions.load_plugin_textdomainFound: includes/Plugin.php#L204
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.

Artifacts

Produced during runtime
Name Size Digest
plugin-check-results
1.35 KB
sha256:7a41ebb8a16f4fd64f924f8fc0452f074b2e77d976987be0d41ccdc1c5108136