WordPress Plugin Check v0.0.3

Scan your WordPress plugin for common errors before submitting it to WordPress.org for review.

The Plugin Check plugin can be used to check a plugin locally on a test site during development, or it can be used to check a plugin .zip from a remote URL.

Intentions

This plugins intention is to minimize the common pitfalls and errors developers encounter when submitting plugins to WordPress.org for review.

When submitting a plugin for admission into WordPress.org there are a number of guidelines that must be followed, and many developers miss steps or checks that prolong the review process over multiple days.

Developing a plugin in tandem with Plugin Check will allow developers to periodically check their code for missteps or invalid code that would prevent a plugin from being accepted into the WordPress.org repository.

Developers should use this plugin during development to check for any errors in their code, or, at the very least, use Plugin Check to scan their plugin before submitting it for review on WordPress.org.

Caveats

• Plugin Check currently only works on Mac OS.
• Plugin Check requires that your WPCS is installed at ~/wpcs/.

Installation & Usage

• Download the latest release of Plugin Check (plugin-check.zip) from the releases.
• Login to your WordPress website and go to 'Plugins > Add New'.
• At the top of the page, click on 'Upload Plugin'.
• Select the plugin-check.zip file you downloaded in step 1.
• Activate Plugin Check.
• Navigate to 'Tools > Plugin Check'.
• Select your plugin from the dropdown list and click 'Check Plugin'.
• Or to check a remote plugin, click on the 'Remote Plugin' tab and enter the URL of the remote location where your plugin is.

Ignored Files When Scanning

If this plugin is used during development, there may be many files in the working copy of your plugin. Plugin Check works by zipping up your local plugin directory, and then scanning that against a set of rules. Some files might get included in the .zip that shouldn't be, so Plugin Check does it's best to exclude a default set of files that are generally used during development that will throw an error during plugin scans.

The following files will not be included in the .zip that is scanned.

• .github
• .wordpress-org
• .distinclude
• .editorconfig
• .eslintignore
• .eslintrc.js
• .gitignore
• .npmrc
• .nvmrc
• .stylelintignore
• .stylelintrc.json
• CODE_OF_CONDUCT.md
• CONTRIBUTORS.md
• babel.config.json
• composer.json
• composer.lock
• cypress.config.js
• node_modules
• vendor
• .htaccess
• Gruntfile.js
• gruntfile.js
• manifest.xml
• package.json
• phpcs.xml
• phpunit.xml.dist
• webpack.config.js
• yarn.lock

Development

To run Plugin Check repository locally:

• Clone this repository into your wp-content/plugins directory.
• From the Plugin Check root, run npm run setup.
• Activate 'Plugin Check' from the WordPress dashboard.
• Head to 'Tools > Plugin Check'.
• Select your plugin from the dropdown list and click on 'Check Plugin'.
• Check the results of the plugin scan in the text field below.
• Or to check a remote plugin, click on the 'Remote Plugin' tab and enter the URL of the remote location where your plugin is.

Credits

This plugin was built leveraging the open source WordPress plugin-scan.sh by @Ipstenu. Huge thanks to the WordPress.org plugin review team.