Components
- Code
- Documentation
- Miscellaneous
- User interface
- Submodule: cookies_facebook_pixel
- Submodule: cookies_filter
- Submodule: cookies_ga
- Submodule: cookies_gtag
- Submodule: cookies_instagram
- Submodule: cookies_ivw
- Submodule: cookies_matomo
- Submodule: cookies_recaptcha
- Submodule: cookies_twitter_media
- Submodule: cookies_video
- Submodule: cookies_asset_injector
Images
Licence
http://www.gnu.org/licenses/old-licenses/gpl-2.0.htmlpermet de créer une interface pour que l'utilisateur choisisse les cookies tiers qu'il veut embarquer.
Release
Covered by Drupal's security advisory policy
Release type : Bug fixes
Covered by Drupal's security advisory policy
Release type : Bug fixes Release type : New features
Covered by Drupal's security advisory policy
Release type : Bug fixes Release type : New features
Description
User consent management module for Drupal 8 and 9.
The module enables existing third-party-integration modules continued to be used in compliance with the GDPR (of course without manipulating their code). It solves the basic problem that when using third-party-integration modules, the user must agree to the use of cookies (according to GDPR) before they are installed.
IMPORTANT: No liability is assumed regarding compliance with the GDPR.
The COOKiES module provides (with the Library Cookies JSR) a fully configurable user interface for user decisions. It also supports out-of-the-box some key third-party integration modules (especially those included in the Thunder distribution):
- Asset Injector
- Google Analytics module
- Google Tag Manager
- IVW Integration <2.4
- reCAPTCHA
- Matomo Analytics
- eTracker Analytics
- Video embed with oembed from core:media module (recommended) or Video Embed Field (iframe, not recom.)
- Twitter media module
- Instagram media module
- Facebook Pixel, support for modules: "Facebook Pixel" (recommended) or Official Facebook Pixel (not recom.)
Further 3rd-party module support
In the near future, some extensions will be available that make programming easier or superfluous for the support of further 3rd party integration modules in COOKiES.
- COOKiES Module Handler covers the handling of Javascript (disable/enable depending on users consent)
- "COOKiES Filter" (by @Anybody & @Grevil) will cover the handling of 3rd party code snippts pasted to the text editor.
Both modules are intended to be transfered to the COOKiES module.
Features
1. Full responsive design.
2. Full translatable by Drupal UI
3. Full accessibility
4. Customizable styling.
4.1. Light: Use CSS-vars to customize colors and some params as described here.
4.2. Heavy: Disable original CSS in the config and start to customize from scatch - or with original SCSS download here)
For developers
For developers, with these Modules above there are some easy-to-understand examples available for integrating further third-party-integration modules into user consent management. It contains code that controls the interfaces and best practices to implement practically any requirement quickly and easily.
Demo starter kit can be found here.
Install:
1. Install module with Composer (alternatively download) and activate it under Admin > Modules (/admin/modules) as you did it many times before.
2. Add the "COOKiES UI" block in the block configuration at Admin>Structure>Blocks (/admin/structure/block) place the block anywhere.
3. Activate additional modules under Admin>Modules (e.g. cookies_ga to support Google Analytics)
Some Configurations
1. Configure the COOKiES module under Admin>Config>System>COOKiES (/admin/config/cookies/config)
2. Users may want to change their cookie preferences. For this reason a "Cookies settings" link in the tools menu is created. Move link to the menu, where you want to place it. (You can create a custom Link very easy with <a href="#editCookieSettings">cookies</a>
)
Important Note
For reasons of performance and in order not to influence the first impression of the page with the cookie banner, a scroll limit is set by default. If your website is not scrollable or your homepage is very short, you should set the sroll limit to zero so that the banner loads immediately.
Possible alternatives
- https://www.drupal.org/project/eu_cookie_compliance
- https://www.drupal.org/project/tacjs
- https://www.drupal.org/project/klaro
- https://www.drupal.org/project/simple_klaro
- https://www.drupal.org/project/cookieconsent
- https://www.drupal.org/project/cookie_content_blocker
- https://www.drupal.org/project/usercentrics_cmp
- https://www.drupal.org/project/cookiebot
- https://www.drupal.org/project/cookiebot_gtm
- https://www.drupal.org/project/cookie_script
Toutes les informations proviennent du site drupal.org