- Can I use depa/sulu-google-reviews-bundle in a Laravel application?
- No. Despite being catalogued alongside Laravel/PHP packages, this is a Symfony bundle built for Sulu CMS 3 and it assumes the Sulu/Symfony kernel. Composer may resolve the requirement, but the bundle's service registration, admin routes, Doctrine entity, and Sulu block will not function in a Laravel app. If you are on Laravel, treat it as a reference implementation to port rather than a dependency to adopt.
- What are the requirements for depa/sulu-google-reviews-bundle?
- PHP 8.2+, Sulu CMS 3.0+, Symfony 7.0+, and MySQL 8.0+. MySQL-only is a hard constraint: no Postgres, MariaDB, or SQLite path is documented, which matters for CI pipelines and shops standardized on MariaDB. You also need a Google Places API key and a Google Place ID.
- How do I install the bundle in Sulu CMS 3?
- Run composer require depa/sulu-google-reviews-bundle; with Symfony Flex the bundle is registered in config/bundles.php automatically. Then import the bundle's routes_admin.yaml in config/routes/routes_admin.yaml with the /admin/api prefix. Finally run bin/adminconsole doctrine:schema:update --force to create the depa_googlereviews_reviews table and clear the cache.
- How do I configure the Google Places API key and Place ID?
- The bundle ships empty defaults for GOOGLE_PLACES_API_KEY and GOOGLE_PLACE_ID, so the application boots without them, but the import command aborts with a hint when they are empty. Set the real values in .env.local, or map different environment variables in config/packages/depa_sulu_google_reviews.yaml using the api_key and place_id options. Never commit the key, and decide who owns the Google Cloud project and quota ceiling.
- Why does the bundle only store reviews rated 4 stars or higher, and can I change that?
- The four-star-minimum filter is hard-coded at ingest as an opinionated product decision, not a configurable setting, so changing it means patching the import code or forking the bundle. Review it against your brand, editorial, and legal standards before adoption. Selectively displaying only positive reviews as "our Google reviews" carries consumer-protection exposure in markets such as Germany, so get sign-off rather than discovering it after launch.
- How do I render the Google reviews on the frontend in Sulu?
- The bundle registers a native Sulu block that you map in your page templates, so editors can place and configure reviews through the Sulu content editor without custom controller code. You will still want to style the block to match your theme and decide how attribution is displayed. Verify what the block renders when the API fails or the reviews table is empty, since stale-or-nothing behavior should be a deliberate choice.
- Is there a console command to import or backfill Google reviews?
- The README references an import command that reads the configured API credentials and aborts with a hint when they are empty, but backfill and scheduling behavior should be confirmed in the source. Check whether the command is idempotent, so re-running it does not duplicate rows, and whether it is rate-limit aware before wiring it into cron. There is no scheduling UI shipped with the bundle.
- Does the bundle support multiple locations or multiple Google accounts?
- No. Scope is deliberately narrow: fetch, store, moderate, and render reviews for a single configured Place ID. There is no multi-location or multi-account support, and no publishing of review replies back to Google. Multi-location sites will need custom work, multiple bundle configurations, or a fork.
- Is depa/sulu-google-reviews-bundle production-ready and actively maintained?
- It is single-vendor code from a Berlin digital agency with almost no community signal, so treat it as vendor code you happen to be able to read and budget for the possibility of owning a fork. It is pinned to Sulu 3.0 or later and Symfony 7, so your upgrade cadence depends on the maintainer absorbing Sulu's breaking changes. Check release history, open issues, and whether compiled admin assets ship in the release or require a Node build before committing.
- What are the Google Places API and legal implications of caching reviews in the database?
- Google's Maps Platform terms constrain caching and storage of Places content and prescribe attribution and refresh behavior, so a persistent reviews table with indefinite frontend display is a compliance question, not just an engineering one. Reviewer names, profile photos, and timestamps are personal data even when public, which brings retention, erasure-request, and processor-agreement obligations. Also confirm whether the bundle calls the legacy Places API or Places API (New), since Google is migrating customers and you need a documented migration path.