- What does the piotrmus/akeneo-product-translation package do?
- It is a Laravel/PHP helper for translating Akeneo product attributes and attribute values across locales, so a multilingual catalog can be maintained from your application instead of by hand in the PIM. It targets developers managing product data for multiple channels and locales who want a simple, code-driven workflow. The public documentation is thin, so expect to read the source and run a short spike before depending on it.
- How do I install akeneo-product-translation in a Laravel app?
- Install it with Composer (composer require piotrmus/akeneo-product-translation) and pin the exact version you have evaluated, for example 0.2.2, rather than floating on ^0.2. Laravel package auto-discovery should register the service provider, and any publishable config or migrations would be exposed through the usual vendor:publish command. Verify provider registration, config keys and migrations in a local environment before rolling it out.
- Which Laravel and PHP versions does it support?
- The package is a Laravel/PHP library, but the supported Laravel and PHP version matrix is not stated in the published metadata supplied for review. Do not assume support for the newest Laravel major; check the composer.json constraints in the repository and confirm they are enforced in CI. Testing on your exact Laravel and PHP combination is the only reliable answer until that matrix is documented.
- Is this package stable enough for production use?
- It is a pre-1.0 (0.x) release, so there is no backward-compatibility contract and a minor bump can break your integration without a deprecation runway. The release evidence available is a single line of metadata for v0.2.2, which is a thin signal for test coverage and release engineering. A reasonable approach is to pin the exact version, wrap it behind a small internal service, and treat upgrades as reviewed changes rather than routine bumps.
- What changed in version 0.2.2 of the package?
- The only published note is a one-line entry describing a fix to an ACL resource code, with no diff, README detail or changelog context available in the review material. Review the diff between 0.2.1 and 0.2.2 directly in the repository rather than relying on the changelog. Establish whether the fix changes behavior in a permissive or restrictive direction before deciding whether the upgrade is routine or urgent.
- Do I need an Akeneo PIM instance or API credentials to use it?
- The package works with Akeneo product attributes and values, so in practice you need access to catalog data, typically through an Akeneo PIM instance and its API or an existing local copy of that data. Exact credential and configuration requirements are not documented in the material available, so confirm the connection settings in the source or config file. Plan for a sandbox Akeneo environment to test translation flows safely.
- How does it handle locales and channels for multilingual catalogs?
- The package is built around Akeneo's locale and channel model: attributes can carry values per locale and per channel scope, and the package helps you translate those values across locales. Typical use is filling translations for a new locale or channel without manually editing every product in the PIM. Confirm how it treats empty values, fallback locales and scope-specific attributes in your own catalog before relying on it for bulk operations.
- How should I test this package in my Laravel application?
- Write integration tests around the paths you actually depend on: translating an attribute value, handling a missing translation, and any permission or resource-code checks if you use them. Include negative cases, not only happy paths, because the recent release note mentions an ACL resource code fix. Run the tests against a fixture catalog that mirrors your real locales and channels.
- How does it compare with other Akeneo translation tools and Laravel translation packages?
- Most alternatives fall into two groups: PIM-side translation workflows or connectors, and generic Laravel translation packages that know nothing about Akeneo attributes or channels. This package sits in between by targeting Akeneo product attributes and values inside a Laravel codebase, which is useful if your catalog operations already live in PHP. Evaluate it alongside your existing Gate/Policy or permission model so you do not end up with two parallel sources of authorization truth.
- How is the package maintained and how should I plan upgrades?
- The evidence available is a single 0.x release line, so commit cadence, maintainer count and issue response times should be checked on the repository before adoption. Pin the exact version in composer.json, read the diff of each release, and keep a changelog of your own integration points. If the package becomes load-bearing, consider a thin internal abstraction so you can swap implementations later.