Cookie Rocket – Cookie Consent Banner & Script Blocker

Izmaiņu žurnāls

2.15.14

Fixed: a blocked embed kept its shape on sites with a strict Content-Security-Policy. The placeholder that stands in for a blocked video or map carries the aspect ratio of the embed it replaces, so the page does not jump when the visitor accepts. That ratio is different for every embed, so it travelled in a style attribute — which such a policy discards, leaving the placeholder with no height: the collapsed layout this placeholder exists to prevent. The ratio now travels in a data attribute and the script applies it.

2.15.13

Fixed: the plugin now behaves the same on sites that send a strict Content-Security-Policy. A CSP whose style-src and script-src do not allow ‘unsafe-inline’ makes the browser discard inline style attributes and inline event handlers. The banner and the dialog put some of their layout and behaviour there, so on those sites parts of the plugin silently stopped working. Everything moved to the stylesheet and to the script file, which the policy allows.
* Fixed: the [cookie-rocket-preferences] and [cookie-rocket-withdraw] shortcodes did nothing under such a policy. They carried their call in an onclick attribute, which the browser refuses to execute, so a visitor could not reopen their choices or withdraw consent from the page where you had placed the button. The script now listens for them by class.
* Fixed: in the preferences dialog each category’s control fell below its label instead of sitting on the right, because the row built its columns with a style attribute.
* Fixed: your Accept button text colour, your solid secondary-button colours and the dialog’s fixed footer colours were only ever applied through style attributes, so a strict policy dropped them and the same settings rendered differently from one site to the next. They are part of the stylesheet now.
* The banner-layout thumbnails in the editor drew “floating” and “modal” as wide bars, when both stack their buttons and render as tall cards. They now match what applying them produces.
* The live preview was shorter than a floating banner, so the banner started above the frame and covered the previewed page. The preview is taller.
Style and markup only; no change to settings, consent records or blocking behaviour.

2.15.12

Fixed: four things in the preferences dialog that were harder to use than they looked. The category controls were a sliding switch with its rounded shape removed, which read as neither a switch nor a checkbox — a square knob in a square track, where the only clue to the state was the colour of the track. They are now plain checkboxes: an empty square for off, a filled square with a checkmark for on, and a greyed checked one for strictly-necessary. Same square, no-radius look; you can tell the state at a glance.
* The close button sat in the header at the same height as the title. It now sits anchored in the top-right corner of the dialog, which is where it is looked for, and it measures 28×28 instead of 13×22 — its width used to come from the width of the glyph itself, below the 24×24 minimum recommended by WCAG 2.5.8 and awkward to hit with a thumb.
* Each category’s description ran the full width and passed under the column of controls. On a phone the text reached the edge while the title above it stopped short, leaving a ragged right margin. Both now break on the same line.
* Hardening: the dialog sets its own box-sizing instead of relying on the theme to set it globally.
Style only. Your settings, banner and consent log are unchanged.

2.15.11

The plugin description and the feature list now say what the plugin does instead of promising an outcome. The description no longer guarantees a PageSpeed score, which depends on your site and host rather than on this plugin, and the framework line no longer claims to grant legal compliance, which no plugin can grant. What it does say is accurate: it ships banner wording and consent rules for GDPR, CCPA / CPRA, LGPD and LFPDPPP, and you pick the one that applies. No functional change.

2.15.10

The plugin header now carries the same name as the listing.

2.15.9

The plugin is now listed as what it does — a cookie consent banner and script blocker — instead of claiming compliance, which no plugin can grant. CCPA / CPRA joins the tags now that the framework is fully supported. Code hardening around the new visitor-country field.

2.15.8

New: the plugin now tells you what it found on your own site. Three notices that appear only when there is something real to say, and go away when you dismiss them or when the fact changes.
* Your visitors’ country is now recorded with each consent decision. It was already resolved in the browser by timezone and then thrown away. No IP, no external service, no new personal data.
* If a meaningful share of your visitors comes from a region under a different framework than the one your banner applies, the plugin says so, with the percentage.
* If a quarter or more of your visitors reject cookies, the plugin says so — and tells you whether Consent Mode v2 is on, which decides whether those visitors are measurable at all.
* The review request now waits until Cookie Rocket has actually done something countable on your site, and says what it did, instead of appearing on a 14-day timer.

2.15.7

Fixed: the cookie bar took a third of a phone screen. On mobile the three buttons stacked one per row — 148px of controls on a 300px bar, tall enough to sit on top of a form’s submit button. Accept now keeps its own full-width row and Customize and Reject share the next one: 282px instead of 300, in two rows instead of three. If your site turns off Customize or Reject, the remaining button grows into the whole row. Only the top and bottom bar layouts change; the popup, floating and drawer layouts are untouched.
* Translations: removed a leftover string and refreshed the template.

2.15.6

New: declare your own services. Cookie Rocket recognizes nine common providers. Anything else on your site — a chat widget, a heatmap tool, a newsletter script — was neither blocked nor listed on your cookie policy. Blocking → Your own services lets you name it, give the script address so it gets blocked, and describe its cookies so they appear on your policy with a real purpose and duration.

New: California. CCPA / CPRA joins GDPR, LGPD and LFPDPPP in the framework selector, with its own banner wording.

New: the scanner sees your shop. On WooCommerce sites it now also reads the shop, cart, checkout and account pages — where conversion pixels usually live and where a homepage-only scan never looked. It also tells you which trackers are new since your last scan.

Fixed: a failed scan no longer reads as a clean site. If a page could not be read, the result says so and lists which, instead of reporting zero trackers found.

Fixed: the scanner reports Google Tag Manager. The container is deliberately not blocked — Consent Mode governs it — but staying silent made a site that loads everything through GTM read “no trackers found”. It is now listed with its real status.

Fixed: the blocking status tells the truth. A tracker pasted straight into your theme is not reached by script blocking unless raw-HTML blocking is on. That row used to claim it was blocked; it now says it is pasted directly into the HTML and links to the switch that handles it.

New: consent-log retention is yours to set. Records were deleted after 90 days with no way to change it and nothing on screen saying so. There is now a field, and the log states how long it keeps records.

Free: the Glass, Graphite and Branded banner themes, and the self-hosted font option.

Updated design. Squared corners, no shadows, no transitions and no entrance animation, throughout the banner, the preferences dialog and the admin screens. If you are updating an existing site, the banner will lose its drop shadow and slide-in and gain a hairline border; your saved corner radius is untouched.

Accessibility. The floating preferences button’s focus ring is now visible on light backgrounds, and the category switches read clearly in both states.

Polish, hardening & fixes from a thorough audit — functionality, security, accessibility, reliability and translations. Nothing to reconfigure; your settings, banner and consent log are unchanged.
* Fixed (accessibility): the banner no longer traps keyboard focus in the bar layout (you can Tab past it), while the popup, side panel and drawer still contain focus while open. The preferences dialog is announced by its title, traps focus even for a returning visitor who opens it from the floating button, returns focus to the control that opened it, and its cookie-category switches carry accessible names (WCAG 2.1.2 / 2.4.3).
* Fixed (reliability): behind a full-page cache, a visitor’s consent could go unrecorded when the cached page carried an expired security token — recording no longer depends on it. The consent-endpoint rate limit is now keyed on the real connection IP with a fixed one-minute window, so it cannot be side-stepped with spoofed headers or become a permanent block.
* Fixed (privacy): blocked social/media embeds (X, Instagram, TikTok, Facebook and similar) fully restore after consent, including embeds that load their own script; and the raw-HTML script blocker now also catches trackers whose src/type attributes are unquoted.
* Fixed (Consent Mode): the “functionality_storage” signal now follows the visitor’s functional-cookie choice instead of always reporting granted.
* Fixed: “Save text” and the Layout / position / width / backdrop controls now report or roll back a failed save instead of showing an unsaved change as applied; consent-log stats and retention compute their window in the site’s own timezone; the preferences close button meets contrast; and the cookie-category grid no longer overflows on narrow phones.
* Improved (translations): the whole interface, the cookie-declaration table (each cookie’s purpose and duration) and the cleanup-schedule label are now complete in Spanish and Portuguese.

2.15.5

On some themes the Reject button could render unfilled; its fill now holds up against theme button styles.

2.15.4

Default banner aligned to the common consent-tool convention: Reject filled with equal prominence, Customize outline, subtle 2px corners.

2.15.3

Banner button order follows the common convention on every layout, and no button is pre-focused when the banner appears.

2.15.2

Banner buttons always take the same corner radius as the banner on every layout.

2.15.1

Live-preview button labels, a clean preview without the admin bar, instant style presets, contextual help tooltips, and a 0px default corner radius.

2.15.0

One-click setup, a live banner editor, blocked-embed placeholders that keep your layout, and consent that persists across localStorage clears.

2.14.x and earlier

Older release notes are available in the plugin’s development history on WordPress.org.