WordPress.org

Yorùbá

Wa WordPress jáde
WordPress.org

Plugin Directory

Plugin Check (PCP)

Plugin Check (PCP)

Láti ọwọ́ WordPress.org
Ṣe ìgbàsílẹ̀
Àkọ́kọ́wò Láaye

Àpèjúwe

Plugin Check is a tool for testing whether your plugin meets the required standards for the WordPress.org plugin directory. With this plugin you will be able to run most of the checks used for new submissions, and check if your plugin meets the requirements.

Additionally, the tool flags violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices.

The checks can be run either using the WP Admin user interface or WP-CLI:

  • To check a plugin using WP Admin, please navigate to the Tools > Plugin Check menu. You need to be able to manage plugins on your site in order to access that screen.
  • To check a plugin using WP-CLI, please use the wp plugin check command. For example, to check the “Hello Dolly” plugin: wp plugin check hello.php
    • Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the --require argument of WP-CLI, to manually load the cli.php file within the plugin checker directory before WordPress is loaded. For example: wp plugin check hello.php --require=./wp-content/plugins/plugin-check/cli.php
    • You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL: wp plugin check https://example.com/plugin.zip or to check a plugin from a path: wp plugin check /path/to/plugin

The checks are grouped into several categories, so that you can customize which kinds of checks you would like to run on a plugin.

Keep in mind that this plugin is not a replacement for the manual review process, but it will help you speed up the process of getting your plugin approved for the WordPress.org plugin repository, and it will also help you avoid some common mistakes.

Even if you do not intend to host your plugin in the WordPress.org directory, you are encouraged to use Plugin Check so that your plugin follows the base requirements and best practices for WordPress plugins.

Plugin Namer Tool

Plugin Check now includes an AI-powered Plugin Namer tool (accessible via Tools > Plugin Check Namer) that helps plugin authors evaluate plugin names before submission. This tool checks for:

  • Similarity to existing plugins in the WordPress.org directory
  • Potential trademark conflicts with well-known brands
  • Compliance with WordPress plugin naming guidelines
  • Generic or overly broad naming issues

The Plugin Namer provides instant feedback with actionable suggestions, helping you choose a clear, unique, and policy-compliant name that stands out in the plugin directory. This feature requires WordPress 7.0+ and configured AI connectors.

Important: The Plugin Namer tool provides guidance only and is not definitive. All plugin name decisions are subject to final review and approval by the WordPress.org Plugins team reviewers.

Checks reviewed by AI

When AI analysis is enabled, Plugin Check can review selected results to help identify likely false positives. Related issues are grouped and analyzed with prompts tailored to the type of check, using the surrounding code as context. The AI review does not remove or change the original results, but adds an additional summary that highlights which findings may need human review before taking action.

Ìgbéwọlẹ̀

Installation from within WordPress

  1. Visit Plugins > Add New.
  2. Search for Plugin Check.
  3. Install and activate the Plugin Check plugin.

Manual installation

  1. Upload the entire plugin-check folder to the /wp-content/plugins/ directory.
  2. Visit Plugins.
  3. Activate the Plugin Check plugin.

FAQ

Where can I contribute to the plugin?

All development for this plugin is handled via GitHub any issues or pull requests should be posted there.

What if the plugin reports something thatÌtumọ̀ Yorùbá: ’s correct as an “error” or “warning”?

We strive to write a plugin in a way that minimizes false positives but if you find one, please report it in the GitHub repo. For certain false positives, such as those detected by PHPCodeSniffer, you may be able to annotate the code to ignore the specific problem for a specific line.

Why does it flag something as bad?

ItÌtumọ̀ Yorùbá: ’s not flagging “bad” things, as such. Plugin Check is designed to be a non-perfect way to test for compliance with the Plugin Review guidelines, as well as additional plugin development best practices in accessibility, performance, security and other areas. Not all plugins must adhere to these guidelines. The purpose of the checking tool is to ensure that plugins uploaded to the central WordPress.org plugin repository meet the latest standards of WordPress plugin and will work on a wide variety of sites.

Many sites use custom plugins, and thatÌtumọ̀ Yorùbá: ’s perfectly okay. But plugins that are intended for use on many different kinds of sites by the public need to have a certain minimum level of capabilities, in order to ensure proper functioning in many different environments. The Plugin Review guidelines are created with that goal in mind.

This plugin checker is not perfect, and never will be. It is only a tool to help plugin authors, or anybody else who wants to make their plugin more capable. All plugins submitted to WordPress.org are hand-reviewed by a team of experts. The automated plugin checker is meant to be a useful tool only, not an absolute system of measurement.

Does a plugin need to pass all checks to be approved in the WordPress.org plugin directory?

To be approved in the WordPress.org plugin directory, a plugin must typically pass all checks in the “Plugin repo” category. Other checks are additional and may not be required to pass.

In any case, passing the checks in this tool likely helps to achieve a smooth plugin review process, but is no guarantee that a plugin will be approved in the WordPress.org plugin directory.

Àwọn àgbéyẹ̀wò

Just what I needed

Òkúdù 25, 2026
As a developer of Plugins, this plugin is perfect for helping me not only to comply with WordPress standards, but also to code better. I have no doubt that every developer will agree that this is a very useful plugin for coding.

Great for checking your work

Òkúdù 23, 2026 1 ìdáhùn
Why not use it? IÌtumọ̀ Yorùbá: ’ve written multiple custom plugins for my site, and I like that I can double-check my work with this plugin. In the rush to come up with my own plugin solutions, I often miss things. This plugin helps me remember to cover the basic best practices of plugin authoring, especially security. Even if there were false-positives, they can always be ignored.

Very useful tool

Èbìbí 16, 2026
Plugin Check has been really helpful for improving my plugin before publishing updates on WordPress.org. The new option to download the issues as an Excel file is very useful and makes it much easier to review and fix everything step by step. Thanks to the team for this great tool. I hope future updates add even easier options to make the workflow faster and smoother.

False positives

Ẹrẹ́nà 19, 2026 1 ìdáhùn
The plugin review started with false positives and was not accurate.

Must have

Èrèlé 3, 2026
Useful tool for catching issues early. If youÌtumọ̀ Yorùbá: ’re serious about plugin development, this is a must-have.

Very helpful

Ṣẹrẹ 29, 2026
Great tool to help finding issues with your plugin. The only thing I would like to see as a button that allows you to ignore certain messages, or mark them as fixed. So if you re-scan, it is easier to see, what still needs to be done. Also helpful would be a better indicator how serious a issue is. I know there are Errors and Warnings, but maybe with a score? And “Error” in red and “Warning” in orange for better accessibility.
Ka gbogbo àwọn àgbéyẹ̀wò 35

Àwọn Olùkópa & Olùgbéejáde

“Plugin Check (PCP)” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

A ti túmọ̀ “Plugin Check (PCP)” sí àwọn èdè agbègbè 16. Ọpẹ́lọpẹ́ fún àwọn atúmọ̀ èdè fún àwọn ìkópa wọn.

Túmọ̀ “Plugin Check (PCP)” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

2.0.0

  • Enhancement Ìtumọ̀ Yorùbá: – Add WordPress functions compatibility check to flag usage of functions unavailable in a pluginÌtumọ̀ Yorùbá: ’s declared minimum WordPress version.
  • Enhancement Ìtumọ̀ Yorùbá: – Add Write File check to detect plugins saving data in the plugin folder instead of the uploads directory or database.
  • Enhancement Ìtumọ̀ Yorùbá: – Add batched AI false positive detection with check-specific prompts and AI model selection for WP-CLI.
  • Enhancement Ìtumọ̀ Yorùbá: – Add CTRF export support for check results.
  • Enhancement Ìtumọ̀ Yorùbá: – Add an error count summary to the Plugin Check UI.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve Direct File Access detection for library-style files.
  • Enhancement Ìtumọ̀ Yorùbá: – Adjust checks for update mode.
  • Fix Ìtumọ̀ Yorùbá: – Relax Update URI header validation for WordPress.org plugin URLs.
  • Fix Ìtumọ̀ Yorùbá: – Improve WordPress functions compatibility detection to avoid PHP serialization false positives.
  • Fix Ìtumọ̀ Yorùbá: – Respect wp_supports_ai() and text-capable model filtering in the Plugin Namer.
  • Fix Ìtumọ̀ Yorùbá: – Show Plugin Namer token usage in results.
  • Fix Ìtumọ̀ Yorùbá: – Recognize EUPL as a GPL-compatible license.
  • Fix Ìtumọ̀ Yorùbá: – Improve internationalization for emoji-prefixed labels.
  • Fix Ìtumọ̀ Yorùbá: – Update PHPCS sniffer repository links.
  • Tweak Ìtumọ̀ Yorùbá: – Update WP-CLI runtime checks documentation.
  • Chore Ìtumọ̀ Yorùbá: – Add automated WordPress function compatibility data generation.
  • Chore Ìtumọ̀ Yorùbá: – Add AI usage disclosure to the pull request template.
  • Chore Ìtumọ̀ Yorùbá: – Add AI coding agent instructions.
  • Chore Ìtumọ̀ Yorùbá: – Clean up wp-env development and test configuration warnings.
  • Chore Ìtumọ̀ Yorùbá: – Show a WordPress Playground preview button on pull requests.
  • Chore Ìtumọ̀ Yorùbá: – Update development and CI dependencies.

1.9.0

  • Enhancement Ìtumọ̀ Yorùbá: – Use the WordPress 7.0 core AI connectors.
  • Enhancement Ìtumọ̀ Yorùbá: – Add External Admin Menu Links check to detect external URLs in top-level admin menus.
  • Enhancement Ìtumọ̀ Yorùbá: – Add and refine the block metadata compatibility check to require apiVersion 3+ for WordPress 7.0+ iframe editor compatibility, including adjusted severity by mode.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve Plugin Updater detection to identify Plugin Update Checker (PUC) calls.
  • Enhancement Ìtumọ̀ Yorùbá: – Accept WTFPL as a GPL-compatible license.
  • Fix Ìtumọ̀ Yorùbá: – Improve PayPal donation URL validation for complex query strings.
  • Fix Ìtumọ̀ Yorùbá: – Ensure AI Check uses the configured model preference.
  • Fix Ìtumọ̀ Yorùbá: – Show a clear Plugin Namer error message when AI connector status is unavailable.
  • Fix Ìtumọ̀ Yorùbá: – Update the Plugin Namer connector settings page link.
  • Tweak Ìtumọ̀ Yorùbá: – Convert the load_plugin_textdomain() check from error to warning severity.
  • Fix Ìtumọ̀ Yorùbá: – Improve readme contributors validation when trailing commas are present.
  • Fix Ìtumọ̀ Yorùbá: – Make markdown file checks case-insensitive.
  • Tweak Ìtumọ̀ Yorùbá: – Refine escaping sniff error messages for clearer guidance.
  • Chore Ìtumọ̀ Yorùbá: – Update development dependencies, including @wordpress/scripts, simple-git, basic-ftp, svgo, immutable, and @wp-playground/cli.
  • Tweak Ìtumọ̀ Yorùbá: – Update WordPress.org Plugins Team naming for consistency.

1.8.0

  • Enhancement Ìtumọ̀ Yorùbá: – Add AI-powered Plugin Namer tool to evaluate plugin names for trademark conflicts and naming best practices.
  • Enhancement Ìtumọ̀ Yorùbá: – Add AI Instructions Detection Check to identify AI tool configuration files and development-only directories.
  • Enhancement Ìtumọ̀ Yorùbá: – Add support for exporting check results in CSV, JSON, and Markdown formats.
  • Enhancement Ìtumọ̀ Yorùbá: – Add check type filter to allow filtering results by errors and warnings.
  • Enhancement Ìtumọ̀ Yorùbá: – Add Direct File Access check to ensure proper security validation with ABSPATH constant.
  • Enhancement Ìtumọ̀ Yorùbá: – Add check for mismatched “Tested up to” header between plugin header and readme.txt.
  • Enhancement Ìtumọ̀ Yorùbá: – Update trademark check to remove acronym exceptions and improve flexibility.
  • Enhancement Ìtumọ̀ Yorùbá: – Add heredoc sniff to detect and restrict heredoc usage (nowdoc allowed).
  • Fix Ìtumọ̀ Yorùbá: – Update Playground integration blueprint for compatibility.
  • Fix Ìtumọ̀ Yorùbá: – Force correct plugin slug detection in WP-CLI command.

1.7.0

  • Enhancement Ìtumọ̀ Yorùbá: – Add Minified File Detection Check to identify and handle minified files in plugins.
  • Enhancement Ìtumọ̀ Yorùbá: – Implement check for insecure use of wp_verify_nonce() to improve security validation.
  • Enhancement Ìtumọ̀ Yorùbá: – Add direct database query sniff to detect direct database calls without using WordPress functions.
  • Enhancement Ìtumọ̀ Yorùbá: – Add prefixing check to ensure proper function and class name prefixing.
  • Enhancement Ìtumọ̀ Yorùbá: – Update localhost sniff regex to improve detection of localhost URLs including *.local domains.
  • Enhancement Ìtumọ̀ Yorùbá: – Disallow runtime checks when custom user table constants are defined for better compatibility.
  • Enhancement Ìtumọ̀ Yorùbá: – Add forbidden functions check to detect usage of disallowed PHP functions.
  • Enhancement Ìtumọ̀ Yorùbá: – New check for wp_safe_redirect to encourage use of WordPress safe redirect function.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve mismatched text domain check for better internationalization validation.
  • Enhancement Ìtumọ̀ Yorùbá: – Detect links that request five-star reviews to enforce plugin directory guidelines.
  • Enhancement Ìtumọ̀ Yorùbá: – Add The Unlicense to GPL-compatible license check.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve localhost sniff code for more accurate detection.
  • Fix Ìtumọ̀ Yorùbá: – Ignore vendor_prefixed and vendor-prefixed folders in checks to prevent false positives.
  • Fix Ìtumọ̀ Yorùbá: – Handle possible empty element in scanner to prevent PHP warnings.
  • Fix Ìtumọ̀ Yorùbá: – Hide error output in scanner for cleaner output.
  • Fix Ìtumọ̀ Yorùbá: – Call ReflectionProperty::setAccessible() only in older PHP versions for better PHP 8.1+ compatibility.
  • Fix Ìtumọ̀ Yorùbá: – Prevent deletion of custom WordPress tables during cleanup in test environment.

1.6.0

  • Enhancement Ìtumọ̀ Yorùbá: – Support strict output format for CLI commands.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve check for donate link in readme.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve info check in Version utils.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve URL validation for plugin header fields.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve ruleset files.
  • Enhancement Ìtumọ̀ Yorùbá: – Increased severity for invalid plugin uri domain and plugin description checks in plugin header.
  • Enhancement Ìtumọ̀ Yorùbá: – Remove CallTimePassByReference as itÌtumọ̀ Yorùbá: ’s deprecated rule.
  • Enhancement Ìtumọ̀ Yorùbá: – Disallow special characters in textdomain.
  • Enhancement Ìtumọ̀ Yorùbá: – Imported readme parser for preventing conflicts with wordpress.org. Use dotorg readme parser if available.
  • Enhancement Ìtumọ̀ Yorùbá: – Discourage the use of load_plugin_textdomain found in plugins as itÌtumọ̀ Yorùbá: ’s not necessary in wordpress.org.
  • Enhancement Ìtumọ̀ Yorùbá: – Upgrade severity for missing readme headers.
  • Enhancement Ìtumọ̀ Yorùbá: – Show tested up to minor check only when it is current major version.
  • Enhancement Ìtumọ̀ Yorùbá: – Added link in plugins page to run the plugin check.
  • Fix Ìtumọ̀ Yorùbá: – Dynamic WP Content folder.
  • Fix Ìtumọ̀ Yorùbá: – Fix test for special chars in file names giving problems to users after clone.
  • Fix Ìtumọ̀ Yorùbá: – Remove Image_Functions_Check as they were making false positives.
  • Fix Ìtumọ̀ Yorùbá: – Prevent WordPress version 10+ from being flagged as an error in the “Tested up to” check.

1.5.0

  • Enhancement Ìtumọ̀ Yorùbá: – Improve url validation to check duplicate protocol.
  • Enhancement Ìtumọ̀ Yorùbá: – Update severity for incorrect textdomains and i18n error codes.
  • Enhancement Ìtumọ̀ Yorùbá: – Now issues in URL Author check are ERROR instead of WARNING.
  • Enhancement Ìtumọ̀ Yorùbá: – New check for minor version in Tested up.
  • Enhancement Ìtumọ̀ Yorùbá: – Make sure headers are not empty in the requires header check.
  • Enhancement Ìtumọ̀ Yorùbá: – Include experimental option in admin.
  • Enhancement Ìtumọ̀ Yorùbá: – Add Behat test for experimental checks from addons.
  • Enhancement Ìtumọ̀ Yorùbá: – Improve license check for Apache.
  • Enhancement Ìtumọ̀ Yorùbá: – Warn if requires headers are not same in readme and plugin header.
  • Fix Ìtumọ̀ Yorùbá: – Remove warning for dynamic callback in register_setting check.
  • Fix Ìtumọ̀ Yorùbá: – Incorrect database tables being referenced on subsites in Multisite.

1.4.0

  • Enhancement Ìtumọ̀ Yorùbá: – Allow ISC license in the License check.
  • Enhancement Ìtumọ̀ Yorùbá: – Added check for use of settings with sanitization callback.
  • Enhancement Ìtumọ̀ Yorùbá: – Added Ìtumọ̀ Yorùbá: –ignore-codes in CLI to introduce a mechanism to ignore specific error codes.
  • Enhancement Ìtumọ̀ Yorùbá: – New utils for fetching necessary version info details.
  • Enhancement Ìtumọ̀ Yorùbá: – Added check for unsupported plugin name in plugin header field.
  • Enhancement Ìtumọ̀ Yorùbá: – Segregate the severity of i18n checks. Make sure that is giving errors in the right context.
  • Enhancement Ìtumọ̀ Yorùbá: – Provide more detailed information about checks when the README does not include a tested version or a list of contributors.
  • Enhancement Ìtumọ̀ Yorùbá: – Added rules from WPCS to prevent issues with content being sent before headers and warn about the use of Call-time pass-by-reference.
  • Enhancement Ìtumọ̀ Yorùbá: – Give more context in the error of check wrong named files.
  • Enhancement Ìtumọ̀ Yorùbá: – Simplified PHPUnit setup. Now it does not depend of running inside a WordPress installation.
  • Enhancement Ìtumọ̀ Yorùbá: – Added new check for restricted contributors.
  • Fix Ìtumọ̀ Yorùbá: – Delete transients in unit tests to avoid false positives.
  • Fix Ìtumọ̀ Yorùbá: – Incorrect Tested up to version comparison will make error for two major versions up.
  • Fix Ìtumọ̀ Yorùbá: – Excluded the use of functions file_get_contents and file_put_contents in the check to prevent false positives.
  • Fix Ìtumọ̀ Yorùbá: – Duplicated error message in the check for wrong named files.
  • Fix Ìtumọ̀ Yorùbá: – Use of Json encode wasnÌtumọ̀ Yorùbá: ’t firing the error message.
  • Fix Ìtumọ̀ Yorùbá: – Change error type of NonEnqueuedImage in ImageFunctions sniff from ERROR to WARNING.

1.3.1

  • Enhancement Ìtumọ̀ Yorùbá: – Add version utilities.
  • Fix Ìtumọ̀ Yorùbá: – Escape error messages.
  • Fix Ìtumọ̀ Yorùbá: – Renamed error type to ERROR_LOW_SEVERITY and WARNING_LOW_SEVERITY.
  • Fix Ìtumọ̀ Yorùbá: – Fix PHPCS checks on unwritable filesystems.

1.3.0

  • Enhancement Ìtumọ̀ Yorùbá: – Update disallowed domains for Plugin URI check.
  • Enhancement Ìtumọ̀ Yorùbá: – Added new checks for Plugin Header fields: missing plugin description, missing plugin version and invalid plugin version.
  • Enhancement Ìtumọ̀ Yorùbá: – New check for validation of donate link in the readme file.
  • Enhancement Ìtumọ̀ Yorùbá: – Increased severity for wrong Plugin Requires.
  • Enhancement Ìtumọ̀ Yorùbá: – Added check Restrict parse_str() without second argument.
  • Enhancement Ìtumọ̀ Yorùbá: – New check for Disallow usage of HEREDOC and NOWDOC.
  • Enhancement Ìtumọ̀ Yorùbá: – Added acronyms allowed in Trademark checks.
  • Enhancement Ìtumọ̀ Yorùbá: – Added option in CLI to add low severity errors and warnings.
  • Enhancement Ìtumọ̀ Yorùbá: – Change error type for License check error codes.
  • Enhancement Ìtumọ̀ Yorùbá: – Always use prefixed tables during runtime check requests.
  • Enhancement Ìtumọ̀ Yorùbá: – Created a new class for checking licenses.
  • Enhancement Ìtumọ̀ Yorùbá: – Added support for MPL-2.0 license.
  • Enhancement Ìtumọ̀ Yorùbá: – Implement gherkin linter in GH action.
  • Enhancement Ìtumọ̀ Yorùbá: – Update check for Contributors in markdown readme files.
  • Enhancement Ìtumọ̀ Yorùbá: – CLI: Fix confusing runtime environment setup order.
  • Enhancement Ìtumọ̀ Yorùbá: – Allow custom checks to provide installed_paths.
  • Enhancement Ìtumọ̀ Yorùbá: – Improved the use of localhost URLs in the Plugin.
  • Enhancement Ìtumọ̀ Yorùbá: – Documented checks in the plugin.
  • Enhancement Ìtumọ̀ Yorùbá: – Increased severity for Code obfuscation checks.
  • Enhancement Ìtumọ̀ Yorùbá: – Differentiate between non-existent readme and default readme file.
  • Enhancement Ìtumọ̀ Yorùbá: – Encourage developers to use native functions for loading images in templates.
  • Enhancement Ìtumọ̀ Yorùbá: – Added a check for not allowing include libraries already in WordPress core.
  • Enhancement Ìtumọ̀ Yorùbá: – Warning for usage of query_posts() in favor of WP_Query.
  • Fix Ìtumọ̀ Yorùbá: – Fix for the local environment is set up before testing.
  • Fix Ìtumọ̀ Yorùbá: – Fix addon checks not being executed when running runtime checks.
  • Fix Ìtumọ̀ Yorùbá: – Allow default as a text domain in the text domain check.
  • Fix Ìtumọ̀ Yorùbá: – Allow GitHub URLs in the Plugin URI field.
  • Fix Ìtumọ̀ Yorùbá: – DonÌtumọ̀ Yorùbá: ’t flag Apache license. ItÌtumọ̀ Yorùbá: ’s allowed in the WordPress.org plugin repository.
  • Fix Ìtumọ̀ Yorùbá: – Removes the path before the plugin, so it wonÌtumọ̀ Yorùbá: ’t affect to badly named files.

1.2.0

  • Enhancement Ìtumọ̀ Yorùbá: – Added a check for badly used names in files.
  • Enhancement Ìtumọ̀ Yorùbá: – Increased severity for BacktickOperator, DisallowShortOpenTag, DisallowAlternativePHPTags, RestrictedClasses, and RestrictedFunctions.
  • Enhancement Ìtumọ̀ Yorùbá: – Added security checks to the Plugin repository category.
  • Enhancement Ìtumọ̀ Yorùbá: – Allowed runtime-set in code sniffer checks.
  • Enhancement Ìtumọ̀ Yorùbá: – Changed warnings to errors in plugin header checks.
  • Enhancement Ìtumọ̀ Yorùbá: – Detect forbidden plugin headers such as repository URIs in the Directory.
  • Enhancement Ìtumọ̀ Yorùbá: – Added a new check for development functions that are not allowed in final plugins.
  • Enhancement Ìtumọ̀ Yorùbá: – Created new images and icons for the plugin.
  • Enhancement Ìtumọ̀ Yorùbá: – Introduced a slug argument in the CLI.
  • Enhancement Ìtumọ̀ Yorùbá: – Added a check for discouraged PHP functions.
  • Enhancement Ìtumọ̀ Yorùbá: – Added validation for Contributors in the readme file.
  • Enhancement Ìtumọ̀ Yorùbá: – Added a warning for mismatched plugin names in the plugin header and readme file.
  • Enhancement Ìtumọ̀ Yorùbá: – Checked for validation of Plugin Header fields: Name, Plugin URI, Description, Author URI, Requires at least, Requires PHP, and Requires Plugins.
  • Enhancement Ìtumọ̀ Yorùbá: – Added a warning if the “Tested up to” value in the readme file exceeds the released version of WordPress.
  • Fix Ìtumọ̀ Yorùbá: – Display a success message if no errors or warnings are found.
  • Fix Ìtumọ̀ Yorùbá: – Made table results responsive.
  • Fix Ìtumọ̀ Yorùbá: – Prevent proceeding to the next check if the Stable Tag value is set to trunk.
  • Fix Ìtumọ̀ Yorùbá: – Allow runtime initialization even when only add-on checks are requested.
  • Fix Ìtumọ̀ Yorùbá: – Fixed an SPDX warning for the GPL version 3 license.
  • Fix Ìtumọ̀ Yorùbá: – Prevent runtime checks in the CLI context when they cannot be used.

1.1.0

  • Feature Ìtumọ̀ Yorùbá: – New Non_Blocking_Scripts_Check (non_blocking_scripts) runtime check to warn about enqueued scripts that use neither defer nor async.
  • Enhancement Ìtumọ̀ Yorùbá: – Changed the namespace of included checks.
  • Enhancement Ìtumọ̀ Yorùbá: – Introduced severity levels for all errors and warnings.
  • Enhancement Ìtumọ̀ Yorùbá: – CLI: Support checking a plugin from a path or URL.
  • Enhancement Ìtumọ̀ Yorùbá: – Added short descriptions and URLs for each check.
  • Enhancement Ìtumọ̀ Yorùbá: – Improved messaging in check results.
  • Enhancement Ìtumọ̀ Yorùbá: – Updated code obfuscation check with more accurate results.
  • Enhancement Ìtumọ̀ Yorùbá: – Updated plugin review check to flag missing input sanitization (WordPress.Security.ValidatedSanitizedInput).
  • Fix Ìtumọ̀ Yorùbá: – Improve readme checks to exclude invalid files.
  • Fix Ìtumọ̀ Yorùbá: – Only show edit link if files are actually editable.

1.0.2

  • Feature Ìtumọ̀ Yorùbá: – New Enqueued_Scripts_Scope_Check (enqueued_scripts_scope), Enqueued_Styles_Size_Check (enqueued_styles_size) and Enqueued_Resources_Check (enqueued_resources) performance checks.
  • Enhancement Ìtumọ̀ Yorùbá: – Improved readme check and added a new wp_plugin_check_ignored_readme_warnings filter.
  • Enhancement Ìtumọ̀ Yorùbá: – New wp_plugin_check_default_categories filter to change the categories which are selected by default.
  • Enhancement Ìtumọ̀ Yorùbá: – New wp_plugin_check_ignore_files filter to allow ignoring specific files.
  • Fix Ìtumọ̀ Yorùbá: – Correct detection of readme files in Windows by normalizing file paths.

1.0.1

  • Fix Ìtumọ̀ Yorùbá: – Add missing test-content folder needed for runtime checks.
  • Fix Ìtumọ̀ Yorùbá: – Do not send emails when setting up test environment.
  • Fix Ìtumọ̀ Yorùbá: – Prevent PHP warning when the argv variable isnÌtumọ̀ Yorùbá: ’t set.

1.0.0

  • Feature Ìtumọ̀ Yorùbá: – Complete overhaul of the plugin, its architecture, and all checks.
  • Feature Ìtumọ̀ Yorùbá: – Added new WP-CLI commands for running checks and listing available options.
  • Enhancement Ìtumọ̀ Yorùbá: – Added option to only run checks for a specific category.

0.2.3

  • Tweak Ìtumọ̀ Yorùbá: – Use version 3.8.0 of the PHP_CodeSniffer library, moving away from squizlabs/PHP_CodeSniffer to use PHPCSStandards/PHP_CodeSniffer.
  • Fix Ìtumọ̀ Yorùbá: – Ensure the plugin works as expected on the WP playground environment to enable reviewers to use PCP. Props @tellyworth.
  • Fix Ìtumọ̀ Yorùbá: – Undefined array key “argv” when running the plugin check in certain environments. Props @afragen. #340

0.2.2

  • Enhancement Ìtumọ̀ Yorùbá: – Include support for Windows Servers.
  • Enhancement Ìtumọ̀ Yorùbá: – Avoid using PHP CLI directly, which enables plugin developers to use PCP in a variety of new environments.
  • Fix Ìtumọ̀ Yorùbá: – Remove dependency on shell_exec and exec functions, which enables plugin developers to use PCP in a variety of new environments.
  • Fix Ìtumọ̀ Yorùbá: – Prevent problems with Readme parser warning related to contributor_ignored for when running the check outside WP.org. Props @dev4press. #276
  • Fix Ìtumọ̀ Yorùbá: – Remove extra period on the end of the sentence for Phar warning. Props @pixolin. #275

0.2.1

  • Added Ìtumọ̀ Yorùbá: – ‘View in code editor’ link beneath each PHPCS error or warning. Props @EvanHerman, @westonruter, @felixarntz, @mukeshpanchal27 #262
  • Fix Ìtumọ̀ Yorùbá: – Ensure readme.txt has priority over readme.md when both are present. Props @bordoni, @afragen #258
  • Fix Ìtumọ̀ Yorùbá: – Ensure that the PHPCS check runs even when the PHPCS binary is not executable. Props @bordoni, @shawn-digitalpoint, @mrfoxtalbot #254
  • Fix Ìtumọ̀ Yorùbá: – Readme changes and typos. Props @aaronjorbin. #261
  • Fix Ìtumọ̀ Yorùbá: – Long lines of code with PHPCS check no longer expand over the size of the notice. Props @bordoni, @felixarntz. #263
  • Fix Ìtumọ̀ Yorùbá: – Ensure that we have PHP 7.2 compatibility remove trailing comma. Props @bordoni, @leoloso. #265
  • Fix Ìtumọ̀ Yorùbá: – Include all strings that were missed in the previous release. Props @bordoni, @pixolin. #270

0.2.0

  • Feature Ìtumọ̀ Yorùbá: – Enable modification of the PHP Binary path used by the plugin with PLUGIN_CHECK_PHP_BIN constant.
  • Feature Ìtumọ̀ Yorùbá: – Include a check for the usage of ALLOW_UNFILTERED_UPLOADS on any PHP files Ìtumọ̀ Yorùbá: – Props EvanHerman at #45
  • Feature Ìtumọ̀ Yorùbá: – Include a check for the presence of the application files (.a, .bin, .bpk, .deploy, .dist, .distz, .dmg, .dms, .DS_Store, .dump, .elc, .exe, .iso, .lha, .lrf, .lzh, .o, .obj, .phar, .pkg, .sh, ‘.so`) Ìtumọ̀ Yorùbá: – Props EvanHerman at #43
  • Feature Ìtumọ̀ Yorùbá: – Include a check for the presence of the readme.txt or readme.md file Ìtumọ̀ Yorùbá: – Props EvanHerman at #42
  • Fix Ìtumọ̀ Yorùbá: – Ensure that Readme parsing is included properly when a readme.md or readme.txt file is present. Props Bordoni #52
  • Tweak Ìtumọ̀ Yorùbá: – Disallow functions move_uploaded_file, passthru, proc_open Ìtumọ̀ Yorùbá: – Props alexsanford at #50
  • Tweak Ìtumọ̀ Yorùbá: – Change the message type for using functions WordPress already includes from Warning to Error. Props davidperezgar at #18
  • Tweak Ìtumọ̀ Yorùbá: – Change the message type for incorrect usage of Stable tag from Notice/Warning to Error. Props davidperezgar at #3

[0.1] 2011-09-04

Original version of the plugin check tool, not a released version of the plugin, this changelog is here for historical purposes only.

Plugin àwùjọ

Àwùjọ ni ó ṣe ìdàgbàsókè àti àtìlẹ́yìn fún plugin yìí. Ṣe ìkópa sí plugin yìí

Àkójọpọ̀ Meta

Àwọn ìbò

4.5 lára àwọn ìràwọ̀ 5.

Your review

See all reviews

Àwọn Olùkópa

Ìrànlọ́wọ́

Àwọn ọ̀ràn tí a yanjú ní oṣù méjì tó kọjá:

0 nínú 2

Wo àpéjọ ìrànlọ́wọ́