Wiwi Cookie Consent
| 开发者 | naiches |
|---|---|
| 更新时间 | 2026年7月28日 22:20 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Opt-in by default — every category starts OFF; nothing tracks until a visitor chooses to allow it.
- Real script blocking — tracking code is wrapped in an inert
<template>element and only activated after consent, not just hidden with CSS. - Per-category consent — Marketing, Analytics, and Functional, each independently toggleable in the preferences modal.
- Quick-add templates for Google Analytics 4, Meta Pixel, and Google Ads — enter your ID, done.
- Fully accessible — keyboard navigation, focus trap, ARIA attributes on the preferences modal.
- Style it yourself — an optional toggle disables the plugin's own CSS entirely while keeping every ID and class in place, so you can theme the banner from your own stylesheet.
- Dutch and English out of the box.
- No consent logging. Nothing about your visitors is stored server-side — no IP, no timestamp, no consent database. Built for anonymous-visitor sites without accounts/logins; there's no identified user to tie a server-side consent record to in the first place. See the notice on the plugin's own settings page for the full reasoning.
- No validation of how you classify a cookie. You decide which category (Marketing/Analytics/Functional) each cookie belongs to, and the plugin blocks/unblocks it accordingly — correctly and reliably. It cannot know whether you classified it correctly (e.g. labelling an analytics cookie as "Functional" to skip consent is a real, commonly-fined mistake). Getting the categories right is your legal responsibility.
- No site-wide cookie scanning or auditing. The plugin doesn't crawl your site to discover what cookies exist — you declare them yourself in the cookie table. Automatic cookie discovery is a fundamentally different (and much heavier) category of tool; see the FAQ.
- No scanning or filtering of other plugins, themes, or embedded content. This plugin only gates the tracking code you configure through its own settings — it will not detect or block a hardcoded script elsewhere on your site, or a YouTube/Maps/social-widget embed. Continuously scanning and filtering arbitrary page content would need to watch the DOM on every page (e.g. a
MutationObserver), which runs against this plugin's zero-front-end-impact design goal. That stays your responsibility — self-host fonts, use privacy-enhanced embed modes, or click-to-load placeholders. - No Terms, Privacy Policy, or Cookie Policy content. The Banner & Modal Text settings let you link to existing WordPress pages for these — the plugin does not write, generate, or validate their content. You (or your agency) must write and maintain Algemene voorwaarden, Privacybeleid/Privacyverklaring, and Cookiebeleid yourselves.
- No bundled updater, no telemetry, no phone-home. Updates come from the WordPress.org repository like any other plugin.
安装:
- Upload the
wiwi-cookie-consentfolder to/wp-content/plugins/, or install the zip via Plugins → Add New → Upload Plugin. - Activate the plugin through the Plugins menu in WordPress.
- Open the new Cookies menu in the admin sidebar.
- Add your tracking code per category (or use the quick-add templates), customise the banner text, and save.
屏幕截图:
常见问题:
Does this plugin store or log what visitors consented to?
No. There is no server-side consent database. See "What it deliberately does not do" above and the notice shown at the top of the plugin's own settings page.
Does it block cookies from other plugins or themes?
No. It only gates tracking code entered through its own settings screen. If you have a tracking script hardcoded in your theme or added by another plugin, route it through Wiwi Cookie Consent's settings if you want it consent-gated, or handle it separately.
Does it check whether I've categorised my cookies correctly?
No. The plugin blocks and unblocks exactly what you tell it to, exactly as configured — that mechanism is reliable. Whether a given cookie genuinely belongs in Marketing, Analytics, or Functional (and whether "Functional" is even the correct exemption for it) is a legal judgement call only you can make. Mislabelling a tracking cookie as "Functional" to avoid asking for consent is one of the most common cookie-banner violations regulators actually fine — the plugin can't catch that for you.
Can this plugin scan my site and find all my cookies for me?
No, and that's intentional. Automatic cookie/tracker discovery is a genuinely different, much heavier category of tool (the kind built by dedicated consent-management platforms). This plugin stays a lightweight blocker for the tracking code you explicitly configure — it does not crawl pages, inspect third-party scripts, or maintain its own cookie database.
Do I still need to write my own Privacy Policy / Terms / Cookie Policy?
Yes, always. The plugin lets you link the banner to existing WordPress pages for Terms & Conditions, Privacy Policy, and Cookie Policy — it does not write or supply any legal content. That text is your (or your agency's) responsibility.
Does it collect any data or phone home?
No. There is no usage tracking, analytics, telemetry, or licensing call-home.
Can I fully restyle the banner?
Yes. Enable "Don't load the plugin's default stylesheet" under Styling in the settings page, and style #wcc-cookie-banner, #cookie-preferences-modal, .wcc-btn, .wcc-toggle, and the other existing classes/IDs from your own theme CSS. The banner's show/hide and open/close behaviour works independently of the stylesheet.
更新日志:
- Fixed: text pasted into a category's tracking code field was inserted into the page as visible content the moment a visitor accepted that category. Anything without a script or stylesheet tag is now ignored at insertion time, so it can never reach a visitor.
- Added: each category now has a "What visitors are told" field, shown under that category in the Manage cookies window. Category explanations previously had nowhere to go, which is what led people to put them in the code field.
- Changed: the settings screen is rebuilt around one card per category, holding that category's explanation, its code, and the cookies it declares. Banner and modal copy, styling and consent settings move to their own tabs.
- Added: saving a code field that contains no script or stylesheet tag now warns, and the category is flagged on screen until it is resolved.
- Added: "Add a known service" now asks for whatever that service actually needs — Adobe Fonts for a kit ID, Google Analytics for a measurement ID — with a note on where to find it and which cookies it will declare. Adobe Fonts and Google Fonts are now included.
- Fixed: a stylesheet or meta tag activated on consent no longer announces "additional content has been added to the page" to screen readers, since nothing visible was added.
- Initial release.