8.1.2
September 25th, 2023
What's fixed
- Fixed an issue where "toggle by default" setting was causing consent groups to always be checked. #77 #78 by @duncanmcclean
8.1.1
August 3rd, 2023
What's fixed
- Fixed handing of Vite assets in
{{ cookie_notice }}tag for some sites #75 #76 by @duncanmcclean
8.0.0
April 28th, 2023
7.1.0
January 7th, 2023
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-noticewouldn'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
6.0.2
October 14th, 2022
6.0.0
September 26th, 2022
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
5.2.0
June 15th, 2022
5.1.0
February 26th, 2022
What's new
- Statamic 3.3 support
Breaking changes
- Dropped support for Statamic 3.0 and Statamic 3.1
5.0.8
January 22nd, 2022
5.0.7
August 24th, 2021
What's fixed
- Fixed issue with
hasConsentif 'cookie notice cookie' does not exist #45
5.0.4
July 11th, 2021
What's fixed
- Fixed bug in new update script I added to display warnings when updating to v5.
5.0.3
July 11th, 2021
What's new
- When upgrading to v5, you'll now get warnings about breaking changes if they affect you.
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.
5.0.0
July 11th, 2021
⚠️ This update contains breaking changes.
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
{{ if {cookie_notice:hasConsented} }}
<!-- has consented to something -->
{{ /if }}
{{ if {cookie_notice:hasConsented group='Marketing'} }}
<!-- marketing scripts -->
{{ /if }}
Now
if (window.cookieNotice.hasConsent()) {
// has consented to something
}
if (window.cookieNotice.hasConsent('Marketing')) {
// marketing scripts
}
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.
3.0.6
February 18th, 2021
- Fix Fix checkbox toggle when user has not consented #26
- And updated the test suite and some of the documentation.