Weave Code
Akeneo Extension Laravel Package
textmaster/akeneo-extension
The TextMaster extension for Akeneo integrates professional translation services into your PIM workflow, so teams can send product content for localization and receive translated content back in Akeneo, simplifying multilingual catalog management and reducing manual handoffs.
The TextMaster Akeneo Extension connects Akeneo PIM with TextMaster’s professional translation and copywriting platform. It lets teams send product content for localization directly from Akeneo, manage translation projects, and import completed translations back into the PIM—streamlining multilingual catalog workflows.
- Send product attributes and locale content to TextMaster
- Track translation project status from Akeneo
- Automatically import completed translations
- Configure API credentials and project settings
- Support multiple locales and attribute groups
Frequently asked questions about Akeneo Extension
- What does textmaster/akeneo-extension do?
- It integrates TextMaster.com with Akeneo PIM so teams can send product attributes and content out for professional translation, track translation projects, and bring localized product data back into Akeneo from a single workflow. In practice it replaces manual export, email, and re-import steps with a connected translation pipeline. It is aimed at catalogue teams managing multi-locale product data rather than at general application string localization.
- Is textmaster/akeneo-extension a Laravel package or an Akeneo extension?
- It is an Akeneo PIM extension that translates content via TextMaster.com, not a typical Eloquent-style Laravel package. Its Laravel-adjacent relevance comes from shared PHP and Doctrine tooling, since the v4.0.2 release touches Doctrine schema configuration for nullable timestamps. The supplied context does not document a Laravel service provider or Facade, so treat it as an Akeneo-side integration first.
- How do I install textmaster/akeneo-extension with Composer?
- Install with Composer using the package name textmaster/akeneo-extension, then enable or register the extension inside your Akeneo application as described in the repository README. The README excerpt was not included in the supplied context, so confirm the exact registration steps and TextMaster API credentials against the repository itself. Run composer update in a development branch and execute your test suite before promoting the change.
- Which Laravel and PHP versions does textmaster/akeneo-extension support?
- The supplied context does not include a composer.json manifest or a documented version matrix, so the supported Laravel and PHP versions cannot be confirmed from it. Check the require constraints in the repository manifest and the Akeneo version you are running before upgrading. Also verify the installed doctrine/dbal major version, because nullability configuration keys and semantics have shifted across DBAL releases.
- What changed in version 4.0.2 of the package?
- Version 4.0.2 is a narrow configuration change that allows Doctrine's schema configuration to treat created_at and updated_at as nullable. That aligns the package with Laravel's long-standing convention that timestamp columns may be nullable, and it mainly affects schema introspection and diffing through doctrine/dbal rather than runtime ORM behavior. No migration requirement, API surface change, or deprecation is called out for the release.
- Will upgrading to 4.0.2 make my existing created_at and updated_at columns nullable?
- It can affect generated schema diffs if your database currently defines those columns as NOT NULL and you use Doctrine-backed schema tooling. A migration or schema-update command could then propose making the columns nullable, which is usually benign but is still a schema change that needs review. Run a schema diff or migration dry-run in a development branch and inspect the SQL before promoting.
- Is doctrine/dbal a required or optional dependency?
- The provided context does not confirm whether doctrine/dbal is a runtime requirement, a dev dependency, or an optional integration. That distinction matters, because it determines whether the nullable timestamp configuration affects every consumer or only those using Doctrine schema tooling for column changes. Read the require and require-dev sections of the package manifest before you upgrade.
- How should I test the upgrade before deploying to production?
- Pin the current version, upgrade in a development branch, and run the full test suite. Then execute the schema-diff or migration dry-run command to confirm no unexpected ALTER TABLE statements are generated. If the diff is clean, promote through staging to production; that schema-diff gate is the meaningful verification step for this release, since no data migration is implied.
- Does the change affect indexes, unique constraints, or timestamp ordering?
- The release note covers only nullability in Doctrine's schema configuration and says nothing about indexes, unique constraints, or ordering assumptions on timestamp columns. If your schema relies on those columns in constraints or sort order, verify the behavior explicitly in your own environment. A schema diff is the quickest way to reveal any unintended changes.
- Are there alternatives to textmaster/akeneo-extension, and is it maintained?
- The supplied context does not list comparable Akeneo translation connectors, so alternatives cannot be named reliably here; review the repository activity and release history before adopting it. Assess it against your Akeneo version, required locales, and whether TextMaster is your translation vendor. Because the evaluation is based primarily on a single patch release note, confirm maintenance cadence and support terms directly with the maintainers.
Weaver
How can I help you explore Laravel packages today?