Weave Code
Languagechooser Bundle Laravel Package
kunstmaan/languagechooser-bundle
A Symfony bundle from Kunstmaan that provides a language chooser for switching between available locales in Kunstmaan-based applications. Small, focused, and easy to integrate into existing CMS setups.
A Symfony bundle that adds a language chooser to multilingual websites built with the Kunstmaan bundle suite. It lets visitors switch between configured locales and integrates with Symfony's locale and routing system.
- Drop-in language switcher for Kunstmaan-based sites
- Works with Symfony locale and localized routes
- Renders a ready-to-use chooser via Twig
- Configurable list of available languages/locales
Frequently asked questions about Languagechooser Bundle
- Can I use kunstmaan/languagechooser-bundle in a Laravel application?
- No, not directly. kunstmaan/languagechooser-bundle is a Symfony bundle built for the Kunstmaan CMS, not a Laravel package. It has no Laravel service provider, facade, auto-discovery, or config publishing path, so you would need a Symfony bridge or a native port. For Laravel, implement locale switching with middleware, configuration, and route prefixes or domains.
- Is kunstmaan/languagechooser-bundle a Laravel package?
- No. It is a Symfony bundle that adds a language chooser to multilingual sites and integrates with the Kunstmaan CMS. The repository is a read-only subtree split of the KunstmaanBundlesCMS monorepo. Treat it as a Symfony component, not a Composer package for Laravel.
- Does kunstmaan/languagechooser-bundle support Laravel 10 or Laravel 11?
- There is no documented Laravel support, including Laravel 10 or 11. The last release was in 2014, so its dependencies reflect Symfony 2-era and old PHP assumptions. Assume incompatibility with current Laravel and PHP versions until a Composer spike proves otherwise. Even then, there is no Laravel integration layer to rely on.
- How do I install kunstmaan/languagechooser-bundle?
- Installation would follow Symfony bundle conventions through Composer, but the package is not designed for Laravel installation. There is no Laravel package metadata, auto-discovery, or publishable configuration. For a Laravel app, do not install it as a dependency; use it only as a reference for language-chooser behavior. If you have a legacy Symfony app, follow that app's bundle registration process.
- How do I configure available locales with kunstmaan/languagechooser-bundle?
- The bundle is built around configured locales and Kunstmaan CMS integration, but the README excerpt provided is empty. Configuration details would come from the Symfony bundle's own docs and service container setup, not Laravel config files. In Laravel, define supported locales in config, detect and persist the choice in middleware, and generate routes with the selected locale.
- Is kunstmaan/languagechooser-bundle maintained?
- No meaningful maintenance signal exists. The last release was 2014-05-22, with 6 stars and 0 dependents on the recorded assessment. That points to an abandoned or effectively unmaintained component with no security-maintenance expectation. Do not adopt it for new Laravel work without planning to own a fork.
- What are the alternatives to kunstmaan/languagechooser-bundle for Laravel?
- Build the capability natively in Laravel. Use locale configuration, middleware for detection and persistence, route prefixes or domains, and a small Blade or JavaScript language chooser. That gives you control over redirect behavior, fallback locale, caching, and SEO. You can also evaluate maintained Laravel localization packages, but confirm current Laravel and PHP support first.
- How should I test language switching in Laravel if I port this bundle?
- Extract the requirements first: supported locales, detection order, persistence rules, redirect behavior, and fallback locale. Then test the native Laravel middleware with feature tests for route prefixes, session persistence, and fallback behavior. Add tests for SEO-sensitive cases such as canonical URLs and hreflang if you emit them. Avoid testing the legacy Symfony bundle internals unless you are maintaining a Symfony application.
- What production risks come with using kunstmaan/languagechooser-bundle?
- The main risks are legacy compatibility and ownership. The 2014 release implies old Symfony and PHP assumptions, possible Composer conflicts, and no security-maintenance expectation. For Laravel, production risks also include incorrect locale detection, redirect loops, cache or session locale bleed, broken canonical or hreflang output, and missing translations. A native Laravel implementation is easier to audit and cache safely.
- Can I use kunstmaan/languagechooser-bundle with KunstmaanBundlesCMS?
- Yes, that is its intended context. The repository is a read-only subtree split of the KunstmaanBundlesCMS and provides the language chooser UI and routing hooks for that Symfony CMS. If you are on a legacy Kunstmaan and Symfony installation, follow the CMS bundle setup. Do not carry it into a Laravel rebuild; isolate the legacy boundary instead.
Weaver
How can I help you explore Laravel packages today?