- What does typicms/translatablebootforms do?
- It is a Laravel package that provides form model binding for translated fields. It integrates TypiCMS translatable models with BootForms so you can build Bootstrap-styled forms for editing multilingual attributes with minimal setup.
- How do I install typicms/translatablebootforms?
- Install it with Composer using composer require typicms/translatablebootforms. You also need BootForms and a TypiCMS translatable model setup in your application. Check the repository README for any service provider registration or configuration steps.
- Which Laravel versions does typicms/translatablebootforms support?
- The provided overview does not list specific Laravel version constraints. Check the package composer.json and README on GitHub to confirm compatibility with your Laravel release. Because it depends on BootForms and TypiCMS packages, match all dependency versions and test before upgrading.
- How does it integrate with TypiCMS translatable models?
- The package hooks into the translation relations of TypiCMS translatable models so BootForms can bind values for each locale. You typically pass the model and translated attribute names to the available BootForms helpers. Consult the repository README for the exact method names and signatures.
- Do I need BootForms installed to use this package?
- Yes, BootForms is a core dependency because this package extends its model binding behavior for translated attributes. Install and configure BootForms first, then add this package. Without BootForms, the Bootstrap-styled form helpers will not be available.
- How do I render multilingual fields in a Bootstrap form?
- Use the package binding helpers with your translatable model, then use BootForms to open a Bootstrap-styled form and render inputs for each locale. The package maps translated attributes to those form fields. The repository README shows the exact API and examples.
- Can I use typicms/translatablebootforms outside TypiCMS?
- It is built around TypiCMS translatable models, so using it outside TypiCMS depends on whether your models implement the same translation relations and behavior. You can adapt your models, but you would need to replicate what the package expects. For non-TypiCMS models, a more general translatable package may be simpler.
- How should I test translated form fields in my Laravel application?
- The overview does not describe the package test suite, so check the repository for tests and coverage. In your application, create a translatable model, bind it to a form, and assert that inputs contain the correct per-locale values. Use Laravel testing tools and a test database for repeatable results.
- Is typicms/translatablebootforms maintained and production-ready?
- Check the GitHub repository for recent commits, releases, and open issues to judge maintenance activity. This is a niche integration for TypiCMS and BootForms, so evaluate long-term support for your project. Pin dependency versions in composer.json and monitor updates before relying on it in production.
- What are alternatives to typicms/translatablebootforms?
- You can use BootForms directly with custom binding logic for translated attributes. Laravel built-in model binding works for simple non-translated fields, and packages such as spatie/laravel-translatable can handle multilingual data with custom form components. For TypiCMS projects, this package remains the targeted integration for BootForms.