- How do I install jelte-ten-holt/in-other-shops in a Laravel application?
- Install it with Composer using composer require jelte-ten-holt/in-other-shops. Then follow the package README to publish any config, views, and translations and to run package migrations if your setup uses them. The package is designed to plug into an existing Laravel app without replacing your catalog logic.
- Which Laravel and PHP versions does this package support?
- The supported Laravel and PHP versions are defined by the package's composer.json constraints. Check those constraints and the README before installing, especially if you are on an older Laravel release. Because the package is Laravel-specific, keep your framework version aligned with its declared support matrix.
- How do I associate shops and product offers with my existing Product model?
- Configure the shop and offer models in the package config, then use the package's relations or API to attach offers to your product models. You keep your existing Product model and catalog logic; the package adds the “in other shops” data layer around it. This lets you store per-product retailer URLs without building custom tables and view logic yourself.
- Can I customize the Blade component that renders the “also available at” section?
- Yes. The package ships a ready-to-use Blade component, and its views can be published and overridden in your application. You can adjust markup, styling, and surrounding layout while keeping the package's data and ordering logic. Translations can also be customized if you need different storefront copy.
- How do I control which shops appear and in what order?
- The package supports visibility and ordering controls for shops and offers. You can hide offers you do not want to display and define the order in which the remaining retailers appear on the product page. This keeps merchandising decisions out of your Blade templates and in the package data layer.
- Does the package support translations for the storefront section?
- Yes. The package's presentation layer includes translations that can be customized, so the “also available at” copy can match your storefront language. Publish the translation files and edit the strings you need. Keep catalog-specific labels in your own models if they vary per product or shop.
- Are outbound links to other retailers configurable?
- Yes. Outbound links are part of the offer data and rendering, so each shop offer can point to its own product URL. If you need specific link attributes such as rel or target, customize the published Blade view. This keeps link behavior under your control without altering the package's data model.
- Do I need database migrations, or can I use my own models?
- The package uses configurable models for shops and offers, so you can align it with your application's conventions. Check the README for whether migrations are included and whether you should publish them or map the package to existing tables. If you use custom models, verify the expected relations and attributes are implemented.
- How should I test this package before using it in production?
- Test the rendered component with representative products, shops, and offer URLs, including hidden and ordered offers. Run integration tests against MySQL as well as SQLite, because SQLite can mask column and identifier issues that appear in production. Also verify outbound links and translated copy in a staging environment.
- What are alternatives to using this package for “in other shops” listings?
- You can build the same feature with your own shop and offer tables, Eloquent relations, and a Blade partial. A custom implementation gives full control but requires maintaining the data layer, ordering, visibility, and view logic yourself. This package is a fit when you want those pieces standardized and configurable in Laravel.