Weave Code
Sylius Wishlist Bundle Laravel Package
sherlockode/sylius-wishlist-bundle
Sylius plugin that adds customer wishlists to your storefront, letting shoppers save products for later, manage their lists, and move items to the cart. Integrates with Sylius resources and templates for straightforward setup and customization.
At a glance
Frequently asked questions about Sylius Wishlist Bundle
- How do I install the Sherlockode Sylius Wishlist Bundle?
- Install it with Composer using composer require sherlockode/sylius-wishlist-bundle, then register the bundle in config/bundles.php. Import the bundle routing, enable the wishlist resources in your Sylius resource configuration, and update the database schema with a Doctrine migration or schema update. Clear the cache afterwards so the new routes, templates and translations are picked up.
- Does this wishlist bundle work with Laravel?
- No. Sherlockode Sylius Wishlist Bundle is built for Sylius, which runs on Symfony, and it depends on Sylius core resources, routing and Twig templates rather than anything in the Laravel framework. There is no Laravel service provider or Laravel-specific integration, so it will not run inside a Laravel application. For a Laravel storefront you would need a different package or a custom implementation.
- Which Sylius versions does this bundle support?
- The supported Sylius versions are declared in the package composer.json, so check that constraint on Packagist or in the GitHub repository before installing. Because the bundle plugs into Sylius resources, templates and routing, it is tied to the Sylius major version it was built against. Pin the bundle to a release that matches your Sylius version and re-run your test suite after upgrading either one.
- Do wishlists require a logged-in customer, or can guests use them?
- Wishlists are tied directly to Sylius customer accounts, so the feature is aimed at logged-in customers rather than anonymous visitors. Guests are typically redirected to the login page when they try to reach a wishlist route. If you need guest wishlists you would have to extend the bundle and store lists against a session or another temporary identifier.
- How do customers add or remove products from a wishlist?
- The bundle adds add-to-wishlist and remove-from-wishlist actions that hook into Sylius product listing pages and product detail pages. Shoppers can save a product without leaving the page they are browsing. The buttons live in standard Twig templates, so you can override them if you want a different placement in your theme.
- Can customers move wishlist items directly into the cart?
- Yes. Wishlist items include a move-to-cart action, so a customer can send a saved product straight to the Sylius cart from their wishlist page. You decide in your templates whether the item is then removed from the list or kept. The integration uses Sylius's own cart manager, so existing cart rules and promotions still apply.
- How do I override the wishlist Twig templates and translations?
- Twig templates can be overridden by placing files under templates/bundles/SherlockodeSyliusWishlistBundle/ in your application, following the standard Sylius bundle override convention. Translation files follow the same pattern, so you can override or add messages per locale without editing vendor code. Keeping overrides in your own theme makes future bundle upgrades much easier.
- Can I extend or replace the wishlist entity classes?
- Yes. The wishlist and wishlist item resources are declared through standard Sylius resource configuration, so you can point them at your own entity classes that extend the bundle defaults. That lets you add fields or behaviour while keeping the bundle's controllers and templates working. Remember to update your Doctrine mapping and run a migration for any added columns.
- How do I test the wishlist feature in my Sylius store?
- The GitHub repository contains the bundle's own test suite and CI configuration, which is the best place to confirm what is covered and which Sylius and PHP versions are tested. Run it locally with the project's Composer scripts or PHPUnit after cloning, especially before relying on a customised fork. For your store, add a functional test that logs a customer in and walks through adding an item, viewing the list and moving it to the cart.
- What are the alternatives to using this bundle?
- Alternatives include building a small wishlist feature yourself on top of Sylius resources, or using another community wishlist plugin for Sylius. This bundle makes sense when you want standard Sylius conventions, overridable Twig templates and translations, and a customer-bound list without writing it from scratch. Check its release history and supported Sylius versions before committing, particularly if your store is on the newest Sylius major.
Weaver
How can I help you explore Laravel packages today?