About the Module
OVERVIEW
Use the CookiePro module to insert an automatically generated cookie banner & preference center script to your website. Simply copy and paste the main script tag provided in your CookiePro account into the module script box – no need to edit your website code.
GETTING STARTED
Sign up for a CookiePro account to retrieve the cookie banner script. We offer different editions, so you can scale your cookie consent needs with your business.
Visit CookiePro.com to get started.
HOW IT WORKS
1. Scan your website and review your cookies categories
2. Style and configure your banner and preference center
3. Block cookies using a tag manager and/or JS Rewrite
4. Copy and paste CookiePro script into Drupal module
5. Save the configuration to publish the cookie banner
FEATURE HIGHLIGHTS
CookiePro is the most mature and trusted cookie consent tool that is purpose-built for compliance with GDPR, ePrivacy and IAB framework.
- Automatically scan and categorize cookies on your website
- Customize your cookie banner and preview before publishing
- Configure consent models by geolocation (Show only in EU)
- Respect prior consent and Do Not Track browser settings
- Granular preferences center and ability to withdraw consent
- Complete records of consent to demonstrate compliance
- Generate and maintain an always up-to-date cookie policy
- Audit website for changes through scheduled website scans
- View previously published versions saved in a script archive
- Leverage built-in templates with multilingual support (50+)
Project Page
https://www.drupal.org/project/cookiepro
Git instructions
git clone --branch 7.x-1.x https://git.drupal.org/project/cookiepro.git
PAReview checklist
https://pareview.sh/pareview/https-git.drupal.org-project-cookiepro.git-...
Comments
Comment #2
avpadernoThank you for your contribution! I added the PAReview checklist. Reviewers will soon check the code and report here what they found out.
If you still haven't done it, please check what reported from the PAReview checklist. There could be some false positives; be careful of not changing code that should not be.
Notice that shared accounts cannot be used to commit code in drupal.org Git repositories.
Comment #3
cookiepro commentedHi kiamlaluno, Thanks for the comment. I've made some changes based on the PAReview checklist and committed them. I'd appreciate any feedback from you/the other reviewers.
Thanks!
Comment #4
cookiepro commentedComment #5
klausiThanks for your contribution!
Review:
* cookiepro_process_html(): Any reason why you don't use the standard way to add Javascript in Drupal 7? Usually #attached is used in a render array in hook_page_build(). See https://www.drupal.org/docs/7/api/javascript-api/managing-javascript-in-... . Then JS aggregating modules can pick that up? Or do you want to avoid that on purpose? Please add a comment in code.
* "'#value' => 'Save Configuration',": all user facing text must run through t() for translation.
Otherwise looks good to me!
Comment #6
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.