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) | 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> | 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. |
|||
| What if the plugin reports something that's correct as an "error" or "warning"? | You have to log in to add a translation. | Details | |
Original untranslated
What if the plugin reports something that's correct as an "error" or "warning"?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Activate the Plugin Check plugin. | You have to log in to add a translation. | Details | |
Original untranslated
Activate the Plugin Check plugin.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Visit <strong>Plugins</strong>. | You have to log in to add a translation. | Details | |
Original untranslated
Visit <strong>Plugins</strong>.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Upload the entire <code>plugin-check</code> folder to the <code>/wp-content/plugins/</code> directory. | You have to log in to add a translation. | Details | |
Original untranslated
Upload the entire <code>plugin-check</code> folder to the <code>/wp-content/plugins/</code> directory.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Install and activate the Plugin Check plugin. | You have to log in to add a translation. | Details | |
Original untranslated
Install and activate the Plugin Check plugin.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Search for <strong>Plugin Check</strong>. | You have to log in to add a translation. | Details | |
Original untranslated
Search for <strong>Plugin Check</strong>.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Visit <strong>Plugins > Add New</strong>. | You have to log in to add a translation. | Details | |
Original untranslated
Visit <strong>Plugins > Add New</strong>.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Manual installation | You have to log in to add a translation. | Details | |
Original untranslated
Manual installation
CommentFound in installation header. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.