JetReviews plugin review and common issues

In JetReviews → Settings → Review Form, check the “Allow Guest Reviews” setting. If reviews are restricted to logged-in users, the form shows a login prompt to guests. Enable guest reviews to allow non-registered visitors to submit reviews. For guest reviews, the plugin typically requires a name and email field to identify the reviewer. If the setting is already enabled and the login message still shows, verify the page’s user context is correctly detected — a caching issue may serve a cached logged-out version to all visitors.

In JetEngine Listing Grid, add the “JetReviews Rating” dynamic tag to the listing item template. In the dynamic tag settings, select the post type that has JetReviews enabled. The tag reads the average rating from JetReviews’ database and displays it for each post in the listing. If the rating shows as placeholder: (1) verify JetReviews is configured for the same post type as the listing; (2) the post must have at least one approved review for a rating to display; (3) verify the JetReviews plugin is active and updated alongside JetEngine.

Approved reviews should appear on the frontend immediately after approval. If approved reviews are missing: (1) clear all page caches — a cached version may not include newly approved reviews; (2) in JetReviews → Reviews, filter by “Approved” status to verify the reviews are indeed marked approved; (3) check the Reviews display widget settings — a filter may be limiting which reviews display (e.g., only showing reviews with 4+ stars); (4) verify the Reviews display widget is on the correct page and connected to the correct post type.

In JetReviews → Settings → Rating Criteria, add multiple criteria. Create criteria named “Food Quality,” “Service,” and “Ambiance” each with a 1-5 star scale. Assign these criteria to the Restaurant post type. When a user submits a review, they rate each criterion independently. JetReviews calculates the overall rating as the average across all criteria. The reviews display widget shows the breakdown per criterion alongside the overall average rating.

In JetReviews → Settings → Reply, enable owner replies. Configure which user roles can reply (typically Administrator and Editor, or a custom role for business owners). Business owners navigate to their listing and see a “Reply” button on each review. Their reply appears below the original review with an “Owner” or “Business” badge. For multi-vendor directories where each vendor owns their listing, combine with a vendor management plugin that grants the appropriate capability to reply to reviews on their specific posts.

JetReviews is separate from WooCommerce product reviews and does not replace them. WooCommerce has its own review system integrated with orders and verified purchases. JetReviews adds a parallel review system for any post type — you could use JetReviews on a custom “Vendor” post type alongside WooCommerce’s native product reviews. For WooCommerce-specific review enhancement (photo reviews, verified purchase badges, incentivized reviews), dedicated WooCommerce review plugins are more integrated.

JetReviews does not have a built-in import tool for migrating reviews from other plugins or platforms. Migrating reviews from the WordPress comment system (where many review plugins store data) or from a custom review database requires custom migration scripting. If migrating from a system that stores reviews as WordPress comments with rating meta, a developer can write a script to import the comment data into JetReviews’ custom database tables.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.