-
released this
2026-08-30 20:53:37 +02:00 | 0 commits to main since this releaseSecond release. Two fixes to how the banner renders inside a theme, plus the
value+unit "Custom" option on every appearance scale.The banner now looks the same on the front as in the preview
The banner is a plugin-owned island dropped into an unknown theme, and styling
barebuttonis a near-universal theme habit — frequently through selectors
that outrank a plain class. Any layout property the banner did not set itself
could be taken over by the theme, and the admin preview could never warn you:
it renders in wp-admin, where no theme stylesheet is loaded. So the preview
promised one banner and the front delivered another.On a theme giving buttons a
min-width, that meant a close (×) stretched across
the whole header, action buttons stacking one per row instead of sharing a line,
and the "continue without accepting" link rendered as a wide centred block.The banner's controls are now shielded from theme layout rules — widths,
margins, letter-spacing, native appearance and the rest — without a single
!important. Colours, font family and sizes are deliberately not shielded:
those still come from your theme through the plugin's CSS variables, so the
FSE-first "looks native with zero configuration" behaviour is unchanged.If your banner already looked right, nothing changes.
Closing the banner is no longer the highlighted default
The banner used to hand focus to its first control when it opened. That control
is the close (×) — which counts as refusing everything. Browsers drew a focus
ring around it, so the most visually prominent thing in the banner was refusal,
and it was the default keyboard action too.The banner now takes focus itself. The × keeps a proper focus ring when you
actually tab to it.New: close-button size
The × has joined the appearance controls: Small / Medium / Large, or Custom with
your own value and unit. The default matches the previous size exactly.Since closing the banner counts as refusing everything, a discreet × next to
clearly-presented choices is the better default — this makes that adjustable.Also in this release
- Custom + unit on every appearance scale. Width, spacing (padding/gap),
text and title size, and corner radius each offer a Custom option backed by a
value + unit control, alongside a free-text font family. The live preview
resolves them exactly as the front does. - "Continue without accepting" outside the box — an extra placement pinning
the refusal link to the top of the viewport (the French press pattern), with
its own colour option. - CAPTCHA fixes. A CAPTCHA rule set to "always blocked" now renders nothing
instead of a dead "Accept & load" button, and the admin warns you when a
CAPTCHA rule is set that way. - Cookies tab: scan and list merged into one view, an "Ignore" status to hide
a cookie from visitors, and a shorter, less unwieldy editor.
Upgrading
Update from wp-admin as usual. If you run a page-cache or CSS-minify plugin,
purge its cache afterwards — the previous banner stylesheet is otherwise frozen
in the minified bundle.Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
0 downloads
- Custom + unit on every appearance scale. Width, spacing (padding/gap),
-
released this
2026-08-01 04:07:36 +02:00 | 2 commits to main since this releaseFirst packaged release — an early one, as the version number says. The plugin is
feature-complete for its scope and builds clean, but it hasn't been through a
long production shakedown yet. Install it where you can keep an eye on it.What it does
A lean, opinionated GDPR / ePrivacy consent plugin: an opt-in banner, a real
blocking engine, and proof of consent — without the weight of a full consent
platform.- Opt-in by default. Nothing optional loads until the visitor agrees.
- Blocking engine that neutralises third-party
<script>and<iframe>tags
before consent and re-activates them on acceptance. Blocked embeds show a
sized, click-to-load placeholder naming the source — including CAPTCHAs
(Turnstile / reCAPTCHA / hCaptcha), rendered inside their own widget. Crawlers
get the unmodified page, and the blocking is page-cache-safe. - Auto-detect — scan your site (database content, or by visiting pages) to
find third-party scripts and embeds, then add them as rules in one click. - FSE-first appearance. The banner inherits your block theme's colours,
fonts and buttons, so it looks native with zero configuration. Light / Dark /
Midnight / Ocean / Sand / Custom themes, position and edge offsets, width,
density, corners, entrance animations and a live preview are all there when
you want them. - Proof of consent (on by default) — one record per event with an anonymous
subject ID, the granular per-purpose decisions, the act, and the exact banner
as the visitor saw it. Hashed or full IP, ~13-month renewal, configurable
retention, and an audit view with CSV export. - WP Consent API mirroring, for plugins that read consent from it.
Requires PHP 8.2+ and WordPress 6.8+.
Install
Download the ZIP below, then Plugins → Add New → Upload Plugin. Nothing is
blocked until rules exist, and the banner only appears once there is something
to manage — so start with Settings → Cookie Consent → Cookies → Auto-detect.From here on the plugin updates itself: new versions appear under Plugins and
Dashboard → Updates, pulled from
git.lrob.net/WP/cookie-consent.Bug reports and suggestions: git.lrob.net/WP/cookie-consent/issues
or lrob.fr/contact.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads