Skip to content

Dev

Dev #2

Triggered via pull request October 4, 2024 07:16
Status Failure
Total duration 1m 49s
Artifacts

plugin-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 8 warnings
WordPress.WP.I18n.MissingTranslatorsComment: rrze-elements-blocks.php#L74
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: rrze-elements-blocks.php#L76
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.Security.EscapeOutput.OutputNotEscaped: rrze-elements-blocks.php#L91
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$error'.
hidden_files: .gitignore#L1
Hidden files are not permitted.
hidden_files: .eslintrc.json#L1
Hidden files are not permitted.
WordPress.Security.EscapeOutput.ExceptionNotEscaped: includes/Plugin.php#L200
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$message'.
WordPress.WP.AlternativeFunctions.file_get_contents_file_get_contents: includes/Patterns.php#L217
file_get_contents() is discouraged. Use wp_remote_get() for remote URLs instead.
WordPress.WP.AlternativeFunctions.rand_rand: includes/Patterns.php#L246
rand() is discouraged. Use the far less predictable wp_rand() instead.
WordPress.DateTime.RestrictedFunctions.date_date: includes/Helper.php#L94
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
missing_readme_header: readme.md#L1
Your readme is either missing or incomplete. The "Tested up to" field is missing. Your readme has to have headers as well as a proper description and documentation as to how it works and how one can use it.
textdomain_mismatch: rrze-elements-blocks.php#L1
The TextDomain header in the plugin file does not match the slug. Found "rrze-elements-b", expected "rrze-elements-blocks".
readme_parser_warnings_trimmed_short_description: readme.md#L1
The "Short Description" section is too long and was truncated. A maximum of 150 characters is supported.
WordPress.WP.EnqueuedResourceParameters.NotInFooter: includes/Main.php#L110
In footer ($in_footer) is not set explicitly wp_register_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.NotInFooter: includes/Main.php#L116
In footer ($in_footer) is not set explicitly wp_register_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.NotInFooter: includes/Main.php#L122
In footer ($in_footer) is not set explicitly wp_register_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.NotInFooter: includes/Main.php#L135
In footer ($in_footer) is not set explicitly wp_register_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.NotInFooter: includes/Main.php#L141
In footer ($in_footer) is not set explicitly wp_register_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.
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/