How to write and save the review

This is step 9 of our onboarding guide to becoming a reviewer

So you now have a theme, and you have access to the ticket in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.

Before we go back to the requirements and how to actually check the theme, lets talk a little about how to write the review.

-The first thing that we would like to remind all reviewers of is to not write the review directly in the comment form in Trac.

This is because if you accidentally get logged out of The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization., or if you accidentally leave or refresh the page, the unsaved content in the comment form will be lost.

Instead, use your favorite word processor, or why not your favorite code editor, so that you can save the review and then add it to the comment form later once it is finished.

Top ↑

Presenting the result of the review

When you start working on a review, the first review is expected within 48 hours. -If you need more time, all you have to do is tell the theme author, so that they know that you are still working on the review.

When showing the result of the review to the theme author, always separate requirements from recommendations. That way, the authors can see what they need to fix before the theme can be added to the theme directory.

Be specific. Including file names and line numbers in your review will help the author, and it will help follow up reviews.

Don’t be afraid to ask the theme author any questions about the theme and the code. Many problems can be solved this way.

Top ↑

Plugin reports

You can include reports from the Theme SnifferTheme Sniffer Theme Sniffer is a plugin utilizing custom sniffs for PHP_CodeSniffer that statically analyzes your theme and ensures that it adheres to WordPress coding conventions, as well as checking your code against PHP version compatibility. The plugin is available from GitHub. Themes are not required to pass the Theme Sniffer scan without warnings or errors to be included in the theme directory. and Theme Check plugins in your review, but don’t just paste a list of warnings without adding additional comments.

Errors needs to be fixed, but there are a few known exceptions, such as overriding WordPress Globals.

All errors needs to be manually checked before they are marked as required.

Warnings are hints of things that may be a problem, but needs to be manually checked.

If you want the theme author to solve warnings, please be specific about this so that the author does not have to wonder.

Top ↑

Selecting a ticket status

When you have added the review content to the comment form in the Trac ticket, you can choose between different statuses, depending on your permissions.

-As you do more reviews, the moderators will give you more privileges to change the ticket status.

Leave as new -Lets theme author continue to improve the theme, but no reviewer will be assigned. Other reviewers are then free to continue the review.

Review -Assign the ticket to yourself (the logged in user), and let the author continue working on improvements.

Approve -If no problems were found, the ticket can be approved.

Not approved -If there are many problems with the theme, the ticket can be closed.

If this is your first review, please ask an experienced reviewer to confirm before closing the ticket.

Last updated: