Weave Code
Localeswitcher Widget Laravel Package
friendsofvictoire/localeswitcher-widget
A Blade widget for Laravel that renders a ready-made language switcher for your application, letting visitors change the active locale without extra markup or wiring. Drop the component into any view, configure the supported locales, and the package handles the selection UI and locale persistence.
Victoire DCMS LocaleSwitcher widget
Frequently asked questions about Localeswitcher Widget
- Is friendsofvictoire/localeswitcher-widget a Laravel package?
- No. Despite the Composer name and routing label, it is a Symfony bundle for Victoire DCMS, with no Laravel service provider, config file, Blade views, or facade. Composer may autoload classes in a Laravel app, but nothing in Laravel invokes them. Treat it as a Victoire/Symfony component, not a Laravel localization package.
- Can I install this locale switcher widget in a Laravel 10 or Laravel 11 application?
- No. The bundle depends on Victoire and Symfony 2.7-3.x era packages, which conflict with the Symfony 6/7 constraints used by Laravel 9 and later. Composer resolution fails, and using --ignore-platform-reqs leaves you with a bundle that cannot register or render. There is no supported path to run it inside a modern Laravel app.
- What Laravel versions does this package support?
- None. It has no Laravel service provider, no config publish step, no Blade component, and no facade, so it is not a Laravel package at any version. It targets a Symfony kernel with Victoire's widget registry and Doctrine-backed widget entity model. Officially, only a Victoire-pinned Symfony 3.4 and PHP 7.x container is a viable runtime.
- How do I install and configure the locale switcher widget?
- In a Victoire/Symfony 3.x app, you install it with composer require friendsofvictoire/localeswitcher-widget, register the bundle in AppKernel, and enable it in the widget registry. Configuration covers supported locales, labels, ordering, and display, and selection is session-aware to preserve the chosen locale. In Laravel there is no install or configuration path because the package never boots.
- Does this package work with PHP 8 or Symfony 6?
- No. The bundle is built for the Symfony 2.7-3.x generation and depends on Victoire packages from that era. Running it on PHP 8.x or Symfony 6/7 would require patching the bundle and its transitive Doctrine, Symfony, and Twig dependencies. Those dependencies are stale and out of security support, so the upgrade cost and exposure sit with you.
- What is the Laravel-native alternative to this locale switcher widget?
- Build a small in-house Blade component instead. Iterate config('app.supported_locales'), resolve the current route name and parameters, preserve the query string, and emit links with correct hreflang and canonical handling. That is roughly 40-80 lines and gives you full control over routing model, analytics, accessibility, and SEO with no dependency or fork obligation.
- Does the widget generate locale-prefixed URLs or handle localized routing?
- No. It is a selection UI that connects to the host application's localization system and relies on your routes already existing. It does not define URL prefixes, subdomains, query parameters, or cookie-based locale routing for you. In Laravel you would need to design that routing model yourself and have the switcher render links that match it.
- Is this package actively maintained, and is it safe for production?
- It has zero stars, zero dependents, no issue traffic, and no evidence of production use, and upstream Victoire is dormant. The bundle will not run on current PHP or Symfony without patching, and its large, stale transitive dependency surface is a security exposure you would own. For a Laravel product the production risk is high and there is no upstream to notify you of fixes.
- Can I use this widget for an editor-placeable language block in a page builder?
- Only if your page builder is Victoire, because the bundle's value is registering a widget type into Victoire's registry and entity model. In Laravel, model the requirement against the page builder actually in your stack, such as a generic renderable or menu block. Importing Victoire's entity contract to get a language dropdown is not a justified trade.
- What should I check before committing to this package?
- First confirm the target is an existing Victoire/Symfony estate rather than a Laravel app, because the package only makes sense for the former. If Victoire, pin the exact PHP/Symfony versions and confirm who still issues security patches for that stack. Also decide whether you need true editor-placeable widget semantics or just a header/footer switcher, and who owns the fork when an upgrade breaks it.
Weaver
How can I help you explore Laravel packages today?