New version of Plugin Check Plugin 1.3.0

A new version of Plugin Check Plugin has been released.

Version 1.3.0 brings enhancements, including new checks for plugin headers, readme file validation, and stricter code quality measures such as restricting parse_str and disallowing HEREDOC and NOWDOC. It adds support for the MPL-2.0 license, improves handling of localhost URLs, and encourages best practices like using native functions for images and avoiding query_posts(). The update also refines license checks, allows custom paths for checks, and includes CLI improvements for low-severity errors and runtime setup. Additionally, various fixes address validation issues, runtime check execution, and file path handling, ensuring better compatibility and adherence to WordPress standards.

In detail, you can see all changes below.

Enhancements

  1. Plugin Header Checks
    • Added validation for missing plugin description and version.
    • Introduced checks for invalid plugin version.
  2. Readme File Validation
    • New validation for the donate link in the readme file.
    • Updated checks for contributors in Markdown readme files.
    • Differentiates between a missing readme file and a default one.
  3. Code and Functionality Checks
    • Restricted parse_str() usage without a second argument.
    • Disallowed usage of HEREDOC and NOWDOC.
    • Added checks to prevent inclusion of libraries already in WordPress core.
    • Added warnings for using query_posts() in favor of WP_Query.
    • Encouraged native functions for loading images in templates.
  4. License Checks
    • Created a dedicated class for license checks.
    • Added support for the MPL-2.0 license.
    • Updated error type for license check codes.
  5. Trademark and Domain Checks
    • Updated disallowed domains for the Plugin URI field.
    • Allowed specific acronyms in trademark checks.
  6. Runtime and CLI Enhancements
    • Added an option in the CLI to include low-severity errors and warnings.
    • Fixed runtime environment setup order in the CLI.
    • Allowed custom checks to provide installed paths.
  7. Severity Updates
    • Increased severity for:
      • Incorrect Plugin Requires values.
      • Code obfuscation.
  8. Miscellaneous
    • Improved handling of localhost URLs.
    • Updated table prefix usage for runtime check requests.
    • Implemented a Gherkin linter in GitHub actions.
    • Documented plugin checks for better clarity.

Fixes

  1. Runtime and Addon Checks
    • Fixed issues with local environment setup before testing.
    • Ensured addon checks execute correctly during runtime checks.
  2. Validation Fixes
    • Allowed default as a text domain in text domain checks.
    • Accepted GitHub URLs in the Plugin URI field.
    • Corrected a false flag for the Apache license in the WordPress.org plugin repository.
  3. File Path Issues
    • Resolved problems caused by poorly named files by removing the path before the plugin.

This release focuses on enhancing code quality, improving validation, and providing better developer tools and documentation.

More info in Plugin Check Plugin WordPress Page and GitHub Page release.

Leave a Comment

ÚLTIMOS ARTÍCULOS

Cierre Ventana

A great year on the WordPress plugin team

It’s been a great year for the WordPress Plugins Team. You can see the numbers in a summary…

Cierre Ventana

Develop more secure WordPress Plugins

Introduction Plugin Check Plugin is the new tool available to everyone that allows you to do automatic reviews…

Cierre Ventana

Create your own WordPress plugin, from scratch or already knowing some

Speakers: Francisco Torres, Paco Marchante and myself, David Pérez. We had the opportunity to be at WordCamp Madrid…

Logo David
Privacy Resume

Esta web utiliza cookies para que podamos ofrecerte la mejor experiencia de usuario posible. La información de las cookies se almacena en tu navegador y realiza funciones tales como reconocerte cuando vuelves a nuestra web o ayudar a nuestro equipo a comprender qué secciones de la web encuentras más interesantes y útiles.Para más información consulta nuestra <a href="/politica-privacidad/">Política de Privacidad</a>