Weave Code
Cookies Regulation Bundle Laravel Package
rich-id/cookies-regulation-bundle
A Symfony bundle for cookie regulation and GDPR consent management. It helps add configurable cookie consent banners and preference controls so applications can collect, store, and respect user consent. Suitable for projects needing compliance-ready cookie notices.
A bundle to easily manage your trackers and the consentement of your users to fit the RGPD standard
Frequently asked questions about Cookies Regulation Bundle
- What is rich-id/cookies-regulation-bundle used for?
- It is a Symfony bundle for cookie consent management and GDPR-style compliance. It provides a consent banner, granular cookie category preferences, consent persistence, and configurable bundle settings with Symfony service and Twig integration.
- Does rich-id/cookies-regulation-bundle work with Laravel?
- The provided documentation describes it as a Symfony bundle, not a Laravel package, and there is no stated Laravel version support matrix in the context. Composer installation mechanics are straightforward, but Laravel integration would require verifying PHP constraints and whether the Symfony service and Twig integration can be bridged or adapted.
- How do I install rich-id/cookies-regulation-bundle?
- Install it as a Composer dependency with composer require rich-id/cookies-regulation-bundle, then follow the bundle's README for Symfony bundle registration and configuration. The provided excerpt does not include exact registration or config steps, so verify those before adoption. Because v0.2.1 is pre-1.0, install it in a throwaway branch or scratch Symfony skeleton first.
- What changed in rich-id/cookies-regulation-bundle v0.2.1?
- The only documented change in v0.2.1 is a release note reading Accesibility (sic). There is no scope, linked PR, migration note, or changelog entry in the provided evidence. You cannot tell whether it touches Twig views, validation markup, form helpers, published config/assets, or translations without inspecting the diff.
- Is rich-id/cookies-regulation-bundle production ready?
- Based on the provided evidence, production readiness is not established. v0.2.1 is a pre-1.0 release with a one-word release note, no test coverage signal, and no maintainer count or release cadence data. Treat it as an evaluation candidate and run a limited spike with snapshot tests before using it in a real service.
- How does cookie consent persistence work in this bundle?
- The bundle provides consent persistence so visitor choices are remembered across requests. The provided context does not specify whether persistence uses cookies, session storage, or another mechanism. Check the bundle configuration and source to confirm storage behavior and any retention or expiry settings.
- Can I customize the cookie consent banner design and categories?
- Yes, the bundle is described as configurable via bundle settings to match your policy and design. It also supports granular preferences so visitors can accept or reject cookie categories. Verify the published Twig templates and asset publishing behavior, because accessibility-related markup changes can affect your CSS selectors and JavaScript handlers.
- What accessibility risks should I check before adopting this bundle?
- Accessibility fixes commonly change DOM structure, add ARIA attributes, or alter focus order. Those changes can conflict with your own CSS selectors, JavaScript event handlers, or snapshot tests. The v0.2.1 note suggests accessibility work, but the context provides no conformance target or automated coverage such as axe-core or pa11y, so render affected screens and compare DOM output.
- What are alternatives to rich-id/cookies-regulation-bundle for cookie consent?
- The provided context does not name specific alternatives. Evaluate other Symfony or Laravel cookie consent packages and hosted consent management platforms against your needs. Compare supported PHP/Laravel matrix, maintenance cadence, test coverage, accessibility conformance, and consent storage before choosing.
- How should I test or evaluate this package before using it?
- Pin and install v0.2.1 in a throwaway branch or scratch Symfony skeleton, then read the source and diff any published assets or views. Render affected screens and compare DOM output with snapshot tests enabled, and verify PHP constraints, framework major support, and peer dependencies. Run this as a short spike and have the evidence reviewed before adoption.
Weaver
How can I help you explore Laravel packages today?