- How do I install Filament Consent Control in a Laravel Filament app?
- Install it with Composer using mmoollllee/filament-consent-control, then publish the package assets and configuration with the vendor:publish commands described in the README. Register ConsentControlPlugin in your Filament panel provider. The package supports PHP 8.2+, Laravel 11.28+ or 12, and Filament 5. Installation is inert until you opt in to its features.
- Which Laravel and Filament versions does filament-consent-control support?
- The package targets PHP 8.2 or newer, Laravel 11.28+ or Laravel 12, and Filament 5. The Laravel floor is a specific patch level rather than 11.0, so panels on Laravel 11.0 through 11.27 are not supported. Confirm the requirements before adding it to an older Laravel 11 application.
- Why does filament-consent-control require Laravel 11.28 or higher?
- The assessment notes that a patch-level minimum usually signals reliance on a specific mid-cycle fix, but the README excerpt does not identify which fix is required. The practical effect is that Laravel 11.0 to 11.27 panels are blocked even though they are otherwise Laravel 11. Ask the maintainer which change is needed and what fails below 11.28 before planning an upgrade.
- Is Filament Consent Control enough for GDPR compliance?
- It provides configurable cookie and privacy consent banners, preference controls, and content blocking for Filament panels, which helps with GDPR-related UI requirements. However, the assessment says it does not appear to handle consent record-keeping or audit logs, so provable consent may require your own implementation. You also need an editorial policy because raw HTML pasted into the same field is not inherently gated.
- How does content blocking work in Filament Consent Control?
- The package uses the blocked-markup data-src pattern: embedded content stays inert in the DOM until the consent-control runtime hydrates it after consent. The Filament editor action helps authors create gated embeds, and the npm runtime remains the source of truth for gating behavior. Raw HTML source paste or legacy content in the same field is not automatically gated.
- Do I need the consent-control npm runtime to use this Filament plugin?
- Yes. The stack has three layers: the consent-control npm runtime in the browser, the laravel-consent-control PHP integration that is pulled automatically, and this Filament package as the admin surface. The Filament plugin does not replace the runtime; it provides the panel UI and editor tools. The README's single-config-file approach still applies to the underlying runtime.
- Can I use filament-consent-control in a multi-tenant Filament panel?
- The assessment flags multi-tenant behavior as an open question and does not confirm whether settings are global, per-panel, or per-tenant. The README excerpt does not clarify this either. Test the settings isolation in a staging tenant before relying on it in a multi-tenant panel.
- How do I test that cookie consent gating actually blocks embeds?
- The assessment notes there is no stated CI or test coverage, so you should verify gating manually in a staging panel. Load a page with a gated embed and confirm the iframe or script is absent or inert before consent, then confirm it hydrates only after acceptance. Also test raw HTML pasted into the editor and consent withdrawal, since those are the likely bypass and re-blocking gaps.
- Is filament-consent-control production ready?
- It is a v0.1.0, single-maintainer, pre-1.0 package, so minor releases may include breaking changes. The main technical risk is its coupling to the young Filament 5 Schema API, which can break on Filament patch releases. Adoption risk is lower because the plugin is an optional admin layer, but consent gating is a legal control and deserves explicit testing.
- Does Filament Consent Control handle consent withdrawal and re-block content?
- The assessment lists consent withdrawal as a key question for the maintainer: it is not confirmed whether the runtime re-blocks already-hydrated iframes in an open page. The npm runtime is described as the source of truth for gating behavior, so withdrawal handling depends on that layer. Test withdrawal explicitly before treating the package as a complete consent control.