Title: Plugin Check (PCP) Author: WordPress.org Published: 4 de Septiembre de 2011 Last modified: 15 de Marzo de 2026 --- Buscar plugins ![](https://ps.w.org/plugin-check/assets/banner-772x250.png?rev=3166100) ![](https://ps.w.org/plugin-check/assets/icon.svg?rev=3166100) # Plugin Check (PCP) Por [WordPress.org](https://profiles.wordpress.org/wordpressdotorg/) [Descargar](https://downloads.wordpress.org/plugin/plugin-check.1.9.0.zip) [Vista previa](https://cl.wordpress.org/plugins/plugin-check/?preview=1) * [Detalles](https://cl.wordpress.org/plugins/plugin-check/#description) * [Reseñas](https://cl.wordpress.org/plugins/plugin-check/#reviews) * [Instalación](https://cl.wordpress.org/plugins/plugin-check/#installation) * [Desarrollo](https://cl.wordpress.org/plugins/plugin-check/#developers) [Soporte](https://wordpress.org/support/plugin/plugin-check/) ## Descripción Plugin Check es una herramienta para comprobar si tu plugin cumple las normas requeridas para el directorio de plugins de WordPress.org. Con este plugin podrás ejecutar la mayoría de las comprobaciones utilizadas para nuevos envíos, y comprobar si tu plugin cumple los requisitos. Además, la herramienta señala infracciones o problemas relacionados con las mejores prácticas de desarrollo de plugins, desde requisitos básicos como el uso correcto de las funciones de internacionalización hasta las mejores prácticas de accesibilidad, rendimiento y seguridad. Las comprobaciones pueden ejecutarse desde el escritorio de WordPress o mediante WP-CLI: * Para comprobar un plugin utilizando WP Admin, navega hasta el menú _Herramientas > Comprobación de plugins_. Necesitas poder gestionar plugins en tu sitio para acceder a esa pantalla. * Para comprobar un plugin mediante WP-CLI, utiliza el comando `wp plugin check`. Por ejemplo, para comprobar el plugin “Hello Dolly”: `wp plugin check hello.php` - Ten en cuenta que, por defecto, al utilizar WP-CLI solo se pueden ejecutar comprobaciones estáticas. Para incluir también comprobaciones en tiempo de ejecución, actualmente es necesaria una solución mediante el argumento `-- require` de WP-CLI, para cargar manualmente el archivo `cli.php` dentro del directorio del comprobador de plugins antes de que se cargue WordPress. Por ejemplo `wp plugin check hello.php --require=./wp-content/plugins/plugin-check/ cli.php` - Puedes utilizar una ruta o URL arbitraria para comprobar un plugin. Por ejemplo, para comprobar un plugin desde una URL: `wp plugin check https://example.com/ plugin.zip` o para comprobar un plugin desde una ruta: `comprobar plugin php/ ruta/a/plugin` Las comprobaciones se agrupan en varias categorías, para que puedas personalizar qué tipos de comprobaciones quieres ejecutar en un plugin. Ten en cuenta que este plugin aún no sustituye al proceso de revisión manual, pero te ayudará a acelerar el proceso de aprobación de tu plugin en el repositorio de plugins de WordPress.org, y también te ayudará a evitar algunos errores comunes. Aunque no tengas intención de alojar tu plugin en el directorio de WordPress.org, te animamos a que utilices Plugin Check para que tu plugin cumpla los requisitos básicos y las mejores prácticas para los plugins de WordPress. **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. ## Instalación #### Instalación desde WordPress 1. Visita **Plugins > Agregar nuevo**. 2. Busca **Plugin Check**. 3. Instala y activa el plugin Plugin Check. #### Instalación manual 1. Sube toda la carpeta `plugin-check` al directorio `/wp-content/plugins/`. 2. Visita **Plugins**. 3. Activa el plugin Plugin Check. ## FAQ ### ¿Dónde puedo contribuir al plugin? Todo el desarrollo de este plugin se lleva a cabo a través de [GitHub](https://github.com/WordPress/plugin-check/). Cualquier problema o pull request debe publicarse allí. ### ¿Y si el plugin informa de algo que es correcto como “error” o “advertencia”? Nos esforzamos por escribir un plugin de forma que minimice los falsos positivos, pero si encuentras alguno, por favor, notifícalo en el repositorio de GitHub. Para ciertos falsos positivos, como los detectados por PHPCodeSniffer, es posible que puedas anotar el código para ignorar el problema específico para una línea concreta. ### ¿Por qué marca algo como malo? No marca cosas “malas” como tales. Plugin Check está diseñado para ser una forma no perfecta de comprobar el cumplimiento de las [directrices de revisión de plugins](https://make.wordpress.org/plugins/handbook/performing-reviews/review-checklist/). No todos los plugins deben cumplir estas directrices. El propósito de la herramienta de comprobación es garantizar que los plugins subidos al [repositorio central de plugins de WordPress.org](https://wordpress.org/plugins/) cumplen los últimos estándares de plugins de WordPress y funcionarán en una amplia variedad de sitios. Muchos sitios utilizan plugins personalizados, y eso está perfectamente bien. Pero los plugins que están destinados a ser utilizados en muchos tipos diferentes de sitios por el público deben tener un cierto nivel mínimo de capacidades, para asegurar un funcionamiento adecuado en diferentes entornos. Las directrices de revisión de plugins se crean con ese objetivo en mente. Este comprobador de plugins no es perfecto y nunca lo será. Es solo una herramienta para ayudar a los autores de plugins, o a cualquier otra persona que quiera hacer que su plugin sea más capaz. Todos los plugins enviados a WordPress.org son revisados manualmente por un equipo de expertos. El comprobador de plugins automatizado está destinado a ser solo una herramienta útil, no un sistema absoluto de medición. ### ¿Es necesario que un plugin pase todas las comprobaciones para ser aprobado en el directorio de plugins de WordPress.org? Para ser aprobado en el directorio de plugins de WordPress.org, un plugin debe pasar normalmente todas las comprobaciones de la categoría “Plugin repo”. Otras comprobaciones son adicionales y puede que no sea necesario aprobarlas. En cualquier caso, pasar las comprobaciones de esta herramienta probablemente ayude a conseguir un proceso de revisión de plugins sin problemas, pero no es garantía de que un plugin sea aprobado en el directorio de plugins de WordPress.org. ## Reseñas ![](https://secure.gravatar.com/avatar/5dd481438e5ca8e135c0520aaf922a34f2a908d8d0e8b358d8563debe0b04589? s=60&d=retro&r=g) ### 󠀁[False positives](https://wordpress.org/support/topic/false-positives-36/)󠁿 [Barry](https://profiles.wordpress.org/tmgm/) 19 de Marzo de 2026 1 respuesta The plugin review started with false positives and was not accurate. ![](https://secure.gravatar.com/avatar/1db275a77ae016b63d1edc49625a6ba5d58b4f7552a272dcf3cf331e728812cc? s=60&d=retro&r=g) ### 󠀁[Must have](https://wordpress.org/support/topic/must-have-741/)󠁿 [Stachethemes](https://profiles.wordpress.org/stachethemes/) 3 de Febrero de 2026 Useful tool for catching issues early. If you’re serious about plugin development, this is a must-have. ![](https://secure.gravatar.com/avatar/a8fadf98d183bd5fb216b5ca07b5722d365e1a2412e5daa0f829c6fd11664783? s=60&d=retro&r=g) ### 󠀁[Very helpful](https://wordpress.org/support/topic/very-helpful-1572/)󠁿 [dansart](https://profiles.wordpress.org/dansart/) 29 de Enero de 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. ![](https://secure.gravatar.com/avatar/e02f782d76eb2b7113cc8477d3504e8b4aa34330634cdc34c0fff8e67c2db23b? s=60&d=retro&r=g) ### 󠀁[Amazingly useful](https://wordpress.org/support/topic/amazingly-useful-15/)󠁿 [muzKore](https://profiles.wordpress.org/muzoid/) 15 de Enero de 2026 This plugin helped me identify areas of my plugin that I thought I had taken care of. When developing my first plugin. I learned a lot through the feedback given and was able to re-run and eventually remove of all errors. On a side note, what I did discover was that a lot of the warnings were general and some were not really applicable to my plugin. It took time and research to work this out so don’t freak out if you get a heap of feedback from the plugin. Try to filter down to the errors, get them sorted and then move onto the warnings and fix what you can where applicable. Cheers. ![](https://secure.gravatar.com/avatar/7e052c1d09941b211f2012c46fcbc3610c9267358b62320c81aa11d88aac7d54? s=60&d=retro&r=g) ### 󠀁[Helpful](https://wordpress.org/support/topic/helpful-488/)󠁿 [Blucube](https://profiles.wordpress.org/edhicks/) 5 de Diciembre de 2025 1 respuesta By it’s nature this is going to flag false positives – potential issues that you’ve dealt with in different ways, or issues that don’t necessarily apply to your particular case – and it does. But it’s a really useful tool to run a quick check and uncover little omissions or improvements to be made. ![](https://secure.gravatar.com/avatar/98882bbd1717ececb0fb9acab6f8a015b9323eb670fb2f309fb1d5e5cfdb04b9? s=60&d=retro&r=g) ### 󠀁[Simple and effective tool for quick plugin checks](https://wordpress.org/support/topic/simple-and-effective-tool-for-quick-plugin-checks/)󠁿 [Mohammed Kateregga](https://profiles.wordpress.org/mohkatz/) 29 de Julio de 2025 1 respuesta Simple and effective plugin check tool, there is room for improvement and adding more functionality with AI, but overall it currently still gets the job done. [ Leer los 32 comentarios ](https://wordpress.org/support/plugin/plugin-check/reviews/) ## Colaboradores & Desarrolladores “Plugin Check (PCP)” es software de código abierto. Las siguientes personas han contribuido a este plugin. Colaboradores * [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/) “Plugin Check (PCP)” ha sido traducido en 15 idiomas. Gracias a [los traductores](https://translate.wordpress.org/projects/wp-plugins/plugin-check/contributors) por sus contribuciones. [Traduce “Plugin Check (PCP)” a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/plugin-check) ### ¿Interesado en el desarrollo? [Revisa el código](https://plugins.trac.wordpress.org/browser/plugin-check/), echa un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/plugin-check/), o suscríbete al [registro de desarrollo](https://plugins.trac.wordpress.org/log/plugin-check/) por [RSS](https://plugins.trac.wordpress.org/log/plugin-check/?limit=100&mode=stop_on_copy&format=rss). ## Historial de cambios #### 1.9.0 * Enhancement – Use the WordPress 7.0 core AI connectors. * Enhancement – Add External Admin Menu Links check to detect external URLs in top-level admin menus. * Enhancement – 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 – Improve Plugin Updater detection to identify Plugin Update Checker( PUC) calls. * Enhancement – Accept WTFPL as a GPL-compatible license. * Fix – Improve PayPal donation URL validation for complex query strings. * Fix – Ensure AI Check uses the configured model preference. * Fix – Show a clear Plugin Namer error message when AI connector status is unavailable. * Fix – Update the Plugin Namer connector settings page link. * Tweak – Convert the `load_plugin_textdomain()` check from error to warning severity. * Fix – Improve readme contributors validation when trailing commas are present. * Fix – Make markdown file checks case-insensitive. * Tweak – Refine escaping sniff error messages for clearer guidance. * Chore – Update development dependencies, including `@wordpress/scripts`, `simple- git`, `basic-ftp`, `svgo`, `immutable`, and `@wp-playground/cli`. * Tweak – Update WordPress.org Plugins Team naming for consistency. #### 1.8.0 * Enhancement – Add AI-powered Plugin Namer tool to evaluate plugin names for trademark conflicts and naming best practices. * Enhancement – Add AI Instructions Detection Check to identify AI tool configuration files and development-only directories. * Enhancement – Add support for exporting check results in CSV, JSON, and Markdown formats. * Enhancement – Add check type filter to allow filtering results by errors and warnings. * Enhancement – Add Direct File Access check to ensure proper security validation with ABSPATH constant. * Enhancement – Add check for mismatched “Tested up to” header between plugin header and readme.txt. * Enhancement – Update trademark check to remove acronym exceptions and improve flexibility. * Enhancement – Add heredoc sniff to detect and restrict heredoc usage (nowdoc allowed). * Fix – Update Playground integration blueprint for compatibility. * Fix – Force correct plugin slug detection in WP-CLI command. #### 1.7.0 * Enhancement – Add Minified File Detection Check to identify and handle minified files in plugins. * Enhancement – Implement check for insecure use of wp_verify_nonce() to improve security validation. * Enhancement – Add direct database query sniff to detect direct database calls without using WordPress functions. * Enhancement – Add prefixing check to ensure proper function and class name prefixing. * Enhancement – Update localhost sniff regex to improve detection of localhost URLs including *.local domains. * Enhancement – Disallow runtime checks when custom user table constants are defined for better compatibility. * Enhancement – Add forbidden functions check to detect usage of disallowed PHP functions. * Enhancement – New check for wp_safe_redirect to encourage use of WordPress safe redirect function. * Enhancement – Improve mismatched text domain check for better internationalization validation. * Enhancement – Detect links that request five-star reviews to enforce plugin directory guidelines. * Enhancement – Add The Unlicense to GPL-compatible license check. * Enhancement – Improve localhost sniff code for more accurate detection. * Fix – Ignore vendor_prefixed and vendor-prefixed folders in checks to prevent false positives. * Fix – Handle possible empty element in scanner to prevent PHP warnings. * Fix – Hide error output in scanner for cleaner output. * Fix – Call ReflectionProperty::setAccessible() only in older PHP versions for better PHP 8.1+ compatibility. * Fix – Prevent deletion of custom WordPress tables during cleanup in test environment. #### 1.6.0 * Enhancement – Support strict output format for CLI commands. * Enhancement – Improve check for donate link in readme. * Enhancement – Improve info check in Version utils. * Enhancement – Improve URL validation for plugin header fields. * Enhancement – Improve ruleset files. * Enhancement – Increased severity for invalid plugin uri domain and plugin description checks in plugin header. * Enhancement – Remove CallTimePassByReference as it’s deprecated rule. * Enhancement – Disallow special characters in textdomain. * Enhancement – Imported readme parser for preventing conflicts with wordpress. org. Use dotorg readme parser if available. * Enhancement – Discourage the use of `load_plugin_textdomain` found in plugins as it’s not necessary in wordpress.org. * Enhancement – Upgrade severity for missing readme headers. * Enhancement – Show tested up to minor check only when it is current major version. * Enhancement – Added link in plugins page to run the plugin check. * Fix – Dynamic WP Content folder. * Fix – Fix test for special chars in file names giving problems to users after clone. * Fix – Remove Image_Functions_Check as they were making false positives. * Fix – Prevent WordPress version 10+ from being flagged as an error in the “Tested up to” check. #### 1.5.0 * Enhancement – Improve url validation to check duplicate protocol. * Enhancement – Update severity for incorrect textdomains and i18n error codes. * Enhancement – Now issues in URL Author check are ERROR instead of WARNING. * Enhancement – New check for minor version in Tested up. * Enhancement – Make sure headers are not empty in the requires header check. * Mejora – Incluir opción experimental en admin. * Mejora – Agregar prueba Behat para comprobaciones experimentales de complementos. * Mejora – Mejorar la comprobación de licencia para Apache. * Mejora – Avisar si las cabeceras requeridas no son las mismas en el readme y en la cabecera del plugin. * Corrección – Eliminar la advertencia de devolución de llamada dinámica en la comprobación de register_setting. * Corrección – Tablas de base de datos incorrectas referenciadas en subsitios en Multisitio. #### 1.4.0 * Enhancement – Allow ISC license in the License check. * Enhancement – Added check for use of settings with sanitization callback. * Enhancement – Added –ignore-codes in CLI to introduce a mechanism to ignore specific error codes. * Enhancement – New utils for fetching necessary version info details. * Enhancement – Added check for unsupported plugin name in plugin header field. * Enhancement – Segregate the severity of i18n checks. Make sure that is giving errors in the right context. * Enhancement – Provide more detailed information about checks when the README does not include a tested version or a list of contributors. * Enhancement – 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 – Give more context in the error of check wrong named files. * Enhancement – Simplified PHPUnit setup. Now it does not depend of running inside a WordPress installation. * Enhancement – Added new check for restricted contributors. * Fix – Delete transients in unit tests to avoid false positives. * Fix – Incorrect Tested up to version comparison will make error for two major versions up. * Fix – Excluded the use of functions file_get_contents and file_put_contents in the check to prevent false positives. * Fix – Duplicated error message in the check for wrong named files. * Fix – Use of Json encode wasn’t firing the error message. * Fix – Change error type of NonEnqueuedImage in ImageFunctions sniff from ERROR to WARNING. #### 1.3.1 * Enhancement – Add version utilities. * Fix – Escape error messages. * Fix – Renamed error type to ERROR_LOW_SEVERITY and WARNING_LOW_SEVERITY. * Fix – Fix PHPCS checks on unwritable filesystems. #### 1.3.0 * Enhancement – Update disallowed domains for Plugin URI check. * Enhancement – Added new checks for Plugin Header fields: missing plugin description, missing plugin version and invalid plugin version. * Enhancement – New check for validation of donate link in the readme file. * Enhancement – Increased severity for wrong Plugin Requires. * Enhancement – Added check Restrict parse_str() without second argument. * Enhancement – New check for Disallow usage of HEREDOC and NOWDOC. * Enhancement – Added acronyms allowed in Trademark checks. * Enhancement – Added option in CLI to add low severity errors and warnings. * Enhancement – Change error type for License check error codes. * Enhancement – Always use prefixed tables during runtime check requests. * Enhancement – Created a new class for checking licenses. * Enhancement – Added support for MPL-2.0 license. * Enhancement – Implement gherkin linter in GH action. * Enhancement – Update check for Contributors in markdown readme files. * Enhancement – CLI: Fix confusing runtime environment setup order. * Enhancement – Allow custom checks to provide installed_paths. * Enhancement – Improved the use of localhost URLs in the Plugin. * Enhancement – Documented checks in the plugin. * Enhancement – Increased severity for Code obfuscation checks. * Enhancement – Differentiate between non-existent readme and default readme file. * Enhancement – Encourage developers to use native functions for loading images in templates. * Enhancement – Added a check for not allowing include libraries already in WordPress core. * Enhancement – Warning for usage of query_posts() in favor of WP_Query. * Fix – Fix for the local environment is set up before testing. * Fix – Fix addon checks not being executed when running runtime checks. * Fix – Allow `default` as a text domain in the text domain check. * Fix – Allow GitHub URLs in the Plugin URI field. * Fix – Don’t flag Apache license. It’s allowed in the WordPress.org plugin repository. * Fix – Removes the path before the plugin, so it won’t affect to badly named files. #### 1.2.0 * Enhancement – Added a check for badly used names in files. * Enhancement – Increased severity for `BacktickOperator`, `DisallowShortOpenTag`,` DisallowAlternativePHPTags`, `RestrictedClasses`, and `RestrictedFunctions`. * Enhancement – Added security checks to the Plugin repository category. * Enhancement – Allowed `runtime-set` in code sniffer checks. * Enhancement – Changed warnings to errors in plugin header checks. * Enhancement – Detect forbidden plugin headers such as repository URIs in the Directory. * Enhancement – Added a new check for development functions that are not allowed in final plugins. * Enhancement – Created new images and icons for the plugin. * Enhancement – Introduced a slug argument in the CLI. * Enhancement – Added a check for discouraged PHP functions. * Enhancement – Added validation for Contributors in the readme file. * Enhancement – Added a warning for mismatched plugin names in the plugin header and readme file. * Enhancement – Checked for validation of Plugin Header fields: Name, Plugin URI, Description, Author URI, Requires at least, Requires PHP, and Requires Plugins. * Enhancement – Added a warning if the “Tested up to” value in the readme file exceeds the released version of WordPress. * Fix – Display a success message if no errors or warnings are found. * Fix – Made table results responsive. * Fix – Prevent proceeding to the next check if the Stable Tag value is set to ` trunk`. * Fix – Allow runtime initialization even when only add-on checks are requested. * Fix – Fixed an SPDX warning for the `GPL version 3` license. * Fix – Prevent runtime checks in the CLI context when they cannot be used. #### 1.1.0 * Feature – New `Non_Blocking_Scripts_Check` (`non_blocking_scripts`) runtime check to warn about enqueued scripts that use neither `defer` nor `async`. * Enhancement – Changed the namespace of included checks. * Enhancement – Introduced severity levels for all errors and warnings. * Enhancement – CLI: Support checking a plugin from a path or URL. * Enhancement – Added short descriptions and URLs for each check. * Enhancement – Improved messaging in check results. * Enhancement – Updated code obfuscation check with more accurate results. * Enhancement – Updated plugin review check to flag missing input sanitization (` WordPress.Security.ValidatedSanitizedInput`). * Fix – Improve readme checks to exclude invalid files. * Fix – Only show edit link if files are actually editable. #### 1.0.2 * Feature – New `Enqueued_Scripts_Scope_Check` (`enqueued_scripts_scope`), `Enqueued_Styles_Size_Check`(` enqueued_styles_size`) and `Enqueued_Resources_Check` (`enqueued_resources`) performance checks. * Enhancement – Improved readme check and added a new `wp_plugin_check_ignored_readme_warnings` filter. * Enhancement – New `wp_plugin_check_default_categories` filter to change the categories which are selected by default. * Enhancement – New `wp_plugin_check_ignore_files` filter to allow ignoring specific files. * Fix – Correct detection of readme files in Windows by normalizing file paths. #### 1.0.1 * Fix – Add missing `test-content` folder needed for runtime checks. * Fix – Do not send emails when setting up test environment. * Fix – Prevent PHP warning when the `argv` variable isn’t set. #### 1.0.0 * Feature – Complete overhaul of the plugin, its architecture, and all checks. * Feature – Added new [WP-CLI commands](https://github.com/WordPress/plugin-check/blob/trunk/docs/CLI.md) for running checks and listing available options. * Enhancement – Added option to only run checks for a specific category. #### 0.2.3 * Tweak – Use version [3.8.0 of the PHP_CodeSniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer/releases/tag/3.8.0) library, moving away from `squizlabs/PHP_CodeSniffer` to use `PHPCSStandards/ PHP_CodeSniffer`. * Fix – Ensure the plugin works as expected on the WP playground environment to enable reviewers to use PCP. Props @tellyworth. * Fix – Undefined array key “argv” when running the plugin check in certain environments. Props @afragen. [#340](https://github.com/WordPress/plugin-check/pull/340) #### 0.2.2 * Enhancement – Include support for Windows Servers. * Enhancement – Avoid using PHP CLI directly, which enables plugin developers to use PCP in a variety of new environments. * Fix – Remove dependency on `shell_exec` and `exec` functions, which enables plugin developers to use PCP in a variety of new environments. * Fix – Prevent problems with Readme parser warning related to `contributor_ignored` for when running the check outside WP.org. Props @dev4press. [#276](https://github.com/10up/plugin-check/pull/276) * Fix – Remove extra period on the end of the sentence for Phar warning. Props @pixolin. [#275](https://github.com/10up/plugin-check/pull/275) #### 0.2.1 * Agregado: enlace “Ver en editor de código” debajo de cada error o advertencia de PHPCS. Agradecimientos a @EvanHerman, @westonruter, @felixarntz, @mukeshpanchal27 [#262](https://github.com/10up/plugin-check/pull/262) * Corrección – Asegúrese de que `readme.txt` tenga prioridad sobre `readme.md` cuando ambos estén presentes. Agradecimientos a @bordoni, @afragen [#258](https://github.com/10up/plugin-check/pull/258) * Corrección – Asegurarse de que la comprobación de PHPCS se ejecute incluso cuando el binario de PHPCS no sea ejecutable. Agradecimientos a @bordoni, @shawn-digitalpoint, @mrfoxtalbot [#254](https://github.com/10up/plugin-check/pull/254) * Corrección – Cambios en el archivo Readme y corrección de errores tipográficos. Agradecimientos a @aaronjorbin. [#261](https://github.com/10up/plugin-check/pull/261) * Corrección: Las líneas largas de código con la comprobación PHPCS ya no se expanden más allá del tamaño del aviso. Agradecimientos a @bordoni, @felixarntz. [#263](https://github.com/10up/plugin-check/pull/263) * Corrección – Asegurarse de que tengamos compatibilidad con PHP 7.2 y eliminar la coma final. Agradecimientos a @bordoni, @leoloso. [#265](https://github.com/10up/plugin-check/issues/265) * Corrección – Incluir todas las cadenas que se omitieron en la versión anterior. Agradecimientos a @bordoni, @pixolin. [#270](https://github.com/10up/plugin-check/issues/270) #### 0.2.0 * Característica – Habilitada la modificación de la ruta del binario de PHP utilizada por el plugin con la constante `PLUGIN_CHECK_PHP_BIN`. * Característica – Incluída una comprobación del uso de `ALLOW_UNFILTERED_UPLOADS` en cualquier archivo PHP – Gracias a EvanHerman en [#45](https://github.com/WordPress/plugin-check/pull/45) * Característica – Incluida una comprobación de la presencia de los archivos de aplicación (`.a`, `.bin`, `.bpk`, `.deploy`, `.dist`, `.distz`, `.dmg`, `.dms`,`. DS_Store`, `.dump`, `.elc`, `.exe`, `.iso`, `.lha`, `.lrf`, `.lzh`, `.o`, `.obj`,`. phar`, `.pkg`, `.sh`, ‘.so`) – Gracias a EvanHerman en [#43](https://github.com/WordPress/plugin-check/pull/43) * Característica: Incluir una comprobación de la presencia del archivo readme.txt o readme.md – Agradecimientos a EvanHerman en [#42](https://github.com/WordPress/plugin-check/pull/42) * Corrección – Asegurarse de que el análisis de Readme se incluya correctamente cuando hay un archivo readme.md o readme.txt presente. Agradecimientos a Bordoni [#52](https://github.com/WordPress/plugin-check/pull/52) * Retoque – Deshabilitar las funciones `move_uploaded_file`, `passthru`, `proc_open`– Atributos alexsanford en [#50](https://github.com/WordPress/plugin-check/pull/50) * Retoque – Cambia el tipo de mensaje para utilizar las funciones que WordPress ya incluye de Advertencia a Error. Agradecimientos a davidperezgar en [#18](https://github.com/WordPress/plugin-check/issues/18) * Retoque – Cambiar el tipo de mensaje para el uso incorrecto de la etiqueta Stable de Aviso/Advertencia a Error. Agradecimientos a davidperezgar en [#3](https://github.com/WordPress/plugin-check/issues/3) #### [0.1] 2011-09-04 Versión original de la herramienta de comprobación de plugins, no es una versión lanzada del plugin, este registro de cambios está aquí solo con fines históricos. ## Plugin de la comunidad Este plugin está desarrollado y recibe soporte de una comunidad. [Contribuir a este plugin](https://github.com/WordPress/plugin-check/) ## Meta * Versión **1.9.0** * Última actualización **hace 2 meses** * Instalaciones activas **9,000+** * Versión de WordPress ** 6.3 o superior ** * Probado hasta **7.0** * Versión de PHP ** 7.4 o superior ** * Idiomas * [Catalan](https://ca.wordpress.org/plugins/plugin-check/), [Chinese (Taiwan)](https://tw.wordpress.org/plugins/plugin-check/), [Dutch](https://nl.wordpress.org/plugins/plugin-check/), [English (Australia)](https://en-au.wordpress.org/plugins/plugin-check/), [English (US)](https://wordpress.org/plugins/plugin-check/), [French (France)](https://fr.wordpress.org/plugins/plugin-check/), [German](https://de.wordpress.org/plugins/plugin-check/), [Italian](https://it.wordpress.org/plugins/plugin-check/), [Japanese](https://ja.wordpress.org/plugins/plugin-check/), [Persian](https://fa.wordpress.org/plugins/plugin-check/), [Polish](https://pl.wordpress.org/plugins/plugin-check/), [Portuguese (Brazil)](https://br.wordpress.org/plugins/plugin-check/), [Russian](https://ru.wordpress.org/plugins/plugin-check/), [Spanish (Chile)](https://cl.wordpress.org/plugins/plugin-check/), [Spanish (Spain)](https://es.wordpress.org/plugins/plugin-check/), y [Swedish](https://sv.wordpress.org/plugins/plugin-check/). * [Traducir a tu idioma](https://translate.wordpress.org/projects/wp-plugins/plugin-check) * Etiquetas * [accessibility](https://cl.wordpress.org/plugins/tags/accessibility/)[performance](https://cl.wordpress.org/plugins/tags/performance/) [security](https://cl.wordpress.org/plugins/tags/security/)[testing](https://cl.wordpress.org/plugins/tags/testing/) * [Vista Avanzada](https://cl.wordpress.org/plugins/plugin-check/advanced/) ## Calificaciones 4.4 de 5 estrellas. * [ 25 valoraciones de 5 estrellas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=5) * [ 1 valoración de 4 estrellas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=4) * [ 2 valoraciones de 3 estrellas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=3) * [ 2 valoraciones de 2 estrellas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=2) * [ 2 valoraciones de 1 estrellas ](https://wordpress.org/support/plugin/plugin-check/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/plugin-check/reviews/#new-post) [Ver todas las reseñas](https://wordpress.org/support/plugin/plugin-check/reviews/) ## Colaboradores * [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/) ## Soporte Problemas resueltos en los últimos dos meses: 0 de 2 [Ver el foro de soporte](https://wordpress.org/support/plugin/plugin-check/)