Weave Code
Translatable Laravel Package
savannabits/translatable
A Laravel package for translating Eloquent model attributes across multiple locales, letting you store and retrieve localized values with locale fallbacks. Useful for multilingual apps that need simple, flexible model translations without heavy dependencies.
Make your Eloquent models and other content translated into multiple languages
Frequently asked questions about Translatable
- How do I install savannabits/translatable in a Laravel app?
- Install it with Composer using composer require savannabits/translatable, then check the package README for any publishable config or migration steps. The release is tied to savannabits/craftable:^7.0.0, so verify dependency compatibility first. Test the install in a sandbox Laravel app before adding it to production.
- Which Laravel and PHP versions does savannabits/translatable support?
- The provided overview and release note do not list supported Laravel or PHP versions. Because v7.0.0 is a new major line positioned with Craftable ^7.0.0, inspect the package composer.json and Packagist metadata for exact constraints. Do not assume compatibility with older Laravel or PHP versions without testing.
- Is savannabits/translatable standalone or does it require Craftable?
- The release note positions this package under savannabits/craftable:^7.0.0, which suggests a Craftable dependency. It is not confirmed whether savannabits/translatable can be used fully standalone. If your app does not use Craftable, run a pilot and review composer.json before committing.
- How does locale fallback work for translated model attributes?
- The package is described as storing and retrieving localized Eloquent values with locale fallbacks. The exact fallback configuration and missing-translation behavior are not documented in the supplied notes. Test fallback locale, empty translations, null values, and cache behavior across at least two locales.
- Can I publish and roll back the savannabits/translatable migrations?
- Publishable config and migrations are not confirmed in the provided release notes. Check the README and package service provider for publish tags, then run migrate and rollback against a disposable database. Review the translation schema and have a data backup plan before production.
- How do I store and retrieve translations for an Eloquent model?
- You make an Eloquent model translatable according to the package docs, store localized values per locale, and retrieve them using the current or configured locale with fallback. The exact trait names, API, and schema are not included in the supplied context. Validate CRUD flows for two locales in a sandbox before relying on the behavior.
- How should I test translatable behavior before production?
- Test installation, config publishing, migrations, translatable CRUD, locale fallback, missing translations, and cache invalidation in a sandbox app. Use a disposable database and add automated tests for at least two locales. Compare results with your existing translation package before any data migration.
- What are the production risks of adopting v7.0.0?
- The main risks are first-release instability for a new major line, dependency conflicts with Craftable ^7.0.0, migration or irreversible schema changes, and incorrect locale fallback in production. Translation tables and locale-aware queries can also affect read performance and indexing. Adopt with a pilot, rollback criteria, and staging validation.
- How do I migrate from an earlier translation package or version?
- The notes do not confirm whether this is a rename, fork, or successor to an earlier package, nor what breaks from v6. Map any old translation schema and data to the new model, rehearse the migration on a disposable database, and back up production data. Avoid bundling this major-version adoption with unrelated framework upgrades.
- Is savannabits/translatable maintained for long-term use, and what alternatives should I evaluate?
- Maintenance impact is elevated because v7.0.0 is the first release of a new major line, with possible follow-up patches and documentation gaps. Support depends on the vendor issue tracker, docs, and release cadence. If you need a standalone or more established translation option, compare alternatives on schema model, fallback behavior, Laravel support, and maintenance before choosing.
Weaver
How can I help you explore Laravel packages today?