Releases: duncanmcclean/cookie-notice
v5.0.5
Cookie Notice is now compatible with Static Caching!
What's new
- Now compatible with static caching #40
Breaking changes
Assets
All users of this addon will need to re-publish Cookie Notice's assets after updating.
php artisan vendor:publish --tag=cookie-notice-assets
Antlers view
If you've chosen to publish Cookie Notices views so you can edit them (they'll exist in resources/views/vendor
), you will need to re-publish the views and make your changes again. Changes had to be made to support static caching.
php artisan vendor:publish --tag=cookie-notice-views
Checking for consent
Additionally, if you're checking for a user's consent anywhere, you'll need to do this using JavaScript instead of the Antlers tags.
Before
Now
if (window.cookieNotice.hasConsent()) {
// has consented to something
}
if (window.cookieNotice.hasConsent('Marketing')) {
// marketing scripts
}
v4.0.1
v4.0.0
- Refactored view to use Antlers, instead of Blade
- Allow for using globals inside the cookie notice view #27
This release shouldn't be a breaking change if you're coming from v3. However, I've marked it as such in case there are any unintended side affects.
You should be able to continue using your Blade cookie notice views for as long as you like. Or if you like, you could switch it around for Antlers. It really doesn't matter which one you use.
v3.0.6
v3.0.5
v3.0.4
v3.0.3
Contains a bunch of bugfix, mostly to do with vendor publishing.
v3.0.2
- Officially supports Statamic 3 (not beta)
v3.0.1
Small refactor
v3.0.0
Cookie Notice is now compatible with Statamic v3.