Privaro Cookie Consent Banner
| 开发者 | evgenij347 |
|---|---|
| 更新时间 | 2026年8月31日 12:07 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Privaro Cookie Consent Banner helps you run a privacy-conscious WordPress site in the EU and beyond. Visitors get a clear, accessible cookie banner (powered by CookieConsent v3). Third-party scripts and embeds stay blocked until consent is granted — no “accept-only” dark patterns.
Why site owners choose Privaro
- Opt-in by default — Statistics and marketing are off until the visitor accepts. Reject all is always available.
- Real script blocking — GA4, GTM, Meta Pixel, Hotjar, Microsoft Clarity, and custom rules via output buffering.
- Embed placeholders — YouTube, Vimeo, and Google Maps load only after marketing consent.
- Cookie scanner — Discover cookies on your own site (no external SaaS scanner).
- Policy helpers — Shortcodes for cookie policy, declaration table, and “Cookie settings” footer link.
- Google Consent Mode v2 — Default
denied, updates on banner choice; works with Google Site Kit. - WP Consent API — Compatible bridge (includes polyfill when the API plugin is not installed).
- Multisite — Network defaults with per-site inherit or override.
- Consent log (optional) — Local audit trail with proof snapshots; data never leaves your server.
- Customizable banner — Light/dark themes, bar or box layout, primary color, live admin preview.
- Consent categories — Necessary, Preferences, Statistics, Marketing, plus custom categories.
- Cookie inventory — Manual edits, scanner import, CSV export.
- Integrations — Google Site Kit, Contact Form 7 (reCAPTCHA deferred), iframe placeholders.
- Tools — JSON export/import of settings between sites.
- Languages — Editable EN/DE strings; Polylang/WPML-friendly.
- Activate the plugin and open Privaro Cookie Consent Banner in wp-admin.
- Configure the Banner tab (texts, colors, policy URLs).
- Enable Integrations → Google Consent Mode v2 and Script blocker if you use analytics/ads.
- Run the Scanner and save cookies to your inventory.
- Add
[wpeu_cookie_policy]/[wpeu_cookie_declaration]to your legal pages and[wpeu_manage_consent]to the footer. - Test in a private browser window — analytics tags should stay blocked until consent.
安装:
From WordPress.org (recommended)
- Go to Plugins → Add New in your WordPress admin.
- Search for Privaro Cookie Consent Banner.
- Click Install Now, then Activate.
- Upload the
privaro-cookie-consent-bannerfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Open Privaro Cookie Consent Banner in the admin sidebar.
- Configure the Banner tab (appearance, texts, privacy/cookie policy URLs).
- Enable Integrations (Consent Mode v2, script blocker) if you use Google Analytics, GTM, or ads.
- Run the Scanner and review cookies in the Cookies tab.
- Add shortcodes to your site:
[wpeu_cookie_policy],[wpeu_cookie_declaration],[wpeu_manage_consent].
屏幕截图:
常见问题:
Is this plugin free and open source?
Yes. Privaro Cookie Consent Banner is GPL-licensed. Core compliance features (banner, blocking, scanner, Consent Mode) are included without a premium tier.
Does it use opt-in consent for EU visitors?
Yes. Statistics and marketing categories require explicit consent. Reject all must remain available alongside accept options.
How do I enable Google Consent Mode v2?
Open Integrations in the plugin settings and enable Google Consent Mode v2. The plugin sets default consent to denied and updates Google tags after the visitor chooses in the banner.
Does this plugin block YouTube videos?
Yes. An iframe processor replaces YouTube, Vimeo, and Google Maps embeds with a placeholder until the visitor grants Marketing consent.
What scripts are blocked before consent?
Known patterns include Google Analytics (GA4), Google Tag Manager, Meta Pixel, Hotjar, Microsoft Clarity, and custom URLs you add under Integrations. Blocking uses output buffering on your site's HTML.
Where is the consent log stored?
Entirely in your WordPress database (wp_wpeu_consent_log). No data is sent to external servers. Retention is configurable in settings.
Can I customize banner colors and layout?
Yes. Use the Primary Color picker, layout (bar/box), and light/dark theme on the Banner tab. A live preview is available in the admin.
How do visitors reopen cookie settings later?
Add the [wpeu_manage_consent] shortcode to your footer or template. Optional attributes: style="button" and label="Cookie settings".
Does it work with Google Site Kit?
Yes. The plugin integrates with Site Kit so analytics tags respect consent state.
Multilingual sites?
Edit banner strings per language in settings. The plugin supports Polylang/WPML workflows via standard WordPress translation hooks.
Multisite support?
Yes. Network-wide defaults with per-site inherit or override. Scanner, cookie list, and consent log remain editable on subsites when inheriting.
Does the scanner send data to a third party?
No. The scanner fetches your own site URLs via the WordPress HTTP API and parses responses locally.
Can I migrate from Complianz?
There is no automatic importer. Map categories manually, copy custom block rules, replace shortcodes, run the scanner, and test on staging before deactivating Complianz. See the GitHub README migration checklist.
What are the system requirements?
PHP 8.1 or newer and WordPress 6.4 or newer.
更新日志:
1.3.5
- Fix consent cookies flickering after accept (disable CookieConsent auto script/cookie management; align cookie path/domain with WordPress).
- Fix GA cookie guard clearing analytics cookies right after statistics consent is granted.
- Add admin fields to translate preferences modal intro title/description and cookie settings link label.
- Fix Live Preview fatal recursion (admin AJAX 500) when validating enabled categories.
- Marked compatible with WordPress 7.1.
- WordPress.org review fixes: safer output buffering, sanitized preview settings, validated consent JSON cookie.
- WordPress.org review fixes: local-only blocking patterns, no silent plugin deactivation, escaped shortcode/iframe output, explicit output buffer close.
- Fix multisite inherit toggle so subsites can disable network defaults.
- Limit read-only inherited UI to Banner and Integrations; keep Scanner, Cookies, and Consent Log editable.
- Network Admin overview tab, network language/category management, and per-site consent logging while inheriting.
- Fix missing consent revision bump handler on Tools tab.
- Consent log snapshots v2: banner texts, policy URLs/intro, category labels, UI settings, and SHA-256 content_hash for accountability.
- Snapshot download JSON includes log record plus proof_snapshot bundle.
- Fix Consent Log list table not rendering rows reliably (explicit WP_List_Table columns and admin screen binding).
- Keep Consent Log tab interactive when site inherits multisite network defaults.
- Horizontal scroll for wide consent log table in admin.
- Restore full plugin name in Network Admin menu (Privaro Cookie Consent Banner).
- JSON export uses effective settings (respects multisite network inherit).
- Accept legacy export files from wp-eu-cookie-suite / eu-cookie-consent-suite slugs.
- Remove network default settings on uninstall from the main site.
- Documentation and dev docs aligned with Privaro Cookie Consent Banner branding.
- Fix fatal error on activation when a stale
vendor/autoload.phpexists from a previous install; always register the includes autoloader.
- WordPress Multisite: network default settings and per-site inherit/override toggle.
- SettingsRepository resolves effective settings for frontend and consent flows.
- Prevent fatal error when legacy cookie plugins are still active during migration.
- Guard helper functions with function_exists for safe coexistence during upgrades.
- Fix banner not reappearing after revoke when reload on revoke is disabled.
- Add PHPUnit tests for scanner AJAX, consent log AJAX, admin sanitize, and uninstall.
- Fix CI PHPCS docblock on deprecated Banner method.
- Align admin menu title with plugin name.
- Update admin preview PHPUnit after custom CSS removal.
- Remove obsolete custom-category limit notice.
- Clear IP hash secret on uninstall when data is removed.
- Rename to Privaro Cookie Consent Banner (distinctive slug for WordPress.org).
- Remove custom CSS field and raw analytics injection; use primary color and ACF filter only.
- Remove artificial cap on custom consent categories.
- Use site-specific secret for optional consent log IP hashing (not AUTH_SALT).
- Move inline scripts/styles to wp_enqueue / wp_add_inline_script API.
- Fix namespace order fatal error on activation.
- Fix ConsentLogger.php namespace order missed in 1.0.1.
- Fix fatal error on activation (ABSPATH guard must come after namespace).
- Fix CookieConsent v3 callbacks (onConsent/onChange via cc.run config).
- Defer consent UUID and sync cookies until valid user choice.
- Harden Google resource blocking before consent.
- BREAKING: plugin folder/file/text domain renamed to privaro-cookie-consent-banner — see BREAKING_CHANGES.md in the GitHub repo.
- Initial release on WordPress.org.
- Features: CookieConsent v3 UI, script blocking, cookie scanner, WP Consent API, Google Consent Mode v2.