Weave Code
Review Bundle Laravel Package
sylius/review-bundle
Sylius Review Bundle adds customer product reviews to Sylius stores, with ratings, review submission, moderation, and average rating display. Integrate it to let shoppers share feedback and help others make informed buying decisions.
[READ-ONLY] Reviews support for Symfony2 applications.
Frequently asked questions about Review Bundle
- Can I install sylius/review-bundle in a Laravel application?
- No. It is a Symfony bundle built on sylius/resource-bundle, Doctrine ORM mappings, the Symfony DI container, Symfony form types, grid abstractions and Twig templates, so there is nothing for Laravel's service container, Eloquent or Blade to bind to. Composer resolution against current Illuminate components will fail, and forcing it would drag an end-of-life PHP and Symfony runtime into your stack with no security support. The realistic use is as a reference implementation of a review domain, not as a dependency.
- What features does Sylius ReviewBundle provide out of the box?
- It adds customer product reviews with star ratings, a submission flow tied to the product catalog, an admin moderation and approval workflow, and an average rating calculation projected onto the product for display. Eligibility rules for who may review are configurable, and the bundle integrates with Sylius product pages through its templates and grid configuration. Everything ships as Symfony services, Doctrine mappings and Twig views.
- Which PHP and Symfony versions does it require, and does that affect Laravel support?
- The bundle targets Symfony 2.x and PHP 5.x-era constraints, which is the core blocker for any modern framework. That runtime pairing is end-of-life, so there are no upstream security patches and no upgrade path. Because of this, no Laravel version is supported, and there is no version of the package you can safely pull into a current Laravel application.
- How do I install and register the bundle?
- In a Sylius application you would add sylius/review-bundle via Composer and register it in the kernel and container configuration, exactly like other Sylius bundles. In practice most teams install sylius/sylius rather than individual bundles, because this repository is a read-only subtree split of the Sylius monorepo. There is no Laravel installation path: no service provider, no config publish tag, no migrations for Illuminate.
- How does the review moderation and approval workflow work?
- Each review carries a status field, and administrators accept or reject submissions from an admin grid, which drives the accept and reject state machine with transition guards. Only accepted reviews contribute to the public product page and to the average rating, which gives you a clean separation between submitted and published content. When porting, decide early whether you need the full guarded state machine or whether a published boolean is enough for a first version.
- How are product average ratings calculated and displayed?
- The bundle derives an average score from accepted reviews and projects it onto the product so product listings and detail pages can display it without aggregating on every request. That projection is the piece most worth copying into Laravel: an average column or a cached aggregate updated when a review transitions to accepted. Do not recompute averages in a Blade loop at render time on a busy catalog.
- Is the package production-safe and actively supported?
- Not for a Laravel target. The codebase sits on an unsupported Symfony and PHP baseline, so production use means inheriting an unpatched runtime. Note also that the five-star rating and zero dependents figures are misleading: this is a read-only subtree split of the Sylius monorepo, so real adoption shows up as sylius/sylius installs, and support is governed by Sylius's release cadence rather than a standalone contract. The risk here is schedule risk from porting, not product risk, because the review domain itself is simple and low throughput.
- What is the best Laravel alternative for product reviews and ratings?
- Evaluate maintained Laravel review and rating packages on Packagist first, and check whether your admin stack already has a reviews or ratings component for Filament or Nova. If nothing fits, a small Eloquent-based review domain is genuinely quick to build and gives you full control over moderation and rating aggregation. The default decision rule should be existing maintained package first, custom build second, and a Sylius port only as a specification input.
- How would I rebuild this review domain in Laravel with Eloquent?
- Start with the schema: a product_reviews table holding rating, title, comment, author, status and timestamps, plus a polymorphic reviewable association if reviews must cover products, services or content, not just products. Model moderation as a status enum with explicit transitions, and expose the average via withAvg on the reviews relation or a cached rating column on the reviewed model. Add admin grids through Filament or Nova, and keep the review eligibility rules in a dedicated service rather than a controller. The transferable assets are the data shape, the moderation state machine and the polymorphic reviewable contract; the Doctrine mappings, service YAML, form types and Twig templates are discarded.
- How do I test a ported review and moderation workflow?
- Feature test the things that actually break: submission eligibility rules, duplicate review prevention per customer and product, each moderation transition including invalid ones, and average rating recalculation after accept or reject. Use factories for products and reviews so the polymorphic reviewable case is covered from day one. Also assert that rejected reviews never appear on the product page or in the aggregate, since that is the leak most likely to reach production.
Weaver
How can I help you explore Laravel packages today?