a. Using the Review Admin Tool

Reviews are done via the Dashboard on the directory. Only reviewers and admins have access to this.

Important Links:

New Plugins New Plugins

All new plugins have a status of ‘draft.’ This means they have not yet been reviewed. To view all newly submitted plugins, go to My Plugins and click on Pending Initial Review:

Click on the post to edit it. You should chose to open in a new window.

On the post edit page, you will see the Plugin Review Tools. Most important at this stage is the zip file. Use that to download the new zip for your review.

Perform the steps on the Review Walkthrough and Review Checklist.

If a plugin shows that it has comments, that means a non-admin has performed a review, but does not have permissions to email the developer and move the post into pending status.

Top ↑

Commenting on Plugins Commenting on Plugins

If you do not have the ability to approve plugins, once you’ve reviewed a plugin please leave an internal note:

Document the issues found. For example, a good note would be as follows:

  • calls wp-load.php on multiple pages
  • saves files to plugin directory
  • includes own jquery
  • calls bootstrap css externally from CDN
  • author has wordpress in their domain name

An administrator will then take this information and send an email to the plugin author, explaining what to fix and why.

If there are no issues found, leave a note stating that.

Top ↑

Pending Plugins Pending Plugins

If, following a review, a plugin cannot be approved yet, a plugin administrator will change the status in Plugin Controls to Pending and press Save Changes.

Then they will use the Contact plugin author button to email them an explanation why, using the predefined replies within SupportPress if possible.

Setting a plugin to pending will not email the developer automatically. You must remember to use the contact button.

Top ↑

Approving Plugins Approving Plugins

When a plugin is ready to be approved, edit the page and click on ‘edit’ for the status. Change the status to Approved and click Save Changes.

This will automatically email the developer. You need do nothing more.

Top ↑

Rejecting Plugins Rejecting Plugins

Most plugins will not be rejected. If a plugin must be rejected, leave an internal note explaining why. Example entries:

  • Rejected per author request
  • Duplicate submission
  • Author banned from directory

Very rarely will those cases occur. Once the plugin is rejected, use the Contact plugin author button to email them and explain why it was rejected.

Top ↑

Reviewing Pending Plugins Reviewing Pending Plugins

Once a plugin has had its initial review, it moves into ‘pending. To view all pending plugins, go to My Plugins and click on Pending:

All pending plugins will remain in this state until they can be approved.