- Is stefpe/sp-consent-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle that provides a GDPR-compliant cookie and consent banner built on Symfony Live Component. There is no Illuminate-only integration layer, so in a Laravel application you would be relying on the Symfony component layer Laravel already consumes rather than on a native Laravel service provider. That makes stack fit a real question rather than a drop-in install, so validate Composer resolution against your target Laravel version before planning adoption.
- How do I install stefpe/sp-consent-bundle with Composer?
- Install it with composer require stefpe/sp-consent-bundle, then register the bundle in your Symfony bundle configuration and ensure Live Component wiring is enabled. Because the package is pre-1.0, pin an exact version such as 0.2.0 instead of a floating ^0.2 range. After installing, run your existing test suite and watch for transitive deprecation notices coming from the Symfony component majors it pulls in.
- Which Symfony and PHP versions does stefpe/sp-consent-bundle 0.2.0 require?
- The 0.2.0 release is scoped almost entirely to Symfony 8 compatibility, and Symfony 8 raises the PHP floor to 8.4, which is above the PHP 8.2 baseline for Laravel 11 and 12. The detail that decides everything is whether composer.json widened the allow-list to ^7.0|^8.0 or replaced it with ^8.0 only. Widened constraints are a low-risk unlock for existing adopters, while a Symfony-8-only constraint hard-couples the package to PHP 8.4 and above.
- Will stefpe/sp-consent-bundle conflict with my Laravel application dependencies?
- It can. Laravel pins its own Symfony component ranges, so a bundle requiring Symfony 8 components cannot be co-installed with a Laravel release that still pins Symfony 7. The conflict usually surfaces as an opaque Composer solver error rather than a clean unsupported message. Run composer why-not or a dry-run install against a representative application first so dependency problems stay out of your shared branch.
- How do I define consent types and check granted permissions with this bundle?
- You define your consent types in configuration, the banner collects opt-ins from users, and the bundle stores them through a configurable storage backend. You then check whether a permission is granted from templates or from services before loading non-essential cookies or scripts. Take the exact service IDs and template helpers from the bundle documentation, since the API is still pre-1.0 and not stability-guaranteed.
- Where does the bundle store collected consent, and can I change the storage?
- Opt-ins are persisted through configurable storage, so you can point the bundle at the persistence layer that fits your application instead of being locked into one default. That matters for GDPR work, because you need an auditable record of what each user consented to and when. Confirm the storage adapter you intend to use appears in the bundle configuration reference before building on it.
- Does the bundle render a cookie banner I can style and override?
- Yes, the consent banner is delivered as a Symfony Live Component, so it renders server-side and can be overridden with your own templates and styling. Template overrides follow standard Symfony bundle and Live Component conventions rather than a bespoke theming API. Verify behavior against your specific Symfony version, since component and template handling can differ between the 7.x and 8.x lines.
- Is stefpe/sp-consent-bundle enough to make my site GDPR compliant?
- It supplies the mechanics: defined consent types, a banner, stored opt-ins, and permission checks callable from templates or services. It does not make you compliant on its own, because compliance also depends on what you load before consent, how you categorise cookies, and how long you retain consent records. Treat the bundle as the plumbing and review your actual consent flow against your own legal requirements.
- How should I pin and test stefpe/sp-consent-bundle before upgrading to 0.2.0?
- Pin an exact version rather than a floating ^0.2 range, because at 0.x there is no backward-compatibility guarantee and a dependency-constraint change this size counts as a break. Read the composer.json diff against 0.1.x, run a dry-run install on a representative application, and deploy to a single non-production service behind your existing test suite. Add feature tests asserting that non-essential cookies and scripts are not loaded until consent is granted, then roll forward.
- Is stefpe/sp-consent-bundle actively maintained and safe for production?
- It is a pre-1.0 package whose 0.2.0 release note is a single line about Symfony 8 compatibility, with no detail on source changes or test coverage. Before production use, check whether 0.1.x remains on a parallel maintenance branch, whether CI proves tests pass against both Symfony 7 and Symfony 8, and whether any deprecated Symfony APIs were migrated. Build an internal matrix of package version, PHP version, Laravel version, and Symfony component line, since at 0.x that matrix is the only reliable integration contract you will have.