New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Plugin Check is a WordPress.org tool which provides checks to help plugins meet the directory requirements and follow various best practices. | You have to log in to add a translation. | Details |
Original untranslated
Plugin Check is a WordPress.org tool which provides checks to help plugins meet the directory requirements and follow various best practices.
You have to log in to edit this translation. |
|||
| ↑ | Plugin Check (PCP) | Plugin Check (PCP) | Details |
Original current |
|||
| <strong>Important:</strong> 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. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Important:</strong> 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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Plugin Check now includes an AI-powered Plugin Namer tool (accessible via <em>Tools > Plugin Check Namer</em>) that helps plugin authors evaluate plugin names before submission. This tool checks for: | You have to log in to add a translation. | Details | |
Original untranslated
Plugin Check now includes an AI-powered Plugin Namer tool (accessible via <em>Tools > Plugin Check Namer</em>) that helps plugin authors evaluate plugin names before submission. This tool checks for:
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| <strong>Plugin Namer Tool</strong> | You have to log in to add a translation. | Details | |
Original untranslated
<strong>Plugin Namer Tool</strong>
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Generic or overly broad naming issues | You have to log in to add a translation. | Details | |
Original untranslated
Generic or overly broad naming issues
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Compliance with WordPress plugin naming guidelines | You have to log in to add a translation. | Details | |
Original untranslated
Compliance with WordPress plugin naming guidelines
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Potential trademark conflicts with well-known brands | You have to log in to add a translation. | Details | |
Original untranslated
Potential trademark conflicts with well-known brands
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Similarity to existing plugins in the WordPress.org directory | You have to log in to add a translation. | Details | |
Original untranslated
Similarity to existing plugins in the WordPress.org directory
CommentFound in description list item. You have to log in to edit this translation. |
|||
| You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL: <code>wp plugin check https://example.com/plugin.zip</code> or to check a plugin from a path: <code>wp plugin check /path/to/plugin</code> | You have to log in to add a translation. | Details | |
Original untranslated
You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL: <code>wp plugin check https://example.com/plugin.zip</code> or to check a plugin from a path: <code>wp plugin check /path/to/plugin</code>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Does a plugin need to pass all checks to be approved in the WordPress.org plugin directory? | You have to log in to add a translation. | Details | |
Original untranslated
Does a plugin need to pass all checks to be approved in the WordPress.org plugin directory?
CommentFound in faq header. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.