Intensified Consent Banner
| 开发者 | intensifiedperceptions |
|---|---|
| 更新时间 | 2026年8月14日 19:14 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Vanilla JavaScript only — no jQuery, no framework, a few KB in total
- No frontend database queries — consent state lives in the visitor's browser (cookie plus a localStorage mirror), so static and server-side caching stay fully intact
- No external requests — every asset is served from your own site
- No custom database tables — a single WordPress option, cleanly removed on uninstall
- Links your privacy policy automatically — it uses the page you already marked under Settings → Privacy
- Three consent categories: Necessary, Statistics, Marketing — with equal-weight Accept and Reject buttons, so refusing is as easy as agreeing
- Script blocking by WordPress script handle, per category, for both external and inline scripts
- Iframe blocking for YouTube, Vimeo and Google Maps, replaced by a placeholder that loads nothing until the visitor consents — extendable with your own domains
- Cookie deletion on consent withdrawal, using the name prefixes you configure per category
- Reopen control as shortcode
[zbconsent_settings]and as a block, so consent can be withdrawn as easily as it was given - Light, Dark and Auto appearance with fully customisable colour palettes and six banner positions
- Consent validity configurable from 1 to 365 days
- Fully internationalised; translations are provided through translate.wordpress.org, and custom banner texts integrate with WPML String Translation
- No automatic cookie scanner. You tell the plugin which script handles to block and which cookie names to delete. The bundled guide shows you how to find both in your browser; no coding is required.
- Cookie deletion is first-party only. On withdrawal the plugin deletes cookies you listed, on your own domain. It cannot remove a third party's cookies from a third party's domain, and JavaScript cannot touch
HttpOnlycookies at all. Blocking a script before it runs is the part that actually prevents cookies from being set; deletion is cleanup. - No consent logs and no dashboard. Nothing is written to your database on the frontend, which is what keeps your page cache working. If you need a stored audit trail for a regulator, this plugin does not provide one.
安装:
- Upload the plugin ZIP via Plugins → Add New → Upload Plugin and activate it.
- Go to Settings → Cookie Consent and map your tracking scripts (e.g. Matomo, Google Analytics) to a consent category.
- Add the reopen control to your footer or privacy page: shortcode
[zbconsent_settings]or the "Cookie settings" block. - Optional: configure cookie deletion prefixes, embed categories, colors, and position.
屏幕截图:
常见问题:
Does the plugin automatically detect tracking scripts and cookies?
No — deliberately. You map script handles and cookie prefixes yourself, and the bundled guide shows exactly how to find them in your browser (no coding needed). A scanner would have to run on every page load and guess at anything it has not seen before, and its results would still need manual review to be reliable.
Does it block YouTube and Google Maps embeds?
Yes, automatically. Known embeds (YouTube, Vimeo, Google Maps) are replaced with a neutral placeholder until the visitor consents — no data is sent beforehand, not even for a video thumbnail. You can add any other provider via a URL fragment.
Can it delete third-party cookies?
Only first-party cookies (set under your own domain) can be deleted client-side — that is a browser limitation, not a plugin limitation. HttpOnly cookies and cookies set on foreign domains are out of reach for every consent plugin, whatever its marketing says.
Does it work with caching plugins and server-side caching?
Yes — that is a core design goal. The frontend runs zero database queries; consent state lives entirely in the visitor's browser. Pages remain fully cacheable (Nginx, Varnish, static exports).
Is it multilingual? Does it work with WPML?
The banner is fully internationalised and follows your site language automatically. Translations are provided through translate.wordpress.org, where anyone can contribute, and WordPress installs them for your locale on its own. You can also supply your own: translate languages/intensified-consent-banner.pot with Poedit or Loco Translate and save the result as wp-content/languages/plugins/intensified-consent-banner-{locale}.mo, which survives plugin updates. Custom banner texts integrate with WPML String Translation.
How do I link my privacy policy in the banner?
You probably do not have to do anything. If you marked a page as your privacy policy under Settings → Privacy, the banner links it automatically. To point somewhere else, type a URL into the "Privacy policy link" field. To suppress the link in code, use the zbc_privacy_url filter and return an empty string.
Can I add or correct a translation?
Yes, and it survives plugin updates. Build a .po from languages/intensified-consent-banner.pot, compile it to .mo, and drop it into wp-content/languages/plugins/ as intensified-consent-banner-{locale}.mo. WordPress loads that file in preference to the one shipped with the plugin.
Is this plugin GDPR compliant?
The plugin provides the technical requirements commonly expected for consent management: equal-weight accept/reject, granular categories, no pre-checked boxes, blocking before consent, and easy withdrawal. Actual compliance depends on your configuration, your privacy policy, and your jurisdiction — this plugin is a tool, not legal advice.
更新日志:
- Removed the deprecated
[zbc_settings]shortcode alias and the pre-1.2 option migration; every registered name now carries the plugin prefix
- Renamed to Intensified Consent Banner. The text domain and the plugin folder changed with it; your settings, your saved consent cookies and any
[zbconsent_settings]shortcodes are unaffected
- All internal names now use the longer
zbconsentprefix (classes, constants, option key, script handles, JS globals). Existing settings are migrated automatically on first load - Reopen shortcode is now
[zbconsent_settings] - Inline CSS and admin JavaScript are emitted through
wp_add_inline_style()andwp_add_inline_script()instead of raw tags - The reopen button no longer uses an inline
onclickhandler, so it works under a strict Content Security Policy - Translations are now provided through translate.wordpress.org; bundled .po/.mo files were removed
- readme: documented the external embed providers (YouTube, Vimeo, Google Maps) and reworded the description
- Plugin Check clean: escaping made explicit at every output site, translators comment added
- The plugin now boots on
initinstead ofplugins_loaded, so WordPress loads the translations itself. The manualload_plugin_textdomain()call is gone - Colour values are re-validated as hex when the CSS is rendered, not only when saved
- New: the banner can link your privacy policy. Leave the field empty and it uses the page marked under Settings → Privacy; type a URL to point somewhere else
- New:
zbc_privacy_urlfilter to override the link in code - Added a link to the online playground on the settings page
- WPML string names for the banner title and text are now English (they were German)
- Added a link to the online playground on the settings page
- WPML string names for the banner title and text are now English (they were German)
- Fixed: leftover German placeholder in Blocked scripts field; marketing purge field now shows a Meta Pixel example
- Wording: caching benefit stated consistently across plugin header, readme, and documentation
- Fixed: embed placeholder handling for theme-based responsive wrappers (FitVids and similar), including wrappers applied by theme JavaScript after blocking
- Fixed: embed placeholder misplaced inside responsive embed wrappers (WordPress block embeds) — placeholder now fills the reserved aspect-ratio space
- First stable release
- Documentation restructured: slim README plus detailed guides (configuration, cookies, troubleshooting)
- Consent cookie documented for privacy policies
- Repository readiness: readme.txt, plugin assets
- Complete user documentation (README.md)
- Sensible defaults: empty banner texts fall back to translated built-in defaults in the site language
- Banner position setting: six placements (bottom/top × left/center/right)
- Larger banner title for clearer hierarchy
- Fixed: translations loading too late, causing English banner on non-English sites (WP 6.7+ JIT interaction)
- Banner position setting
- Full internationalization: English source strings, 11 bundled languages (EN, DE, de_AT, ES, FR, IT, PT, NL, EL, PL, CS, HU), .pot template
- Appearance settings: Light / Dark / Auto mode with two fully customizable color palettes (background, title, text, button, button hover)
- Iframe/embed blocker: automatic YouTube, Vimeo, Google Maps detection with privacy placeholder; custom domains with per-provider category
- Reopen control: shortcode [zbc_settings] and Gutenberg block
- Cookie deletion on consent withdrawal, with per-category prefix configuration
- Minified frontend assets with SCRIPT_DEBUG fallback
- WPML integration for dynamic banner texts (String Translation)
- Settings page: script handle mapping, banner texts, colors
- Fixed: inline scripts without src could lose their type attribute and run unblocked
- Initial release: category-based consent banner, script blocking by handle, cookie + localStorage state, zero frontend DB queries