Weave Code
Gmap Widget Laravel Package
friendsofvictoire/gmap-widget
friendsofvictoire/gmap-widget provides a reusable Laravel widget for rendering interactive Google Maps in Blade views, with configurable markers, zoom, map type, and simple setup for adding location maps to your application.
friendsofvictoire/gmap-widget adds a ready-made Google Maps widget to the Victoire CMS, letting editors drop an interactive map into any page without touching markup. Map settings are configured directly in the widget panel, keeping content changes in the hands of editors.
- Configurable address or coordinates and zoom level
- Optional marker with custom info-window text
- Responsive map rendering via Twig templates
- Simple drag-and-drop insertion in the Victoire editor
- Minimal setup through Composer
Frequently asked questions about Gmap Widget
- Is friendsofvictoire/gmap-widget a Laravel package?
- No. It is a Symfony bundle that provides a Google Map widget for Victoire DCMS, a Symfony-based content management system. There is no Laravel service provider, no config file to publish, no Blade views, and no Eloquent or facade integration. In a Laravel application there is no bundle or kernel registration mechanism for it to hook into.
- Can I install friendsofvictoire/gmap-widget in a Laravel application with Composer?
- Composer may resolve and download it, but there is no integration path into Laravel's rendering pipeline. Making it work would mean either porting the widget logic into a Blade or Livewire component or running a Symfony sidecar just to render a map, both of which are disproportionate to the value delivered. For a Laravel target, building the equivalent component is the realistic route.
- Which Laravel versions does this Google Maps widget support?
- None. The package has no Laravel support matrix because it was never built for Laravel; it targets Victoire DCMS on Symfony with Twig templates. Its Composer constraints pin PHP 5.6/7.0-era and Symfony 2.x/3.x-era components, which will conflict with current Symfony releases. Do not expect it to be installable or testable against modern Laravel or Symfony versions.
- How do I install and configure the Google Maps widget in Victoire CMS?
- The standard path is to require the package with Composer, register the bundle in the Symfony kernel, and then add the map widget as a content block through Victoire's page editor. Configuration happens at the widget level in the editor rather than through a Laravel-style config file. The package is only viable if your application is already running Victoire DCMS on Symfony with Twig.
- Why does the map show a 'For development purposes only' watermark or a blank canvas?
- The last release was December 2016, which predates Google Maps API key enforcement and the 2018 pay-as-you-go billing change. The widget almost certainly instantiates the JavaScript API without a modern key and loading path. Because the failure is client-side API drift, it appears at runtime in the browser rather than at build time.
- Does friendsofvictoire/gmap-widget work with PHP 8 and Symfony 5, 6, or 7?
- There is no evidence of PHP 8 or Symfony 5-7 compatibility, and the Composer constraints point to PHP 5.6/7.0 and Symfony 2.x/3.x. There is also no observable CI or test coverage to confirm behaviour on modern runtimes. Any fork would need Composer constraint updates, PHP 8 compatibility work, and a smoke test before use.
- What are the alternatives to this package for embedding Google Maps in a Laravel app?
- The cleanest replacement is a thin in-house Blade or Livewire component wrapping the Google Maps JavaScript API, which takes roughly a day or two and gives full control over key injection, consent gating, and lazy loading. Leaflet or MapLibre with OpenStreetMap or a commercial tile source removes the Google billing and terms-of-service surface entirely. If the requirement is only a location reference, a static map image with a 'Get directions' link eliminates the dependency.
- Is friendsofvictoire/gmap-widget maintained and safe to use in production?
- It is a single-maintainer project with no release in roughly nine years and no observable security-response process. The technical risk is high and concentrated in abandonment rather than specific defects. Using it in production is only defensible as a short-lived stopgap in a legacy Victoire instance with a dated removal ticket.
- How should I handle Google Maps API keys, billing, and GDPR consent with this widget?
- The 2016 codebase does not address any of these concerns, so you must add them yourself. Externalise the API key into environment or config, add consent gating for third-party embeds in the relevant jurisdictions, and review CSP script-src and frame-src implications. You also need to confirm who owns the Google Maps billing account and the expected monthly map-load volume.
- How can I test this map widget without calling the Google Maps API in CI?
- There is no built-in test coverage, and the widget's failures are client-side JavaScript runtime issues rather than build-time errors. In CI you would need to stub or mock the map script and assert on rendered markup instead of live tiles. A practical approach is a static-map fallback for no-JS and consent-denied cases plus a manual browser smoke test for the interactive path.
Weaver
How can I help you explore Laravel packages today?