Cookie Compliance for WordPress – Cookie Consent, GDPR & CCPA

Registro de cambios

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 rules needs its own exclusion for logged-in users. Purge your cache once after updating — copies already stored are not cleared automatically.
• 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 Microsoft tracking plugin is active. Nothing about your visitors, your content or your users is sent; the Privacy section lists it all.
• 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.

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 until a translation for your language is available.
• 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 problem.
• 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.

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, connection, consent records and updates are unchanged; nothing to do. Renamed text may show in English until translations catch up.
• 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 not applied. It can also be set to Basic Operations, for storage that is strictly necessary on your site.
• 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 consent records no longer depend on your visit allowance.
• 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.

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 «Always» option has been retired; if you used it, open Protection and choose a category.

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, instead of seeing a button that appears to do nothing. Sites that have already moved Google Recaptcha to Basic Operations are unaffected.
• 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: nothing was held back for them, and those services were told consent had been given before the visitor had answered the banner. Blocking is still switched off for users who can manage the banner, so you can keep working on your own site as before. If your site needs a wider exemption, a developer can adjust it with the cn_manage_cookie_notice_cap filter.

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 script, so the banner appeared late (or not at all) and cookies could load before a visitor consented; the plugin now signals them to leave its script alone, whether or not the plugin’s «Caching Compatibility» option is enabled.

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 previously prevent the script from loading; this extends the compatibility added in 3.1.1.
• 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 checkout remains available as before.
• 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».

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.

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-form helper scripts now signal these tools to skip them, extending the banner-script protection added in 3.0.3.
• Tweak: The WordPress dashboard widget now shows a protection scorecard — GPC signal, consent records, and visit quota — replacing the previous usage chart.

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 automatically gate themselves on the consent state captured by your banner. Hu-manity’s four consent levels map to the WP Consent API’s five categories: Strictly Necessary → functional (always allowed), Functional → preferences, Analytics → statistics and statistics-anonymous, Marketing → marketing. Global Privacy Control automatically suppresses the marketing category. A new «WP Consent API» toggle on the Configuration tab lets you turn the integration off; it is on by default when both plugins are active.
• 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.

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.

3.0.5

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

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 tools to skip it, extending the same banner-script protection added in 3.0.3.
• 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 extension blocked the admin bundle.

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 visibility implied by the banner’s direct browser-to-platform requests, retention of plugin-side caches and platform-side account/consent data, sub-processors (Braintree for plugin-initiated payments, additional payment gateway providers for webapp-managed subscriptions, and Hu-manity.co’s email subscription service), data processing location (European Union, AWS Ireland), and concrete data-subject rights (deactivation, CSV export, account deletion, and GDPR Article 17 / CCPA erasure of visitor records within a 30-day SLA per GDPR Article 12).
• 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-jetpack-boost), and Cloudflare Rocket Loader (data-cfasync). Also adds stable IDs (hu-banner-options, hu-banner-js) so users of plugins without attribute support (W3 Total Cache, SG Optimizer, Swift Performance) can enter these as exclusion keywords in their plugin settings.
• 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 on-screen indication), or «Show full banner» (the standard consent flow). When CCPA or other US privacy laws are selected, the plugin defaults to «Show passive notice» — improving transparency without re-displaying the banner on every page. The active mode is also surfaced on the GPC Support card under Compliance Behavior so site admins can see at a glance how GPC manifests for their visitors. The setting can still be changed at any time in the Cookie Compliance web application.

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 downstream.

3.0.1

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

3.0.0

• Rebrand: Plugin renamed from «Cookie Notice & Compliance for GDPR / CCPA» to «Compliance by Hu-manity.co». WordPress admin sidebar now reads «Compliance» with Settings and Audit Trail submenus. All internal option keys and slugs remain unchanged — no action required for existing installs.
• New: Modern React-based admin dashboard replaces the legacy PHP settings pages. Three main tabs — Protection, Settings, and Audit Trail — with a polished, card-based interface.
• New: Guided setup wizard with banner template picker (6 presets), setup checklist, and quick-start configuration for new installs.
• New: Welcome Modal with in-plugin account creation, plan selection, and Braintree payment — complete the signup flow without leaving WordPress.
• New: Protection Chooser — redesigned tier selection (Basic, Professional, Business) with feature comparison cards.
• New: 5-position banner placement selector (top, bottom, floating left, floating right, floating center) with fixed/floating toggle. Dismiss animation controls added to Banner Design settings.
• New: Law Selector with geo-aware regulation display and compliance context for GDPR, CCPA, and 100+ jurisdictions.
• New: Consent Modes panel — configure Google Consent Mode v2, Facebook, and Microsoft consent toggles directly from the plugin.
• New: Audit Trail tab — view consent log records pulled live, with dynamic consent level labels.
• New: Conditional Display rule builder — control when and where the consent banner appears.
• New: Excluded Script Handles setting — exclude specific scripts from autoblocking by handle name.
• New: Centralized notification system with contextual calls-to-action based on your setup status and subscription tier.
• New: Portal deep links — jump directly from the plugin to the relevant page in the Cookie Compliance web application.
• New: Live configuration sync — admin pages pull fresh banner configuration from the platform on load.
• New: React ErrorBoundary prevents white-screen crashes — admin gracefully recovers from unexpected errors.
• Improvement: Pro feature indicators show locked features with upgrade prompts for free-tier users.
• Improvement: Usage dashboard shows near-limit nudge at 70%+ of cycle usage.
• Improvement: Email-exists recovery flow guides users who try to register with an existing account.
• Fix: Domain URL normalization on login prevents duplicate app registrations.

2.5.16

• Fix: Multisite with global override now correctly reads blocking data and cache-purge transients from network storage
• Fix: Custom patterns and providers are now always included in huOptions regardless of autoblocking state

2.5.15

• Fix: Multisite with global override now correctly loads custom blocking patterns and providers on the frontend

2.5.12

• New: Added pull configuration option to sync on demand instead of waiting for cron

2.5.11

• Security: Enforce TLS verification for platform API requests.
• Security: Require capability + nonce for cache purge and privacy consent/conditional rule AJAX handlers.
• Tweak: Switch admin notice JS to vanilla to avoid jQuery conflicts and ensure notices can be closed.

2.5.10

• Fix: Make close icon keyboard-focusable (Enter/Space handler, tabindex, focus outline)
• Fix: Ensure policy link uses href/target and data attrs so «Message» position opens correctly
• Fix: Enqueue frontend JS when [cookies_revoke] shortcode is present to allow reopen links for logged-in sessions
• Fix: Guard legacy options fallback to avoid PHP 8 fatal on non-array settings

2.5.9

• Security: Fixed Stored XSS vulnerability in [cookies_accepted] shortcode via HTML entity resurrection
• New: Easy Digital Downloads privacy consent support
• Fix: Improved bot detection and object cache compatibility

2.5.8

• New: Microsoft Clarity Consent API v2 support
• Fix: Prevent loading banner in Beaver Builder
• Fix: Improved bot detection and object cache compatibility
• Fix: Close icon accessibility by switching to button

2.5.7

• New: Microsoft Consent Mode support
• Tweak: Convert banner links to buttons (for accessibility)
• Tweak: Improved compatibility with caching plugins
• Fix: Displaying cookie notice in admin

2.5.6

• New: Added Form and Source columns to Privacy Consents table
• Fix: WooCommerce render block issue
• Tweak: Updated WooCommerce Blocks Checkout handling
• Tweak: Disable Privacy Consent cupport when there are no forms available
• Tweak: Updated Chart.js to 4.4.8

2.5.5

• New: Added Privacy Consent activity chart
• Fix: Hummingbird caching plugin compatibility

2.5.4

• New: Option to handle all or selected forms in Privacy Consent
• Fix: Undefined array key «form_type» when switching WooCommerce forms

2.5.3

• Fix: Undefined huOptions variable
• Fix: Prevent loading Privacy Consent modules without Cookie Compliance
• Tweak: Updated Chart.js to 4.4.6

2.5.2

• Fix: Fatal error on pages with embedded contact form 7 forms

2.5.1

• Fix: Missing one of the plugin files

2.5.0

• New: Introducing Privacy Consent
• Tweak: UI updates for the Consent Logs page
• Tweak: Onboarding screen UI improvements
• Tweak: Switch from local to GMT time for consent logs display
• Tweak: Admin menu reorganization

2.4.18

• Fix: Potential security issue with escaping textarea fields
• Fix: Saving link target for Privacy Policy page
• Fix: Force protocol for widget URL

2.4.17

• New: SpeedyCache caching plugin compatibility
• New: Breeze caching plugin compatibility
• Fix: Improved WP Rocket plugin compatibility
• Fix: Improved Speed Optimize plugin compatibility
• Fix: Network settings override switching
• Tweak: Chart.js updated to 4.4.3

2.4.16

• New: Option to enable/disable bot detection
• Fix: Typo in wp_die() function calls
• Tweak: Improved escaping text strings

2.4.15

• New: Passing Google Consent default parameters (Cookie Compliance only)
• Fix: Invalid Norwegian language locale code

2.4.14

• New: Google Consent V2 support (Cookie Compliance only)
• New: Added scripts option to Compliance Settings

2.4.13

• Fix: Removed unneeded parameter from WP Fastest Cache compatibility fix

2.4.12

• New: WP Optimize caching plugin compatibility
• Fix: WP Fastest Cache plugin compatibility

2.4.11

• New: Dedicated Consent Logs page
• New: Google AMP support for Cookie Compliance
• New: Settings navigation through tabs and menu items
• Fix: Saving App ID/Key not working in edge cases
• Tweak: Chart.js updated to 4.4.0

2.4.10

• New: Option to enable/disable caching compatibility
• New: WP Fastest Cache plugin compatibility
• Fix: Potential security issue with purging cache
• Fix: Improved refreshing Compliance analytics data
• Tweak: Chart.js updated to 4.3.2

2.4.9

• New: WP Rocket plugin compatibility
• New: LiteSpeed Cache plugin compatibility
• New: Google Consent Mode support (Cookie Compliance only)
• New: Facebook Pixel Consent Mode support (Cookie Compliance only)

2.4.8

• New: Added Pages to Conditional display
• Fix: Homepage display issue
• Fix: Background color issue
• Tweak: Improved WP Rocket support
• Tweak: Improved SG Optimizer support

2.4.7

• New: Conditional display of the banner
• Tweak: Improved sanitization and validation of data
• Tweak: PHP 8.1 and 8.2 compatibility
• Tweak: Added async attribute when autoblocking is disabled

2.4.6

• Fix: Cookie Compliance inactive status issue

2.4.5

• Tweak: Remove the notice from the Elementor page builder
• Tweak: Remove the notice from widgets screen
• Fix: Improved Contact Form 7 reCaptcha compatibility

2.4.4

• Fix: Undefined index: status and subscription

2.4.3

• Fix: Deprecated preg_replace() notice in PHP 8.1

2.4.2

• New: Compatibility with Autoptimize plugin
• Fix: Improved Contact Form 7 reCaptcha support
• Fix: Fixed non-static method cookies_set()

2.4.1

• New: Contact Form 7 reCaptcha support
• Tweak: Switched health status from critical to recommended when Cookie Compliance is not integrated
• Tweak: Add SimeSite=Lax for created cookies

2.4.0

• New: Advanced Multisite support
• Fix: Polylang translation not working for shortcode
• Fix: Parse error: syntax error, unexpected ‘[‘

2.3.1

• New: Option to run consent banner in debug mode
• Fix: Invalid validation of dismissable notices

2.3.0

• New: Compliance Multi-license pricing options
• Tweak: WordPress 6.0 compatibility

2.2.3

• Fix: Undefined notice in WP dashboard
• Fix: Close icon event not firing
• Tweak: Remove aria-label from the close icon
• Tweak: CSS tweaks in the admin

2.2.2

• Fix: Uncrawlable close notice link
• Tweak: WordPress 5.9 compatibility
• Tweak: Prevent displaying the notice in an iframe
• Tweak: Send site language to a web app on signup

2.2.1

• Fix: Missing variable definition in frontend

2.2.0

• New: Option to hide banner for logged in users (Compliance only)

2.1.5

• Tweak: Additional sanitization applied

2.1.4

• Fix: WordPress 5.8 widgets compatibility

2.1.3

• Fix: HTML attributes removed from text strings
• Tweak: Improved sanitization of options

2.1.2

• Tweak: Improved escaping of button labels

2.1.1

• Fix: Security bug related to compliance caching

2.1.0

• New: Introducing Cookie Compliance Free plan

2.0.4

• Fix: Undefined constant HOURS_IN_SECONDS
• Fix: Button style none adding CSS classes «cn-set-cookie cn-button»
• Tweak: Switched the behavior of close icon from accept to reject
• Tweak: Minified frontend and admin js files

2.0.3

• Fix: Cookies accepted function issue when Compliance activated

2.0.2

• Tweak: UI/UX improvements

2.0.1

• Fix: Pending Compliance update blocking the notice
• Fix: PHP Warning: Cannot modify header information
• Tweak: UI/UX fixes for the settings screen

2.0.0

• New: Introducing Cookie Compliance for GDPR/CCPA

1.3.2

• Retoque: Acelerada la carga del «Corona Banner» moviendo el archivo JS al pie de página con el parámetro asíncrono
• Retoque: Mejora en el relleno CSS de los botones
• Retoque: Mejoras de accesibilidad en los enlaces

1.3.1

• Corrección: No se puede servir el enlace de la política de privacidad
• Corrección: Enlace en blanco de la política de cookies en un mensaje
• Corrección: Índice no definido `on_click`
• Retoque: Ajustada de nuevo la opacidad por defecto a 100

1.3.0

• Nuevo: Introduce el banner del coronavirus que muestra datos acerca de la pandemia del coronavirus y los cinco pasos recomendados por la OMS (Organización Mundial de la Salud)
• Nuevo: Opción para establecer la opacidad de la barra
• Nuevo: Aceptar el aviso con el icono «Cerrar»
• Corrección: Enlace de la política añadido al mensaje sin la opción de la política activada

1.2.51

• Corrección: Problemas con iOS y el botón de «Aceptar» y «Rechazar»
• Retoque: Añadida la caducidad de la cookie para los rechazos por separado, agradecimientos a Carlos Buchart

1.2.50

• Corrección: La clase CSS del cuerpo siempre se establece como «cookies-refused»
• Retoque: Mejora de la compatibilidad de IE y Safari con CustomEvent y ClassList
• Retoque: Cambiar el JS del plugin en el evento `init`

1.2.49

• Nuevo: Opción para aceptar el aviso al hacer clic en cualquier página
• Retoque: Eliminar la dependencia de jQuery
• Retoque: Cambio de jQuery a animaciones CSS3
• Retoque: Mejora de la estructura del CSS y HTML

1.2.48

• Corrección: Etiquetas HTML eliminadas del mensaje de cookies
• Corrección: El destino del enlace no se aceptaba en el enlace de privacidad integrado

1.2.47

• Nuevo: Opción para seleccionar la posición del enlace a la política de privacidad
• Retoque: No recargar la página al hacer clic en el botón de rechazo
• Retoque: Añadido el atributo `aria-label` al contenedor del aviso de cookies

1.2.46

• Retoque: Eliminar la cookie del plugin WP Super Cache al desactivarlo
• Retoque: Eliminar de la base de datos la versión del plugin al desactivarlo

1.2.45

• Retoque: Mejorada la compatibilidad con el plugin WP Super Cache
• Retoque: Problema con el estilo CSS del contenedor y consulta de medios para el móvil

1.2.44

• Corrección: El texto del botón de revocación se ignoraba en el shortcode
• Corrección: El botón de revocación del consentimiento no se mostraba automáticamente en la posición superior
• Retoque: Añadido el shortcode de análisis del contenido `[cookies_accepted]`, gracias a dsturm

1.2.43

• Nuevo: Opción para revocar el consentimiento del usuario
• Nuevo: Ampliado el bloqueo del script a la cabecera y el pie de página
• Nuevo: Sincronización con la página de política de privacidad de WordPress 4.9.6
• Nuevo: Opción de clase personalizada para el botón
• Retoque: Añadida la opción de caducidad de la cookie de 1 hora

1.2.42

• Nuevo: Introducción del shortcode `[cookies_accepted]` `[/cookies_accepted]`
• Corrección: Problema con la caducidad infinita de las cookies

1.2.41

• Corrección: Bucle de redirección infinito con el scroll activado

1.2.40

• Corrección: Alinear al centro los `div`en algunos temas
• Retoque: Ampliada la lista de etiquetas HTML permitidas en el código de rechazo
• Retoque: Minimizar el CSS y JS

1.2.39

• Nuevo: Opción para recargar la página después de aceptar las cookies

1.2.38

• Retoque: Mover las funciones JS de la cookie de la portada antes de la llamada preparada del documento, gracias a fgreinus
• Retoque: Ajustar el manejo funcional del código JavaScript
• Corrección: No válida la fecha de caducidad infinita en Chromium
• Corrección: Eliminada la función obsoleta `screen_icon()`

1.2.37

• Retoque: Añadir `aria landmark role=»banner»`
• Retoque: Ampliar `cn_cookie_notice_args` con una clase de botón

1.2.36.1

• Corrección: Problema de subida al repositorio con la versión 1.2.36

1.2.36

• Corrección: Compatibilidad para traducción de cadenas de WPML 3.2 o superior
• Corrección: Posible conflicto con otros plugins de una variable global
• Retoque: Añadir el array `$options`al filtro `cn_cookie_notice_output`, gracias a chesio.
• Retoque: Eliminados los archivos locales de traducción en favor de las traducciones del repositorio de WP

1.2.35

• Retoque: Usar `html_entity_decode` en un bloque de código no funcional
• Retoque: Optimización de la ubicación de la función `get_pages()`
• Retoque: Capacidad de filtrado de la gestión del aviso de cookies

1.2.34

• Corrección: Problema de validación HTML de los `href` vacíos en los enlaces

1.2.33

• Nuevo: Traducción a griego, gracias a Elias Stefanidis

1.2.32

• Corrección: Botón de aceptación de cookies oculto al aceptar en lugar del contenedor del mensaje de cookies

1.2.31

• Nuevo: Campo de código JavaScript no funcional
• Corrección: Problema causado por la minimización de la caché JavaScript

1.2.30

• Corrección: Error de jQuery después de aceptar las cookies

1.2.29

• Retoque: Añadir la clase al elemento del cuerpo cuando se muestra
• Retocado: Traducción Italiana actualizada

1.2.28

• Nuevo: Opción para ajustar el desplazamiento del scroll

1.2.27

• Retoque: Eliminar correctamente el evento de scroll para limitar posibles conflictos
• Retocado: Traducción Italiana actualizada

1.2.26

• Corrección: La opción de aceptación de cookies al hacer scroll funcionaba sin marcar.
• Corrección: Advertencia `call_user_func()`en versiones inferiores de WP

1.2.25

• Nuevo: Opción para aceptar las cookies al hacer scroll, gracias a Cristian Pascottini

1.2.24

• Nuevo: Opción para rechazar la aceptación de cookies
• Nuevo: Evento personalizado `setCookieNotice`
• Retoque: Actualización de la traducción a italiano, gracias a Luca Speranza

1.2.23

• Nuevo: Traducción a finés, gracias a Daniel Storgards

1.2.22

• Retoque: Actualización de la traducción a sueco, gracias a Ove Kaufeldt

1.2.21

• Nuevo: Movido el desarrollo del plugin al repositorio GitHub de dFactory
• Retoque: Limpieza del código

1.2.20

• Nuevo: Opción para seleccionar la colocación de los scripts, en la cabecera o en el pie de página

1.2.19

• Nuevo: Traducción a danés, gracias a Lui Wallentin Gottler

1.2.18.1

• Corrección: Corrección rápida en el código `print_r`en la versión 1.2.18

1.2.18

• Nuevo: Opción para el destino del enlace de«Más información»
• Retoque: IDs HTML adicionales para una personalización más flexible

1.2.17

• Nuevo: Traducción a hebreo, gracias a Ahrale Shrem

1.2.16

• Retoque: Falta la traducción a holandés debido a un error tipográfico

1.2.15

• Nuevo: Traducción a danés, gracias a Hans C. Jorgensen
• Corrección: La barra de aviso no es visible si no se ha seleccionado una animación

1.2.14

• Nuevo: Traducción a húngaro, gracias a Surbma

1.2.13

• Nuevo: Traducción a croata, gracias a Marko Beus

1.2.12

• Nuevo: Traducción en esloveno, gracias a Thomas Cuk

1.2.11

• New: Swedish translation, thanks …