- Can I install manuxi/google-reviews-bundle in Laravel with Composer?
- Not idiomatically. It is a Symfony bundle with a Bundle class, DependencyInjection extension, and auto-wired service definitions; Laravel has no bundle or container-extension concept, and the package ships no ServiceProvider, facade, or config publish tag. Composer may fetch the code, but you would have to port the service and configuration into Laravel yourself.
- How do I install and configure it in a Symfony or Contao project?
- Install it with Composer, enable the bundle in your kernel or Contao setup, then configure the Google Place ID and API credentials. The bundle exposes a content element or module for placement and supports template overrides. Confirm the exact config keys and cache settings against the package README and your Symfony version.
- Does this package support Laravel 10 or Laravel 11?
- There is no Laravel support in the package as described. It has no Laravel service provider, facade, or publishable config, and its services are designed for Symfony's container. A Laravel 10 or 11 app would need a custom port, likely using the Http facade and a small DTO mapping layer.
- How does the bundle cache Google Places reviews to reduce API calls?
- It includes built-in caching so review responses can be reused instead of calling the Google Places API on every request. The cache is intended to keep social proof current while limiting quota usage and latency. You should verify the cache adapter, TTL, and invalidation behavior in the code or README for your Symfony setup.
- Which Google Places API endpoint does this bundle call?
- The provided assessment says this is unverified in v1.0.2. The package likely still targets the legacy maps.googleapis.com/maps/api/place endpoint, and nothing in the release notes indicates a move to Places API (New) at places.googleapis.com/v1. Inspect the client code or diff the tags before relying on it.
- What review data can I display with manuxi/google-reviews-bundle?
- It exposes reviewer, rating, review text, and date so templates and content elements can render testimonials and star ratings. Template overrides let you customize the markup for your site. The package is built around Google Places reviews, so displayed content depends on what the API returns for your Place ID.
- Is v1.0.2 a safe upgrade for manuxi/google-reviews-bundle?
- Treat it as unverified. The release notes are content-free, the tag numbered 1.0.2 is labeled Initial release, and there is no changelog describing features, breaking changes, dependency bumps, or endpoint migration. Diff the v1.0.2 tag against the prior March 2021 state before upgrading.
- Does it support PHP 8.2/8.3 and Symfony 6/7?
- No evidence in the v1.0.2 release notes confirms modern PHP or Symfony support. There are no stated PHP 8.2/8.3 constraints, Symfony 6/7 constraints, or Guzzle major-version bump mentioned. Check composer.json and run the test suite in a disposable project before assuming compatibility.
- Is manuxi/google-reviews-bundle actively maintained and widely used?
- Community validation is weak: roughly 2 stars, no visible dependents, and no clear issue triage. A release published into silence is not adoption, and the content-free notes make future version bumps hard to assess. For a Laravel team, this argues for treating the code as a reference implementation rather than a dependency.
- What are the alternatives for showing Google reviews in Laravel?
- You can call the Google Places API directly with Laravel's Http facade and map the response into a DTO or view model, which is roughly a day of work. You can also link out to Google or embed a Google-provided widget, subject to attribution and caching rules. If you need a package, choose one with explicit Laravel support, a service provider, publishable config, and recent maintenance.