Cookie Notice Release Notes

What's new

Added a config option to allow changing the cookie-notice.yaml path #83 by @mwagena

9.0.0

May 9th, 2024

In version 9, Cookie Notice has been completely overhauled, with a big focus on making it easier to manage third-party scripts and more flexibility for developers around customizing the consent widget. To upgrade, please follow the upgrade guide.

What's new

Statamic 5 support #79 by @duncanmcclean
A new Control Panel to let clients manage third-party scripts (including Google Tag Manager & Meta Pixel).

What's improved

Improved design on the consent widget
Easier than ever to build custom consent widgets

What's changed

Dropped PHP 8.1 support
Dropped Statamic 4 support
Everything (seriously, it's a big update)

What's fixed

Fixed an issue where "toggle by default" setting was causing consent groups to always be checked. #77 #78 by @duncanmcclean

What's fixed

Fixed handing of Vite assets in {{ cookie_notice }} tag for some sites #75 #76 by @duncanmcclean

What's new

PHP 8.1 support is back! #74

What's fixed

Fixed publishing of Cookie Notice's CSS file

What's fixed

Fixed publishing of Cookie Notice's CSS file

What's fixed

Changed how CSS is being marked as published

What's fixed

Adjusted tag of publishable assets

What's fixed

Moved Pest into require-dev

What's fixed

Fixed Vite build issues once and for all #68 #72 #73

What's fixed

Fix build issues with Vite #66 #67 by @florianbrinkmann

What's fixed

Fixed an issue with Vite assets not being published correctly #65

What's new

Cookie Notice v8 now supports Statamic 4 #61
Now using Vite to build assets internally #60

Upgrade guide

In your site's composer.json file, replace doublethreedigital/cookie-notice with duncanmcclean/cookie-notice
Then, change the addon's version constraint to ^8.0

What's new

Statamic 3.4 Support

What's improved

There's been a few small design changes to the notice
CSS for the notice are now loaded inline, rather than via an external stylesheet (prevents it from not being displayed with some ad-blockers)

What's fixed

Fixed a JavaScript issue when loading the notice for the first time
Fixed an issue where text on 'Manage Cookies' button sometimes wouldn't show
Fixed an issue where the CSS file in public/vendor/cookie-notice wouldn't be included in your site's Git repository

7.0.0

December 29th, 2022

The supported versions of PHP/Statamic/Laravel used alongside this addon have changed, the supported versions are now:

PHP 8.1 & 8.2
Statamic 3.3
Laravel 9

What's improved

You can now click the buttons on the cookie notice widget while the page is still loading #55 #56

What's fixed

Fixed an issue for new users providing consent

What's new

Cookie Notice now has events! You can listen to them to detect consent changes, then trigger the relevant third-party scripts. #54

What's new

The Cookie Notice view is 'translatable' out-of-the-box now #51 #52

What's new

Statamic 3.3 support

Breaking changes

Dropped support for Statamic 3.0 and Statamic 3.1

What's new

The JavaScript code can be included in a different place than the Notice itself #48 #49

What's fixed

Fixed issue with hasConsent if 'cookie notice cookie' does not exist #45

What's fixed

Fixed TailwindCSS classes being purged incorrectly #44

What's new

Support for Statamic 3.2

What's fixed

Fixed bug in new update script I added to display warnings when updating to v5.

What's new

When upgrading to v5, you'll now get warnings about breaking changes if they affect you.

What's fixed

Fixed issue with CSS not being compiled properly

5.0.1

July 11th, 2021

This release resolves an issue in the publish workflow of the previous release. Please review v5.0.0 for the changelog.

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

{{ if {cookie_notice:hasConsented} }}
    #676E95;"><!-- has consented to something -->
{{ /if }}
 
{{ if {cookie_notice:hasConsented group=#89DDFF;">'Marketing#89DDFF;">'} }}
    #676E95;"><!-- marketing scripts -->
{{ /if }}

Now

#89DDFF;">if (window#89DDFF;">.cookieNotice#89DDFF;">.#82AAFF;">hasConsent()) #89DDFF;">{
#89DDFF;">    #676E95;">// has consented to something
#89DDFF;">}
 
#89DDFF;">if (window#89DDFF;">.cookieNotice#89DDFF;">.#82AAFF;">hasConsent(#89DDFF;">'Marketing#89DDFF;">')) #89DDFF;">{
#89DDFF;">    #676E95;">// marketing scripts
#89DDFF;">}

4.0.1

June 15th, 2021

What's improved

The cookie notice will no longer show in Live Preview #42

4.0.0

March 5th, 2021

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.