- Is rgsystemes/olark-bundle a Laravel package?
- No. It is a Symfony bundle registered through Symfony's bundle and kernel model. It ships no Laravel service provider, no config publish tag, no facade, and no Laravel version constraint, so it will not be auto-discovered by Laravel. Treat it as a framework mismatch for a Laravel codebase.
- How do I install and register the Olark bundle?
- You install it with Composer and then register the bundle in your Symfony bundles.php or kernel, after which you set your Olark site ID in bundle configuration. The Twig integration renders the chat snippet without hardcoding JavaScript in templates. In Laravel there is no equivalent registration step, which is the first sign the integration does not fit.
- Does it support Laravel 10 or Laravel 11?
- There is no evidence of Laravel support and no Laravel version constraint in the package metadata. The package targets Symfony's bundle registration and Twig rendering model, not Laravel's service container or Blade. A Laravel 10 or 11 application should not expect this to work as a drop-in dependency.
- How do I configure the Olark site ID?
- You define the Olark site ID and widget options in the bundle configuration rather than editing templates. That keeps the account key and options environment-aware instead of scattered across views. In a Laravel app the equivalent is a single config entry plus a Blade partial that emits the snippet.
- Can I enable or disable Olark chat per environment?
- Yes, the bundle is designed to let you enable or disable chat per environment through configuration. That is useful for keeping live chat off in local and CI environments. A Laravel implementation can match this with a simple config or environment check around the Blade include.
- Does the bundle handle GDPR or cookie consent for Olark?
- No. The bundle only injects Olark's third-party JavaScript, which can set cookies on page load or interaction. Consent gating under GDPR or CCPA, plus chat transcript retention terms, remain your responsibility. Wrap the snippet behind your existing cookie consent mechanism and load it only after opt-in.
- Does it support Symfony 6 or Symfony 7?
- The only framework currency change in v2.0.3 was added Symfony 5.4 support, and Symfony 5.4 has reached end of life. There is no visible evidence of Symfony 6.x or 7.x readiness. If you are on a modern Symfony release, verify compatibility before pinning the package.
- What is the best alternative for a Laravel application?
- Build the Olark embed natively: add a config entry for the account ID, include a Blade partial in your layout, and gate the script behind your cookie consent handler. That is roughly fifty lines and keeps the integration inside your own test and release cadence. It also removes a framework-mismatched transitive dependency.
- Can I call the Olark JavaScript API, such as identify or chat events, with this bundle?
- The package appears to focus on configuration and snippet injection, and the supported Olark API surface is not documented. It is unclear whether it exposes runtime hooks like identify or event listeners, or just the embed. If your product needs API calls, add a small JavaScript module of your own rather than assuming the bundle covers it.
- Is the package actively maintained, and what changed in v2.0.3?
- v2.0.3 is a housekeeping patch: a brand-name correction and Symfony 5.4 support, with no new features or breaking changes. Maintainer depth looks thin, with two first-time contributors, one of them an AI agent whose compatibility pull request was merged. That suggests low human review bandwidth, so read the 2.0.0 diff before adopting or upgrading.