Weave Code
Filament Translatable Tabs Laravel Package
codedor/filament-translatable-tabs
Filament Translatable Tabs organizes translatable fields into clean, locale-based tabs in Filament forms. Switch languages instantly, keep translations side by side, and reduce form clutter—simple setup for multilingual admin panels built with Filament and Laravel.
At a glance
Frequently asked questions about Filament Translatable Tabs
- What does codedor/filament-translatable-tabs do?
- It is a Filament admin-panel plugin that groups translatable fields into locale-based tabs so editors can switch languages quickly and keep translations side by side. It is aimed at multilingual Laravel applications using Filament, and it primarily reduces form clutter rather than changing how translations are stored. Confirm the README for exact field and API usage in your Filament version.
- How do I install filament-translatable-tabs in a Laravel Filament app?
- Install it with Composer using the codedor/filament-translatable-tabs package name, then register the plugin in your Filament panel provider according to the package README. The v3.1.0 release notes do not call out database migrations or config changes, so backend setup should be light in a compatible Filament app. Validate the install in a non-production branch before rolling it out.
- Which Laravel, PHP, and Filament versions does filament-translatable-tabs support?
- The provided evaluation does not publish a precise Laravel, PHP, or Filament version matrix, so check the package README and composer.json before adoption. It is designed for Laravel applications with Filament multi-locale admin workflows. Pay particular attention to your Filament major version and Tailwind version, because v3.1.0 includes a Tailwind v4 CSS migration.
- Does v3.1.0 of filament-translatable-tabs require Tailwind v4?
- v3.1.0 migrates plugin.css to Tailwind v4, which is a meaningful frontend compatibility signal even though the release is minor. The notes do not explicitly say every consumer must run Tailwind v4, so treat it as a potential consumer-facing compatibility change and test it. If your host app is still on Tailwind v3 or an older Filament version, pin v3.0.0 until you have validated the upgrade.
- How do I upgrade filament-translatable-tabs from v3.0.0 to v3.1.0 safely?
- Upgrade with Composer in a non-production environment, then republish or rebuild assets if your setup requires it and clear view and asset caches. Audit custom CSS that targets tabs, locale badges, or plugin selectors, and run visual regression checks on locale tabs, badges, responsive layouts, RTL, and long locale names. Keep a rollback pin to v3.0.0 until staging and production checks pass.
- Do I need to publish or compile CSS assets after installing filament-translatable-tabs?
- The release note indicates a CSS migration but does not clearly state whether compiled assets are shipped or must be published or compiled by the consumer. Check the package documentation and your Filament theme build pipeline, especially if you publish or override plugin CSS. Missing compiled assets and stale cache busting are common failure modes to verify after deployment.
- Can I customize the locale tabs and badge styling in filament-translatable-tabs?
- You can style the locale tabs and badges through your Filament theme or custom CSS, but avoid relying on undocumented selectors. v3.1.0 includes badge naming changes, so audit any overrides that target locale badge class names. Scope custom CSS carefully to avoid specificity conflicts with the plugin and host app styles.
- Does filament-translatable-tabs work with RTL layouts and long locale names?
- RTL layouts and long locale names are explicitly part of the recommended visual QA checklist for this plugin. The release does not indicate runtime scaling concerns, but frontend layout regressions are possible after the Tailwind v4 CSS migration. Test tabs, badges, responsive breakpoints, and long labels in staging before production.
- What is the rollback path if the new styling breaks my Filament admin panel?
- Pin the package back to v3.0.0 with Composer, republish or rebuild assets if applicable, clear view and asset caches, and verify cache busting on your CDN or static asset layer. Because v3.1.0 is CSS-focused, the rollback is mainly an asset and dependency-version exercise rather than a database rollback. Document the exact steps before upgrading so you can recover quickly if styling regresses.
- What production issues should I watch for after upgrading filament-translatable-tabs?
- Watch for broken tab or badge styling, CSS specificity conflicts, missing compiled assets, incompatible Tailwind build pipelines, locale badge selector changes, RTL or long-label layout regressions, and stale cached CSS after deployment. Verify production CSS build size, cache busting, and CDN or static asset behavior after the Tailwind v4 migration. Triage issues by including Filament version, Tailwind version, package version, and screenshots.
Weaver
How can I help you explore Laravel packages today?