Product and Store Reviews: setup and help

1. Upload and install the mprcomments ZIP through Modules > Module Manager.
2. Click Configure, or open Reviews > Settings > Configuration.
3. Keep Enable Reviews and Product Reviews on. Review Require Moderation and Allow Guest Reviews.
4. Check display, photo and notification settings, then click Save.
5. Open an active product and use its review form as a customer. Submit a rating and review text.
6. If moderation is on, open Reviews > Reviews and approve the pending review.
7. Reload the product and check its review content, stars and rating badge where your theme renders them.

Installation creates the module schema, hooks, admin menu, default configuration and modules/mprcomments/img/reviews/ upload directory. Use Reviews > Settings > Integrity if optional service credentials, tables or hooks need attention.

The form is headed Review Settings. Settings are grouped into General, Review Types, Display, SEO & Anti-Spam, Notifications, Integrations and Theme styles.

You can store reviews for products, categories, CMS pages and the store. The supplied storefront form collects product reviews. Other review types need a separate collection form or integration.

A signed-in customer's name and email come from their account. Guests must provide both when guest submissions are enabled. A signed-in customer cannot submit another non-spam review for the same entity in the same shop.

The uploader accepts JPEG, PNG and WebP images. It checks image readability, resizes within 1200 by 1200 pixels and creates thumbnails. Your PHP image library must support the chosen format, and the review image directory must be writable. PHP upload and POST limits can impose a lower limit than the module setting.

After a photo test, check the image on the published review. A review can save its text even when an attachment is skipped, because invalid files are dropped during upload.

The v3 check requires a successful response, a score of at least 0.5 and action submit_review. There is no threshold field in this form. Configure both keys before enabling CAPTCHA. With v2, a review can be submitted when the secret key or the provider response is unavailable.

When verification is enabled, the native form also offers Email verification alternative. The customer completes the review, selects that alternative and clicks Email me a verification code. They then enter the eight-digit code and choose Verify and submit review. The code lasts 10 minutes and permits at most five checks. A changed review requires a new code. The form tells customers to select the same photos again after requesting a code.

The email alternative works without JavaScript. It requires working PrestaShop mail delivery and private writable verification state under the PrestaShop cache directory. The module creates its verification directory with 0700 and its state file with 0600 permissions.

Content checks require at least 10 characters and a rating from 1 to 5. The supplied form limits title to 255 characters and content to 5000 characters. Spam checks also reject excessive URLs and selected HTML tags.

Product schema uses approved native product reviews only. Imported company reviews are left out of product structured data, even if you include them in a visible badge count. When mprseorevolution is enabled, this module skips its own product schema output. Check the combined page markup with Google's Rich Results Test; Google decides whether rich results are shown.

Use the normal PrestaShop mail setup for notifications. Test the new-review, individual approval and reply emails. Bulk approval directly updates review statuses and does not run the individual approval notification service.

Review reminders record the order, product and customer for pending invitations, skipping existing reminders and products already reviewed. The supplied cron synchronizes external reviews only. The module does not send reminder emails, regardless of the reminder switch or delay.

Open Reviews > Reviews. Filter the list by status or entity as needed. You can approve, reject, mark as spam, delete and reply to reviews. Bulk actions include Approve selected, Reject selected and Delete selected. Deletion is not a reversible status change.

Use a public reply for the text you want displayed beneath the review. The reply email is attempted when enabled and the review has a customer email.

Open Reviews > Criteria to create translated criterion names. Set the entity type, active state and position. Criteria can apply to all types or product, category, CMS or store reviews. The model uses active on, type all and position 0 for new criteria. Check the criterion list in the product form after saving.

The verified-purchase check uses a valid order containing the product. It is not a guest email verification label. The module does not provide a customer-account screen for editing submitted reviews. Handle review changes through the back-office tools.

Use Review Settings > Integrations for credentials and display. Reviews > External Reviews lists imported records. These are company reviews, not native reviews of the particular product.

Trustpilot

For API sync, enable Trustpilot, enter the API key and Business Unit ID, save, then click Sync Now in External Reviews Status. Read the provider's fetched/new counts and errors. The current readiness check requires the key and Business Unit ID, not the API secret.

For a CSV import, enable Trustpilot and save to expose Trustpilot CSV Import. Choose the CSV and click Import. Required headers can use these alternatives:

referenceId: referenceId, id, reviewId, reference_id
stars: stars, rating, star
createdAt: createdAt, created_at, date, datePublished

Optional headers:

text: text, content, review, reviewText, body
title: title, heading
consumer.displayName: consumer.displayName, consumerDisplayName, author, name, consumer_name
language: language, lang, locale

The parser reads comma-separated CSV with a header and accepts a UTF-8 BOM. Review IDs and ratings from 1 to 5 are required for imported rows.

Google Business Profile

Enter the credentials, save and use Sync Now. The module signs a JWT, requests an access token, then reads account and location reviews. You need PHP OpenSSL, cURL, working HTTPS and API access for these credentials, and the service account must have access to that business location. Read any sync errors before relying on this integration.

Company-review display

There is no current Lazy-load Company Reviews on Product Pages field. When a product has no native reviews but company reviews are displayed, the tab title identifies them as Company reviews, with their count. Native product reviews retain their own meaning and count.

Schedule external sync

The status panel shows a Cron URL only when a sync token has been configured. The token is empty by default. The module does not generate one automatically or offer a control to create one. Use Sync Now if your installation has no configured token.

When your installation supplies a token, use the displayed URL:

https://example.com/module/mprcomments/cron?token=YOUR_EXT_CRON_TOKEN&action=sync

The endpoint returns JSON for the shop of the request. Read each provider's result, since the overall success flag does not mean every provider imported. Keep the token private. This cron is for external review sync only.

Modern product pages use displayProductExtraContent. PrestaShop below 1.7 has displayProductTab and displayProductTabContent handlers. Your theme must render the appropriate hooks.

For listing stars, a developer can use:

{hook h='displayProductListReviews' product=$product}

The badge handlers are displayProductAdditionalInfo and displayMprProductFunctionalButtons. Choose the appropriate placement in your theme and check for duplicate output when customizing:

{hook h='displayProductAdditionalInfo' product=$product}
{hook h='displayMprProductFunctionalButtons' product=$product}

The form sends action=submitReview, entity type/ID, rating, title, content, criterion_{id} fields and optional review_images[]. It also needs the current session token. Use the supplied form or its generated URL; the old payload example without a session token is not a complete submission form.

The public hub uses the reviews route, normally /reviews with friendly URLs and the appropriate language/shop prefix. It lists approved reviews. Only its first unfiltered view with available content is intended to be indexable. Paginated, filtered and empty variants use noindex policy. Root examples:

/reviews: index, follow when it has content
/reviews?page=2: noindex, follow
/reviews?type=product: noindex, follow

The module exposes the root hub to compatible sitemap generators. Product structured data remains separate from imported company reviews displayed on the hub.

In Theme styles, use detected theme values and shared style controls. Review-specific defaults are:

For theme CSS, you can use:

.mprcomments-container {
  --mprcomments-star: #ffb400;
  --mprcomments-star-empty: #d8d8d8;
  --mprcomments-verified: #1f9d55;
  --mprcomments-radius: 8px;
}
.mprcomments-review__reply {
  border-left: 3px solid var(--mprcomments-primary);
}
.mprcomments-badge__link {
  text-decoration: none;
}
.mprcomments-external__title {
  margin-top: 1.5rem;
}

The GDPR export returns a customer’s review fields. A GDPR deletion request anonymizes their name, email and customer ID on linked reviews and removes their helpfulness votes and reports. Review content and IP addresses remain stored. Masking displayed names is a separate display setting.

Test moderation with one pending review, then approve it and verify public output. Test a public reply, notification email, a valid photo and a helpful vote from a logged-in customer.

If submission fails, check guest permissions, duplicate review restrictions, minimum text length, IP interval, current session token and CAPTCHA or email verification. If email codes fail, check mail delivery, code expiry, changed review/photos and writable private cache state.

If photos are missing, inspect PHP upload limits, writable img/reviews, image format support and the actual published attachment. If stars are absent, confirm approval, native review count, display switches and theme hooks. If external reviews are absent, check enabled providers, credentials, source counts, Sync Now errors and Show Company Reviews on Product Pages.

If schema is absent, check approved native product reviews, Enable Schema.org Markup and whether mprseorevolution owns schema output. If reminders do not send, the current module only creates their queue. Adding the external-sync cron does not supply a sender.

Turn off Enable Reviews to stop normal review display. Disable external-sync scheduling separately if you configured it. Export the data you need before uninstalling. Uninstall removes module configuration and schema tables, including saved reviews and related records. The uninstall method does not explicitly delete the img/reviews directory or verification cache files; check residual files if you remove the module completely.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.