Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Cookie Compliance for WordPress · Version history

Cookie Compliance for WordPress changelog and version history

Latest version
3.1.18
Nov 2, 2026 (7 days ago)
Releases
143
since 2013
In the last year
34
about one every 11 days
Tested up to
WordPress 7.1.4
PHP 7.4 or later

Releases each year

  • 20132 releases
  • 201418 releases
  • 201520 releases
  • 20164 releases
  • 20173 releases
  • 20185 releases
  • 20194 releases
  • 20205 releases
  • 202113 releases
  • 20229 releases
  • 202310 releases
  • 202412 releases
  • 20257 releases
  • 202631 releases

202631 releases

  1. Cookie Compliance for WordPress 3.1.18Latest

    • Fix: On sites using Polylang, Conditional display lists pages in every language, and rules for those pages are kept when you save.
    • Improvement: The plugin now calls the Cookie Compliance web app your dashboard, the name you know it by.

  2. Cookie Compliance for WordPress 3.1.17

    • New: The Overview tab now shows your last 30 days of consent activity, the same charts as the WordPress dashboard widget.
    • New: On connected sites, Cookie Consent lets you set your company’s country, saved to your Cookie Compliance account.
    • Fix: On connected sites, a privacy law’s suggested settings apply when you first select that law. Later saves keep the banner choices you have made.
    • Fix: On the Overview tab, Meta, Microsoft, and Global Privacy Control show as optional when they are off. Global Privacy Control stays recommended for CCPA and other US state laws.
    • Fix: Support now opens in the Admin Portal with this domain already selected.
    • Improvement: Clearer banner and Privacy Consent screens. Standard and Compact appear with the New engine, “Can’t see your banner?” sits with your banner, and Admin Portal links open this site.

  3. Cookie Compliance for WordPress 3.1.16

    • Improvement: Simpler, more reliable privacy policy link. On connected sites, choose your policy page and turn on Sync to use it on your banner; set the link text in the Admin Portal. In Banner Only mode, the policy button always opens your policy.
    • Tested up to WordPress 7.1.

  4. Cookie Compliance for WordPress 3.1.15

    • Docs: Refreshed the plugin page. Older version history now lives in changelog.txt. No change to your banner or settings.

  5. Cookie Compliance for WordPress 3.1.14

    • New: An Overview tab shows your protection status in plain words, your last 7 days of consents, and a one-click fix for anything that needs attention.
    • New: Preview shows your banner even when it would be hidden for you, and says why.
    • Improvement: Tabs are now Overview, Cookie Consent, Privacy Consent and Consent Logs. Laws, languages and Consent Signals (formerly consent mode) sit together on the Cookie Consent tab.
    • Improvement: Compliance evidence follows your live banner and blocking settings, with no scan to wait for. The tracker list is removed, as it only showed trackers added by hand. Blocking is unchanged.
    • Fix: With page caching on, preview, page-builder and JSON requests are no longer cached, so visitors always get the banner. If your cache may hold such a page, purge it once.
    • Security: Account messages, such as sign-in or payment errors, show as plain text, and debug logs no longer store full account replies.

  6. Cookie Compliance for WordPress 3.1.13

    • New: Sites on the classic interface can move to the new admin interface from a card in the sidebar. Your settings, connection and banner stay exactly as they are.
    • New: The new admin interface opens with a “Your banner” panel showing the banner your site really runs — its engine and style — with a quick way to preview it on your site.
    • New: On sites using the New banner engine, you can choose a Standard or Compact banner right from WordPress. Setup now starts with this choice.
    • New: Sites you add from the plugin now start on the New banner engine, the same as sites added in your Cookie Compliance account.
    • Improvement: The new admin interface now includes the Privacy Consent tab and form consent logs, and saves your settings just like the classic screens.
    • Improvement: On multisite networks, Network Administrators can manage network-wide settings from the new admin interface, and each sub-site’s consent records stay private to that site.
    • Improvement: “Revoke consent” is now called “Update consent”, matching your Cookie Compliance account.
    • Improvement: Removed banner templates, so the plugin no longer changes colours set in the Admin Portal. Set colours and position in Admin Portal → Configuration → Design.
    • Improvement: Clearer protection status that shows exactly when your banner is live.
    • Improvement: When your banner engine changes in your Cookie Compliance account, the plugin tells you once and offers to purge your page cache so visitors get the new banner.
    • Improvement: On the Privacy Consent tab, the status card shows one Connection row, and its “Open Admin Portal” button opens this site’s app; a connected site whose last check did not come back shows “Not confirmed” instead of the sign-up offer. Where you enter your App ID and App Secret Key, and on…
    • Improvement: Connect, sign-in and key labels now use the same words as your Cookie Compliance account.
    • Improvement: The status cards are shorter and “Pull latest settings” appears once per page.
    • Improvement: When you sign in to an account that has apps but none for this site, the plugin now asks which app this site should use, or lets you create a new one, instead of creating a new app for you.
    • Fix: In the new admin interface, clearing your App ID and App Secret Key now disconnects the site fully, the same as the classic screens.
    • Fix: On sites with page caching, connecting from the new admin interface now refreshes cached pages after your banner settings arrive, not before.
    • Fix: The Protection tab no longer shows the Threat Intelligence panel, whose news items never changed.
    • Fix: On connected sites, Save WordPress Settings now saves your WordPress settings only. It no longer changes your live banner’s colours, position, opacity or consent behaviour; it still updates the banner’s privacy policy link from your WordPress privacy page.
    • Fix: On sites using CCPA or Other U.S. State Laws, the Do Not Sell link you enter with your laws is now saved to your banner (its default language). An address that is not a full web link is refused and nothing is saved.
    • Fix: In setup, Apply & Finish now applies the languages you selected.
    • Fix: Plan, pricing and language screens now list the same features, limits and discount as the product.
    • Fix: Signing in from a WordPress installed in a subfolder (for example example.com/blog) now connects the app already on that domain, instead of stopping with “Domain URL already exists”.
    • Fix: On new accounts with no app yet, signing in from the plugin now creates the app for your site, instead of stopping with “No apps found”.
    • Fix: On accounts with two-step verification, signing in from the plugin now asks for the verification code instead of connecting with the password alone.

  7. Cookie Compliance for WordPress 3.1.12

    • Improvement: Your site stays connected and protected through a brief network or server problem, rather than waiting for the next scheduled check to recover.
    • Improvement: Banner settings from your account hold steady between checks.
    • Improvement: On multisite networks where the plugin is network-activated but each site keeps its own account, the WP Consent API integration follows that site’s own selected privacy laws.
    • Improvement: On multisite networks, your privacy laws, banner design, visit figures and consent records show up consistently across every screen, and visit-limit warnings reach each site.
    • Improvement: On the Consent Logs screen, records that cannot be loaded are now reported as such instead of appearing as an empty list, and the CSV export does the same — a log with no entries and a log that could not be reached no longer look alike.
    • Improvement: Upgrading to a paid plan now waits for the payment to be confirmed before reporting it. A declined card, or a network problem during checkout, is reported plainly with the reason — previously the upgrade could appear to have gone through and then revert. Connecting a site and adding bi…
    • Improvement: Forms protected by Gravity Forms reCAPTCHA wait for reCAPTCHA to finish loading after a visitor accepts cookies, so the form submits without a reload.
    • Improvement: The Compliance dashboard reports what it can see — which protections are switched on. Turning Autoblocking off is no longer flagged where your selected laws permit it, and a switched-off script blocking engine is called out clearly.

  8. Cookie Compliance for WordPress 3.1.11

    • Fix: Region-specific (geolocation) rules now apply from a visitor’s very first pageview, not just after the plugin’s next scheduled refresh — as long as your settings synced within the last 12 hours.
    • Fix: Free-plan sites now show their real 1,000 visits/month allowance right away instead of 0 right after reconnecting an account or switching back from a paid plan.

  9. Cookie Compliance for WordPress 3.1.10

    • New: Two controls over script blocking on the Configuration tab, where there was one. “Autoblocking” keeps its existing job — holding third-party scripts until a visitor chooses. The new “Script blocking engine” switch turns Cookie Compliance’s blocking off entirely, for every visitor and every reg…
    • Fix: On sites connected to a Cookie Compliance account, a second publish made within about two minutes of the first now reaches your site promptly — handy when you’re adjusting settings and republishing to check the result. What you publish has always been saved correctly; this shortens the wait fo…
    • Fix: On WordPress multisite networks, the settings every site shares — your Cookie Compliance account, banner and blocking list — are now protected, so only a Network Administrator can change them and the whole network stays on the right account. Sites with their own separate account keep full cont…
    • Fix: On Free-plan sites that reach their monthly visit limit, your Autoblocking choice is now remembered while blocking is paused, and applies again the moment the next cycle begins — including if you save other settings in the meantime.
    • Fix: On Free-plan sites, the visit-limit alert now appears only once autoblocking has actually paused — so it no longer warns that scripts may be firing while your Autoblocking setting still reads “On”.

  10. Cookie Compliance for WordPress 3.1.9

    • Fix: On sites that honour Global Privacy Control or Do Not Track, a visitor’s opt-out is now applied as soon as the banner can act on it, instead of waiting for your settings to load.
    • Fix: On sites using Gravity Forms with Google reCAPTCHA, visitors can page through a multi-page form before choosing cookies — only the final submit waits for consent. Since 3.1.5 Next and Previous waited too. Worth retesting if you run a multi-page form.
    • Fix: On those same sites, a visitor who has already accepted cookies is no longer asked to accept again when submitting. They are now told that the form is still loading, or that reCAPTCHA did not load, whichever is the case.
    • Tweak: On those same sites, a developer can switch this compatibility off site-wide with the cookie_notice_gravity_forms_recaptcha_enabled filter. Google reCAPTCHA is still held until a visitor accepts, either way.
    • Fix: On sites with page caching, your caching plugin is now told not to store pages viewed by anyone who can manage the banner. Script blocking is off on those pages, so a cached copy served to a visitor left them unprotected. Most caching plugins honour this; a CDN that ignores your site’s caching…
    • Tweak: On sites connected to a Cookie Compliance account, the requests the plugin already makes now carry a little more about your setup — its version and which features are on, your site’s language, basic diagnostics, which caching or optimisation plugins you use, and whether a Google, Meta or Mic…
    • Tweak: On those same sites, publishing usually pushes your changes out within seconds; the scheduled check behind that now runs twice a day instead of once, halving the wait when a push cannot get through.

  11. Cookie Compliance for WordPress 3.1.8

    • Improvement: On sites running WordPress in a language other than English, the Compliance settings screens can now be translated. Their text was previously fixed in English no matter which language your site used. Translations are supplied by the translation community, so screens stay in English unt…
    • Fix: On sites using reCaptcha by BestWebSoft, the captcha now appears as soon as a visitor accepts cookies, rather than only when they accept within the first few seconds of the page loading. Until they accept, the form says that the captcha needs their consent, instead of reporting a connection pr…
    • Tweak: On sites using Google, Facebook or Microsoft Consent Mode, your signal settings now travel with the page, so those platforms receive them from the first pageview of a visit.

  12. Cookie Compliance for WordPress 3.1.7

    • Rebrand: Plugin renamed from “Compliance by Hu-manity.co” to “Cookie Compliance for WordPress” — one product, of which this plugin is the WordPress half. The plugin’s admin screens, and the name a screen reader announces for the banner, now read “Cookie Compliance” throughout. Your settings, connec…
    • Fix: On sites using Google Consent Mode, the Advertising, Analytics and Functional group controls are replaced by one control per signal, still grouped under those headings. Each changes only its own signal, so Security Storage is no longer reset by another control and no longer reports itself as n…
    • Fix: On sites connected to a Cookie Compliance account, opening Upgrade to Pro after being signed in a day or more now returns you to sign-in, instead of an error that refreshing could not clear.
    • Fix: On sites whose domain was moved to a different Cookie Compliance app or plan, the visit limit now follows the current plan. It is enforced only from recent visit figures, and Sync Config is no longer switched off when the limit is reached — it is what clears it. Google Consent Mode and your co…
    • Tweak: The Compliance settings screen now opens straight away and refreshes from the Admin Portal in the background, instead of showing nothing until that finished. If the refresh cannot complete, it says it is showing your last synced settings, and when they were synced.
    • Tweak: If your consent mode settings change elsewhere while you have the Consent Modes panel open, your unsaved edits are kept and the panel tells you the stored settings have moved on.
    • Tweak: Site Health now reports your plan, cycle visits against your limit, and how old the usage figures are — measured from when they were calculated, not from when this site last pulled them.

  13. Cookie Compliance for WordPress 3.1.6

    • Tweak: On sites managed from both the Admin Portal and the WordPress Protection screen, saving one consent mode setting now leaves the others exactly as you set them.
    • Tweak: On sites using Google, Facebook, or Microsoft consent modes, each signal is now matched to a purpose category — Content Personalization, Site Optimization, or Ad Personalization — so the setting you pick is what the banner sends, and the category names match the Admin Portal. The earlier “Al…

  14. Cookie Compliance for WordPress 3.1.5

    • Fix: On sites using Gravity Forms with Google reCAPTCHA, forms can now be submitted as soon as a visitor accepts cookies — on the same page, with no reload. Previously the submit button could stay in a loading state indefinitely. Visitors who have not chosen yet are now asked to accept cookies, ins…
    • Fix: On sites where visitors sign in — membership sites, online courses, shops — signed-in visitors now get cookie blocking and the correct consent signals to Google, Microsoft and Meta, the same as every other visitor. Previously any signed-in visitor was treated as someone working on the site: no…

  15. Cookie Compliance for WordPress 3.1.4

    • Fix: On sites protected by a security plugin or firewall (such as WordFence), saving your settings after adding Google Tag Manager or analytics code could fail with a “403” error. The plugin now sends that code in a form these tools don’t mistake for an attack, so your settings save normally.
    • Fix: The consent banner now displays and blocks cookies reliably on sites using a JavaScript optimizer — including WP Rocket, Autoptimize, LiteSpeed Cache, SiteGround Speed Optimizer, WP Fastest Cache, and WP Hummingbird’s “Delay JavaScript”. These tools could delay or combine the Cookie Compliance…

  16. Cookie Compliance for WordPress 3.1.3

    • Fix: On sites that use SiteGround Speed Optimizer, LiteSpeed Cache, or Breeze to combine, defer, or minify JavaScript, the plugin now reliably keeps the Cookie Compliance script out of those optimizations — so the banner displays and cookies stay blocked until a visitor consents. These tools could…
    • Tweak: The plugin’s upgrade screen now links you to the Admin Portal to complete a subscription there, with the plan pre-filled. Use it when you need a multi-domain plan, an invoice/VAT receipt, or a payment method other than card — all long available in the Admin Portal; the in-plugin card checkou…
    • Tweak: Privacy-law settings now stay in sync with the Admin Portal. Per-region (geolocation) rules are configured in the Admin Portal and are respected when you save a law selection in the plugin, and each law’s on-screen description reflects what the banner does on your plan.
    • Tweak: Standardized wording across the plugin — the Hu-manity.co web application is now consistently referred to as the “Admin Portal”.

  17. Cookie Compliance for WordPress 3.1.2

    • Compatibility: Verified and confirmed compatible with WordPress 7.0.
    • Fix: Banner position and banner size now save correctly on sites without a Cookie Compliance subscription — since 3.0.1 these settings appeared to save but silently reverted on every reload.
    • Fix: Reconnecting a domain to a different Cookie Compliance app now refreshes its plan status right away — the visit-limit notice and autoblocking allowance update on save instead of lagging until the next hourly sync.
    • Fix: Account setup now confirms an explicit success response before activating a paid plan, so an incomplete or interrupted server reply can no longer leave an account on the wrong plan.
    • Tweak: Banner-script delivery is now server-controlled, so future banner improvements can roll out gradually and safely without requiring a plugin update. Your current banner is unchanged.
    • Tweak: Configuration and plan changes made in your Cookie Compliance dashboard now apply to your site faster. Previously a publish or plan upgrade could take until the next scheduled sync to take effect; your site now refreshes its settings right away via a secure server signal.

  18. Cookie Compliance for WordPress 3.1.1

    • Fix: The cookie compliance banner and per-form privacy consent prompts now render correctly on sites where Cloudflare Rocket Loader or a caching/optimizer plugin (WP Rocket, LiteSpeed Cache, Autoptimize, NitroPack, Jetpack Boost) defers script execution. The plugin’s inline configuration and per-fo…
    • Tweak: The WordPress dashboard widget now shows a protection scorecard — GPC signal, consent records, and visit quota — replacing the previous usage chart.

  19. Cookie Compliance for WordPress 3.1.0

    • New: WP Consent API integration — Compliance now registers as the active Consent Management Platform under the WP Consent API when that plugin is installed, so cooperative plugins like WooCommerce, Google Site Kit, Burst Statistics, WP Statistics, AddToAny, and Pixel Manager for WooCommerce automat…
    • Tweak: The loading screen now reads “Hang tight — this may take a few seconds on slower connections” and the troubleshooting panel waits 15 seconds before appearing, giving slow connections more breathing room before setup suggestions surface.

  20. Cookie Compliance for WordPress 3.0.6

    • Tweak: The Consent Security Policy (CSP) warning on the Compliance settings page now clears immediately once a valid .htaccess is detected — reloading the page, clicking Purge Cache, or clicking Pull Configuration each re-evaluate in real time.

  21. Cookie Compliance for WordPress 3.0.5

    • Fix: Disabling Autoblocking via the legacy settings form on multisite sites now saves correctly.

  22. Cookie Compliance for WordPress 3.0.4

    • Fix: The Compliance settings page no longer breaks on sites where Cloudflare Rocket Loader or a caching/optimizer plugin (WP Rocket, LiteSpeed Cache, Autoptimize, NitroPack, SG Speed Optimizer, or Jetpack Boost) is configured to process WP admin scripts. The plugin’s admin bundle now signals these…
    • Fix: If the Compliance settings page fails to load, you now see a “Loading Compliance dashboard…” message that reveals troubleshooting steps (caching plugin, browser extension, incognito mode) and a link to support — replacing the silent white screen some users hit when a CDN, optimizer, or browser…

  23. Cookie Compliance for WordPress 3.0.3

    • Tweak: Send client type, plugin version, and admin UI mode (React or Legacy) as HTTP headers on platform API requests to support integration adoption analytics. No effect on banner behavior, site visitors, or consent data.
    • Docs: Added a Privacy section to the readme describing, by service and data category, what the plugin sends to Hu-manity.co services and when. Placed after Installation per WordPress convention. Covers admin-side state stored on the WordPress site (options, transients, localStorage), the visitor IP…
    • Fix: Added JS optimizer exclusion attributes to the banner script tags to prevent caching and performance plugins from delaying consent recording. Covers WP Rocket (data-nowprocket), Autoptimize (data-noptimize), LiteSpeed Cache (data-no-optimize), NitroPack (nitro-exclude), Jetpack Boost (data-jet…
    • New: GPC banner mode is now configurable directly from the plugin. The Protection tab’s GPC panel exposes three options for what visitors see when their browser signals Global Privacy Control — “Show passive notice” (a brief auto-dismiss confirmation that the preference was honored), “Silent” (no o…

  24. Cookie Compliance for WordPress 3.0.2

    • Fix: Decouple Autoblocking from privacy law selection in React and legacy settings — the toggle now appears for connected users regardless of whether laws are configured, and is no longer mislabeled as a Pro-only feature in the legacy UI.
    • Fix: Preserve boolean types when caching Designer, Account, and Analytics API responses — compliance flags such as gpcSupportMode, doNotTrackMode, onScroll, onClick, uiBlocking, revokeConsent and nested regulations were being silently coerced to strings, which risks breaking strict type checks down…

  25. Cookie Compliance for WordPress 3.0.1

    • Fix: Resolved missing file error preventing plugin activation for some users who updated during the initial 3.0.0 release

  26. Cookie Compliance for WordPress 3.0.0

  27. Cookie Compliance for WordPress 2.5.16

  28. Cookie Compliance for WordPress 2.5.15

  29. Cookie Compliance for WordPress 2.5.14

  30. Cookie Compliance for WordPress 2.5.13

  31. Cookie Compliance for WordPress 2.5.12

20257 releases

  1. Cookie Compliance for WordPress 2.5.11

  2. Cookie Compliance for WordPress 2.5.10

  3. Cookie Compliance for WordPress 2.5.9

  4. Cookie Compliance for WordPress 2.5.8

  5. Cookie Compliance for WordPress 2.5.7

  6. Cookie Compliance for WordPress 2.5.6

  7. Cookie Compliance for WordPress 2.5.5

202412 releases

  1. Cookie Compliance for WordPress 2.5.4

  2. Cookie Compliance for WordPress 2.5.3

  3. Cookie Compliance for WordPress 2.5.2

  4. Cookie Compliance for WordPress 2.5.1

  5. Cookie Compliance for WordPress 2.5.0.1

  6. Cookie Compliance for WordPress 2.5.0

  7. Cookie Compliance for WordPress 2.4.18

  8. Cookie Compliance for WordPress 2.4.17.1

  9. Cookie Compliance for WordPress 2.4.17

  10. Cookie Compliance for WordPress 2.4.16

  11. Cookie Compliance for WordPress 2.4.15

  12. Cookie Compliance for WordPress 2.4.14

202310 releases

  1. Cookie Compliance for WordPress 2.4.13

  2. Cookie Compliance for WordPress 1.4.12

  3. Cookie Compliance for WordPress 2.4.11.1

  4. Cookie Compliance for WordPress 2.4.11

  5. Cookie Compliance for WordPress 2.4.10

  6. Cookie Compliance for WordPress 2.4.9

  7. Cookie Compliance for WordPress 2.4.8

  8. Cookie Compliance for WordPress 2.4.7

  9. Cookie Compliance for WordPress 2.4.6

  10. Cookie Compliance for WordPress 2.4.5

20229 releases

  1. Cookie Compliance for WordPress 2.4.4

  2. Cookie Compliance for WordPress 2.4.3

  3. Cookie Compliance for WordPress 2.4.2

  4. Cookie Compliance for WordPress 2.4.1

  5. Cookie Compliance for WordPress 2.4.0

  6. Cookie Compliance for WordPress 2.3.1

  7. Cookie Compliance for WordPress 2.3.0

  8. Cookie Compliance for WordPress 2.2.3

  9. Cookie Compliance for WordPress 2.2.2

202113 releases

  1. Cookie Compliance for WordPress 2.2.1

  2. Cookie Compliance for WordPress 2.2.0

  3. Cookie Compliance for WordPress 2.1.5

  4. Cookie Compliance for WordPress 2.1.4

  5. Cookie Compliance for WordPress 2.1.3

  6. Cookie Compliance for WordPress 2.1.2

  7. Cookie Compliance for WordPress 2.1.1

  8. Cookie Compliance for WordPress 2.1.0

  9. Cookie Compliance for WordPress 2.0.4

  10. Cookie Compliance for WordPress 2.0.3

  11. Cookie Compliance for WordPress 2.0.2

  12. Cookie Compliance for WordPress 2.0.1

  13. Cookie Compliance for WordPress 2.0.0

20205 releases

  1. Cookie Compliance for WordPress 1.3.2

  2. Cookie Compliance for WordPress 1.3.1

  3. Cookie Compliance for WordPress 1.3.0

  4. Cookie Compliance for WordPress 1.2.51

  5. Cookie Compliance for WordPress 1.2.50

20194 releases

  1. Cookie Compliance for WordPress 1.2.49

  2. Cookie Compliance for WordPress 1.2.48

  3. Cookie Compliance for WordPress 1.2.47

  4. Cookie Compliance for WordPress 1.2.46

20185 releases

  1. Cookie Compliance for WordPress 1.2.45

  2. Cookie Compliance for WordPress 1.2.44

  3. Cookie Compliance for WordPress 1.2.43

  4. Cookie Compliance for WordPress 1.2.42

  5. Cookie Compliance for WordPress 1.2.41

20173 releases

  1. Cookie Compliance for WordPress 1.2.40

  2. Cookie Compliance for WordPress 1.2.39

  3. Cookie Compliance for WordPress 1.2.38

20164 releases

  1. Cookie Compliance for WordPress 1.2.37

  2. Cookie Compliance for WordPress 1.2.36.1

  3. Cookie Compliance for WordPress 1.2.36

  4. Cookie Compliance for WordPress 1.2.35

201520 releases

  1. Cookie Compliance for WordPress 1.2.34

  2. Cookie Compliance for WordPress 1.2.33

  3. Cookie Compliance for WordPress 1.2.32

  4. Cookie Compliance for WordPress 1.2.31

  5. Cookie Compliance for WordPress 1.2.30

  6. Cookie Compliance for WordPress 1.2.29

  7. Cookie Compliance for WordPress 1.2.28

  8. Cookie Compliance for WordPress 1.2.27

  9. Cookie Compliance for WordPress 1.2.26

  10. Cookie Compliance for WordPress 1.2.25

  11. Cookie Compliance for WordPress 1.2.24

  12. Cookie Compliance for WordPress 1.2.23

  13. Cookie Compliance for WordPress 1.2.22

  14. Cookie Compliance for WordPress 1.2.21

  15. Cookie Compliance for WordPress 1.2.20

  16. Cookie Compliance for WordPress 1.2.19

  17. Cookie Compliance for WordPress 1.2.18.1

  18. Cookie Compliance for WordPress 1.2.18

  19. Cookie Compliance for WordPress 1.2.17

  20. Cookie Compliance for WordPress 1.2.16

201418 releases

  1. Cookie Compliance for WordPress 1.2.15

  2. Cookie Compliance for WordPress 1.2.14

  3. Cookie Compliance for WordPress 1.2.13

  4. Cookie Compliance for WordPress 1.2.12

  5. Cookie Compliance for WordPress 1.2.11

  6. Cookie Compliance for WordPress 1.2.10

  7. Cookie Compliance for WordPress 1.2.9.1

  8. Cookie Compliance for WordPress 1.2.9

  9. Cookie Compliance for WordPress 1.2.8

  10. Cookie Compliance for WordPress 1.2.7

  11. Cookie Compliance for WordPress 1.2.6

  12. Cookie Compliance for WordPress 1.2.5

  13. Cookie Compliance for WordPress 1.2.4

  14. Cookie Compliance for WordPress 1.2.3

  15. Cookie Compliance for WordPress 1.2.2

  16. Cookie Compliance for WordPress 1.2.1

  17. Cookie Compliance for WordPress 1.2.0

  18. Cookie Compliance for WordPress 1.1.0

20132 releases

  1. Cookie Compliance for WordPress 1.0.1

  2. Cookie Compliance for WordPress 1.0.0

Questions about Cookie Compliance for WordPress’s releases

What is the latest version of Cookie Compliance for WordPress?

3.1.18, released on Nov 2, 2026 (1 week ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.

How often is Cookie Compliance for WordPress updated?

34 releases in the last year, about one every 11 days. Its first release on WordPress.org dates from July 2013.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Cookie Compliance for WordPress’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.