- How do I install duncanmcclean/cookie-notice in a Laravel application?
- Install it with Composer, publish the config and views, then include the Blade component in your root layout. For Statamic sites the addon registers natively; for plain Laravel the Blade component is the entry point. Confirm your cookie categories and banner wording before shipping to production.
- Does duncanmcclean/cookie-notice block non-essential cookies or scripts until consent?
- No, based on the provided evaluation it provides a consent notice and preference storage, not a script-blocking layer. You must gate analytics, marketing, and other non-essential tags yourself so they do not run before consent. Treat the package as the UI and state holder, not the full consent enforcement system.
- How do I customize the cookie notice text, buttons, and styling?
- Publish the package config and views, then edit the notice text, buttons, and styling in the published files. The package is designed around a Blade component, so you include it in your layout and override the published views as needed. Keep customizations documented so future package updates are easy to reconcile.
- How does the package remember a visitor's cookie consent?
- It remembers consent with a cookie, so returning visitors can avoid seeing the banner again. Because that state lives client-side, it can be cleared by the visitor or spoofed, and it is not a server-side audit trail. Test the returning-visitor path after upgrades, especially around the widget-flash fix in v10.2.2.
- Which Laravel and PHP versions does duncanmcclean/cookie-notice support?
- The context provided here does not publish a full compatibility matrix. Check the package composer.json for the authoritative Laravel, PHP, and Statamic constraints before installing, and run your test suite after upgrading.
- Can I use duncanmcclean/cookie-notice with Statamic?
- Yes, it is described as a Statamic addon that registers natively for Statamic sites. For plain Laravel applications you use the Blade component instead. If you support both, keep the published config and view overrides in sync.
- Does duncanmcclean/cookie-notice support Google Consent Mode v2?
- The available context does not indicate built-in Google Consent Mode v2 support. The package is described as a notice and preference widget, not a tag manager or consent-mode implementation. If you need Consent Mode signals for EU traffic, plan to wire those signals yourself around the consent state.
- Is duncanmcclean/cookie-notice suitable for Inertia, Vue, or SPA applications?
- It is a better fit for server-rendered Laravel or Statamic sites with Blade or Antlers layouts. In an SPA-first front end, consent state often needs to be shared across a client router and a server API, so this widget becomes one input to a broader consent store. Expect to add your own state management and script gating in that architecture.
- How do I upgrade to duncanmcclean/cookie-notice v10.2.2?
- v10.2.2 is described as a non-breaking patch within the 10.x line, so a normal composer update is the expected path with no config or view migration. The notable runtime change is a widget-flash fix for visitors with stored preferences. After upgrading, verify a returning visitor does not see the banner flash or re-render.
- What should I consider before using duncanmcclean/cookie-notice in production versus a full CMP?
- Use it when you need a lightweight, server-rendered consent notice and can handle script gating yourself. Consider a fuller consent management platform or tag manager if you need server-side audit trails, cross-SPA state, or built-in Google Consent Mode v2. Also weigh single-maintainer risk, CSP compatibility, and accessibility testing.