- Is oro/crm-hangouts-call-bundle a Laravel package?
- No. It is a Symfony 2.x bundle built for the OroCRM and OroPlatform application, not a framework-agnostic Composer library. It has no Laravel service provider, facades, or Laravel config files, and its classes depend on Oro's DI container, ACL voters, and ActivityManager. You cannot composer require it into a Laravel app and use it like a normal package.
- Can I install oro/crm-hangouts-call-bundle in Laravel 10 or 11?
- No, the install will fail at Composer dependency resolution. The bundle targets Symfony ~2.7 and ~2.8 with PHP 5.5 and 7.0-era conventions, while Laravel 10 and 11 ship Symfony 6 and 7 components and require PHP 8.1 or newer. This is a hard Composer conflict, not a soft one, so a short dependency-resolution spike will fail fast and give you evidence for stakeholders.
- What does the Oro CRM Hangouts Call Bundle actually do?
- It integrates the classic Google Hangouts calling experience into OroCRM so users can start a call directly from a Contact or Account record. It then logs the call as an activity on the CRM timeline using Oro's ActivityManager and entity infrastructure. The real value is the CRM context and activity logging, which is exactly why the code is tightly coupled to Oro's data model.
- Does the Google Hangouts API used by this bundle still work?
- No. Google deprecated the classic Hangouts API in 2017 and shut it down; the successor surface is Google Meet via Calendar conferenceData or the Meet REST API. Even if you managed to get the bundle running, the integration target it calls no longer exists, so the feature would fail on the API side. Any new work should target Google Meet instead of Hangouts.
- Is oro/crm-hangouts-call-bundle still maintained?
- No. The last release was on 2016-02-15, more than nine years ago, and the repository has roughly one star and zero dependents. There is no PHP 8 support, no security patching, and no upstream activity. Treat the repository as archived reference material rather than a dependency you can rely on.
- What Laravel and PHP versions can run oro/crm-hangouts-call-bundle?
- It was built for Symfony ~2.7 and ~2.8 and PHP 5.5 and 7.0-era conventions inside an OroPlatform application. It is not designed for Laravel at all, so there is no meaningful Laravel version support. Modern Laravel 10 and 11 apps run Symfony 6 and 7 components on PHP 8.1 or newer, which is incompatible with the bundle's pinned legacy dependencies.
- Can I reuse the OAuth2 code from oro/crm-hangouts-call-bundle in a Laravel app?
- You can read it as a reference for a Google OAuth2 authorization and token-refresh flow, but do not install or shim the bundle. In Laravel, use an existing Google provider such as Laravel Socialite or google/apiclient, and store tokens with Laravel's encrypted casting. Also study how the bundle associated call records to CRM entities to inform your own schema design and UI entry points.
- How do I add Google Meet links to a Laravel CRM instead?
- Build a thin native integration using google/apiclient plus the Google Calendar API conferenceData field, or the Meet REST API, to create a meeting and return a join link. Store OAuth credentials per user or use a service account for workspace-wide behavior, and keep tokens encrypted. Add a Meeting or CallRecord Eloquent model with a polymorphic association to your CRM-like entities, and put creation and status retrieval into a queued job so the request path stays fast.
- What are the production risks of shimming oro/crm-hangouts-call-bundle into Laravel?
- The risk is high. The bundle is unmaintained, targets a dead Google API, and depends on Oro-specific infrastructure that has no Laravel equivalent. The biggest danger is false-positive momentum: a team spending weeks getting it to boot before discovering that the API it calls no longer exists. There is also no security patching, so any code you force into production carries unresolved risk.
- What are the best alternatives to oro/crm-hangouts-call-bundle for Laravel developers?
- The best path is a native Laravel integration: Laravel Socialite or google/apiclient for OAuth, Google Calendar conferenceData or the Meet REST API for meeting links, and an Eloquent model with a polymorphic association for call records. If you need broader video calling, evaluate maintained SDKs for Zoom, Microsoft Teams, or Google Meet instead of legacy Hangouts code. There is no maintained Laravel package that wraps this Oro bundle, so anything you find is likely a fork of dead code.