assets\/js\/chart.min.js<\/code> \u2014 Chart.js library (MIT License). Source code and unminified version available at: https:\/\/github.com\/chartjs\/Chart.js<\/p><\/li>\nassets\/js\/cookieboxs-consent-mode.js<\/code> \u2014 Contains standard third-party integration embed snippets (e.g., Google Tag Manager, Meta Pixel, TikTok Pixel, Microsoft Clarity, Hotjar, LiveChat, Intercom, etc.). These are the official JavaScript snippets provided by each service for website embedding, written in their standard compact form. Each snippet includes a source URL comment pointing to the official documentation. A full list of source URLs is also available in the file header comments. The surrounding plugin logic (consent state management, Google Consent Mode v2 setup, custom script injection) is authored by this plugin and is fully human-readable.<\/p><\/li>\n<\/ul>\n\nOfficial documentation URLs for all embedded third-party snippets:<\/p>\n\n
\n- Google Tag Manager: https:\/\/developers.google.com\/tag-platform\/tag-manager\/web<\/li>\n
- Meta Pixel: https:\/\/developers.facebook.com\/docs\/meta-pixel\/get-started<\/li>\n
- TikTok Pixel: https:\/\/ads.tiktok.com\/help\/article\/get-started-pixel<\/li>\n
- Microsoft Clarity: https:\/\/learn.microsoft.com\/en-us\/clarity\/setup-and-installation\/clarity-setup<\/li>\n
- Hotjar: https:\/\/help.hotjar.com\/hc\/en-us\/articles\/115011639927<\/li>\n
- Heap Analytics: https:\/\/developers.heap.io\/docs\/web<\/li>\n
- Mixpanel: https:\/\/docs.mixpanel.com\/docs\/tracking-methods\/sdks\/javascript<\/li>\n
- PostHog: https:\/\/posthog.com\/docs\/libraries\/js<\/li>\n
- LinkedIn Insight Tag: https:\/\/learn.microsoft.com\/en-us\/linkedin\/marketing\/integrations\/ads-reporting\/insight-tag<\/li>\n
- Pinterest Tag: https:\/\/help.pinterest.com\/en\/business\/article\/install-the-pinterest-tag<\/li>\n
- Snapchat Pixel: https:\/\/businesshelp.snapchat.com\/s\/article\/snap-pixel-about<\/li>\n
- Twitter\/X Pixel: https:\/\/business.x.com\/en\/help\/campaign-measurement-and-analytics\/conversion-tracking-for-websites<\/li>\n
- Microsoft Advertising UET: https:\/\/help.ads.microsoft.com\/apex\/index\/3\/en\/56682<\/li>\n
- LiveChat: https:\/\/developers.livechat.com\/docs\/getting-started\/installing-livechat<\/li>\n
- Crisp: https:\/\/docs.crisp.chat\/guides\/chatbox-sdks\/web-sdk\/<\/li>\n
- Tawk.to: https:\/\/help.tawk.to\/article\/adding-a-tawk-to-widget-to-your-website<\/li>\n
- Intercom: https:\/\/developers.intercom.com\/installing-intercom\/web\/installation<\/li>\n
- Yandex Metrica: https:\/\/yandex.com\/support\/metrica\/code\/counter-initialize.html<\/li>\n
- Matomo: https:\/\/developer.matomo.org\/guides\/tracking-javascript-guide<\/li>\n<\/ul>\n\n
Privacy Policy<\/h3>\n\n
CookieBoxs does not send visitor consent records to the plugin author's servers.<\/p>\n\n
Consent records are stored in the WordPress database. Optional third-party integrations that you configure, such as analytics, advertising, chat, or embedded media services, connect directly from the visitor's browser to those third-party providers after the relevant consent conditions are met.<\/p>\n\n
Admin-only connections used for plugin news, optional deactivation feedback, or optional license validation are described below.<\/p>\n\n
External Services<\/h3>\n\n
This plugin uses external services only for user-configured integrations. Third-party integrations are optional, disabled by default, and only activated when the site administrator enables and configures them. The plugin does not offload any of its own assets (JavaScript, CSS, images) to external servers \u2014 all plugin files are included locally.<\/p>\n\n
Plugin services<\/h4>\n\n\nVisionSolutions API - plugin news and updates<\/strong>: used in the admin area only; sends plugin version, WordPress version, and site language when an administrator opens the settings page. Provider: VisionSolutions, https:\/\/visionsolutions.pl\nTerms of use: https:\/\/visionsolutions.pl\/regulamin\/\nPrivacy policy: https:\/\/visionsolutions.pl\/polityka-prywatnosci\/<\/p><\/li>\nVisionSolutions API - deactivation feedback (optional)<\/strong>: sends selected reason, optional comment, site URL, WordPress version, and PHP version only if an administrator submits feedback during deactivation. Provider: VisionSolutions\nTerms of use: https:\/\/visionsolutions.pl\/regulamin\/\nPrivacy policy: https:\/\/visionsolutions.pl\/polityka-prywatnosci\/<\/p><\/li>\nVisionSolutions API - PRO license validation (optional)<\/strong>: sends license key, site domain, and plugin version on activation and periodic validation. Provider: VisionSolutions\nTerms of use: https:\/\/visionsolutions.pl\/regulamin\/\nPrivacy policy: https:\/\/visionsolutions.pl\/polityka-prywatnosci\/<\/p><\/li>\nipapi.co geolocation API (optional, PRO)<\/strong>: used only when geo-targeting is enabled and fallback geolocation is needed; sends visitor IP address. Provider: ipapi\nTerms of use: https:\/\/ipapi.co\/terms\/\nPrivacy policy: https:\/\/ipapi.co\/privacy\/<\/p><\/li>\nCookie Scanner (admin-initiated, PRO)<\/strong>: two-phase scan. Phase 1 (server): sends requests from your server to your own website pages to detect cookies and tracking scripts from HTML. Phase 2 (browser): loads the scanned page in a hidden iframe within the administrator's browser to detect cookies set by JavaScript (e.g. pixels loaded via Google Tag Manager). All scanning happens locally \u2014 no external provider is contacted.<\/p><\/li>\n<\/ul>\n\nOptional integrations (services)<\/h4>\n\n
These are third-party services that the site administrator can optionally enable. When enabled, the plugin loads the official embed snippet provided by each service, which connects the visitor's browser directly to that service provider. These are service integrations, not offloaded plugin assets. Each integration is disabled by default and only activates when the administrator provides their account ID.<\/p>\n\n
\nGoogle Tag Manager<\/strong> - tag management service; may load on page view and use Consent Mode signals. Loaded from: www.googletagmanager.com. Provider: Google LLC.\nTerms of use: https:\/\/marketingplatform.google.com\/about\/analytics\/terms\/us\/\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nGoogle Analytics 4<\/strong> - analytics service; loaded from www.googletagmanager.com\/gtag\/js via wp_enqueue_script. Provider: Google LLC.\nTerms of use: https:\/\/marketingplatform.google.com\/about\/analytics\/terms\/us\/\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nGoogle Ads<\/strong> - conversion tracking and remarketing service; loaded from www.googletagmanager.com\/gtag\/js via wp_enqueue_script. Provider: Google LLC.\nTerms of use: https:\/\/ads.google.com\/intl\/en\/home\/terms\/\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nMeta Pixel<\/strong> - advertising measurement service; loaded from connect.facebook.net. Provider: Meta Platforms, Inc.\nTerms of use: https:\/\/www.facebook.com\/legal\/terms\nPrivacy policy: https:\/\/www.facebook.com\/privacy\/policy\/<\/p><\/li>\nTikTok Pixel<\/strong> - advertising measurement service; loaded from analytics.tiktok.com. Provider: TikTok Inc. \/ ByteDance Ltd.\nTerms of use: https:\/\/ads.tiktok.com\/i18n\/official\/policy\/business-products-terms\nPrivacy policy: https:\/\/www.tiktok.com\/legal\/privacy-policy<\/p><\/li>\nMicrosoft Clarity<\/strong> - session analytics and heatmaps service; loaded from www.clarity.ms. Provider: Microsoft Corporation.\nTerms of use: https:\/\/clarity.microsoft.com\/terms\nPrivacy policy: https:\/\/privacy.microsoft.com\/en-us\/privacystatement<\/p><\/li>\nHotjar<\/strong> - heatmaps, recordings, and feedback service; loaded from static.hotjar.com. Provider: Hotjar Ltd.\nTerms of use: https:\/\/www.hotjar.com\/legal\/policies\/terms-of-service\/\nPrivacy policy: https:\/\/www.hotjar.com\/legal\/policies\/privacy\/<\/p><\/li>\nMatomo<\/strong> - analytics service; loaded from the site administrator's configured Matomo instance URL. Provider: InnoCraft Ltd. or the site owner's Matomo host.\nTerms of use: https:\/\/matomo.org\/matomo-cloud-terms-of-service\/\nPrivacy policy: https:\/\/matomo.org\/matomo-cloud-privacy-policy\/<\/p><\/li>\nYandex Metrica<\/strong> - analytics service; loaded from mc.yandex.ru. Provider: Yandex LLC.\nTerms of use: https:\/\/yandex.com\/legal\/metrica_termsofuse\/\nPrivacy policy: https:\/\/yandex.com\/legal\/confidential\/<\/p><\/li>\nHeap Analytics<\/strong> - analytics service; loaded from cdn.heapanalytics.com. Provider: Heap Inc.\nTerms of use: https:\/\/heap.io\/legal\/heap-terms-of-service\nPrivacy policy: https:\/\/heap.io\/legal\/privacy<\/p><\/li>\nMixpanel<\/strong> - analytics service; loaded from cdn.mxpnl.com. Provider: Mixpanel, Inc.\nTerms of use: https:\/\/mixpanel.com\/legal\/terms-of-use\/\nPrivacy policy: https:\/\/mixpanel.com\/legal\/privacy-policy\/<\/p><\/li>\nPostHog<\/strong> - analytics and feature flags service; loaded from the site administrator's configured PostHog host. Provider: PostHog, Inc.\nTerms of use: https:\/\/posthog.com\/terms\nPrivacy policy: https:\/\/posthog.com\/privacy<\/p><\/li>\nLinkedIn Insight Tag<\/strong> - advertising measurement service; loaded from snap.licdn.com. Provider: LinkedIn Corporation.\nTerms of use: https:\/\/www.linkedin.com\/legal\/l\/li-marketing-terms\nPrivacy policy: https:\/\/www.linkedin.com\/legal\/privacy-policy<\/p><\/li>\nPinterest Tag<\/strong> - advertising measurement service; loaded from s.pinimg.com. Provider: Pinterest, Inc.\nTerms of use: https:\/\/policy.pinterest.com\/en\/terms-of-service\nPrivacy policy: https:\/\/policy.pinterest.com\/en\/privacy-policy<\/p><\/li>\nSnapchat Pixel<\/strong> - advertising measurement service; loaded from sc-static.net. Provider: Snap Inc.\nTerms of use: https:\/\/snap.com\/en-US\/terms\nPrivacy policy: https:\/\/snap.com\/en-US\/privacy\/privacy-policy<\/p><\/li>\nTwitter\/X Pixel<\/strong> - advertising measurement service; loaded from static.ads-twitter.com. Provider: X Corp.\nTerms of use: https:\/\/twitter.com\/en\/tos\nPrivacy policy: https:\/\/twitter.com\/en\/privacy<\/p><\/li>\nMicrosoft Advertising UET<\/strong> - conversion tracking service; loaded from bat.bing.com. Provider: Microsoft Corporation.\nTerms of use: https:\/\/about.ads.microsoft.com\/en-us\/policies\/legal\nPrivacy policy: https:\/\/privacy.microsoft.com\/en-us\/privacystatement<\/p><\/li>\nIntercom<\/strong> - customer messaging service; loaded from widget.intercom.io and api-iam.intercom.io. Provider: Intercom, Inc.\nTerms of use: https:\/\/www.intercom.com\/legal\/terms-and-policies\nPrivacy policy: https:\/\/www.intercom.com\/legal\/privacy<\/p><\/li>\nLiveChat<\/strong> - support chat service; loaded from cdn.livechatinc.com. Provider: LiveChat, Inc.\nTerms of use: https:\/\/www.livechat.com\/legal\/terms-of-service\/\nPrivacy policy: https:\/\/www.livechat.com\/legal\/privacy-policy\/<\/p><\/li>\nCrisp<\/strong> - customer messaging and chat service; loaded from client.crisp.chat. Provider: Crisp IM SAS.\nTerms of use: https:\/\/crisp.chat\/en\/terms\/\nPrivacy policy: https:\/\/crisp.chat\/en\/privacy\/<\/p><\/li>\nTawk.to<\/strong> - support chat service; loaded from embed.tawk.to. Provider: Tawk.to Ltd.\nTerms of use: https:\/\/www.tawk.to\/legal\/terms-of-service\/\nPrivacy policy: https:\/\/www.tawk.to\/legal\/privacy-policy\/<\/p><\/li>\n<\/ul>\n\nScript blocker safe domains<\/h4>\n\n
The automatic script blocker does not block scripts from essential service domains (payment gateways, CAPTCHAs, translation). These domains are whitelisted so the script blocker does not interfere with site-critical functionality provided by other plugins or themes. The CookieBoxs plugin itself does not load any files from these domains \u2014 they are only whitelisted to prevent breakage:<\/p>\n\n
\nStripe<\/strong> - payment processing service; loaded by other plugins from js.stripe.com and checkout.stripe.com. Provider: Stripe, Inc.\nTerms of use: https:\/\/stripe.com\/legal\/ssa\nPrivacy policy: https:\/\/stripe.com\/privacy<\/p><\/li>\nPayPal<\/strong> - payment processing service; loaded by other plugins from www.paypal.com and www.paypalobjects.com. Provider: PayPal Holdings, Inc.\nTerms of use: https:\/\/www.paypal.com\/us\/legalhub\/useragreement-full\nPrivacy policy: https:\/\/www.paypal.com\/us\/legalhub\/privacy-full<\/p><\/li>\nGoogle reCAPTCHA<\/strong> - spam protection service; loaded by other plugins from recaptcha.net. Provider: Google LLC.\nTerms of use: https:\/\/policies.google.com\/terms\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nhCaptcha<\/strong> - spam protection service; loaded by other plugins from js.hcaptcha.com. Provider: Intuition Machines, Inc.\nTerms of use: https:\/\/www.hcaptcha.com\/terms\nPrivacy policy: https:\/\/www.hcaptcha.com\/privacy<\/p><\/li>\nCloudflare Turnstile<\/strong> - bot protection service; loaded by other plugins from challenges.cloudflare.com. Provider: Cloudflare, Inc.\nTerms of use: https:\/\/www.cloudflare.com\/terms\/\nPrivacy policy: https:\/\/www.cloudflare.com\/privacypolicy\/<\/p><\/li>\nGoogle Translate<\/strong> - translation service widget; loaded by other plugins from translate.google.com and translate.googleapis.com. Provider: Google LLC.\nTerms of use: https:\/\/policies.google.com\/terms\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\n<\/ul>\n\nContent blockers<\/h4>\n\n
Content blockers are an optional feature that replaces embedded third-party media (YouTube, Vimeo, Google Maps) with a placeholder until the visitor grants consent. When consent is given, the embed loads normally from the service provider.<\/p>\n\n
\nYouTube<\/strong> - video embeds can be blocked until consent; loaded from www.youtube.com and www.youtube-nocookie.com. Provider: Google LLC.\nTerms of use: https:\/\/www.youtube.com\/t\/terms\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nVimeo<\/strong> - video embeds can be blocked until consent; loaded from player.vimeo.com and vimeo.com. Provider: Vimeo, Inc.\nTerms of use: https:\/\/vimeo.com\/terms\nPrivacy policy: https:\/\/vimeo.com\/privacy<\/p><\/li>\nGoogle Maps<\/strong> - map embeds can be blocked until consent; loaded from www.google.com\/maps and maps.googleapis.com. Provider: Google LLC.\nTerms of use: https:\/\/cloud.google.com\/maps-platform\/terms\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\n<\/ul>\n\n\n\n- Upload the
cookieboxs<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n- Activate the plugin in WordPress.<\/li>\n
- Go to Settings -> CookieBoxs.<\/li>\n
- Choose your language and region preset.<\/li>\n
- Configure the integrations you want to use.<\/li>\n
- Save your settings.<\/li>\n<\/ol>\n\n\n
\nDoes it include Google Consent Mode v2?<\/h3><\/dt>\nYes.<\/p><\/dd>\n
Does the plugin guarantee legal compliance?<\/h3><\/dt>\nNo. CookieBoxs is a technical tool that can help with consent management and privacy-related configuration. Site owners remain responsible for reviewing their legal obligations, policies, and third-party services.<\/p><\/dd>\n
Does it block scripts before consent?<\/h3><\/dt>\nThe plugin includes an automatic script blocker and cookie cleaner. Built-in integrations are designed to load according to their assigned consent category. Google Tag Manager may load earlier and rely on Consent Mode signals, depending on configuration.<\/p><\/dd>\n
Can I customize the banner text?<\/h3><\/dt>\nYes. Banner text, category labels, and descriptions can be customized in the plugin settings.<\/p><\/dd>\n
How do I add custom scripts?<\/h3><\/dt>\nGo to Settings -> CookieBoxs -> Custom Scripts and assign the script to a consent category.<\/p><\/dd>\n
Is it compatible with caching plugins and page builders?<\/h3><\/dt>\nCookieBoxs is designed to work with common caching plugins and standard WordPress themes and builders.<\/p><\/dd>\n
Does it support multisite?<\/h3><\/dt>\nYes.<\/p><\/dd>\n
How do I show a link to reopen cookie settings?<\/h3><\/dt>\nUse the shortcode [cookieboxs_settings]<\/code> or enable the floating badge.<\/p><\/dd>\n\n<\/dl>\n\n\n3.3.7<\/h4>\n\n\n- Fixed (critical): enabling Google Maps under Blocking could blank the entire page content on posts\/pages that ran through the_content. An unescaped slash in the \"google.com\/maps\" match pattern broke the regex, so the content filter returned nothing. The pattern is now escaped correctly and the filter can never return empty content (it falls back to the original content if anything goes wrong).<\/li>\n
- Fixed: the floating badge icon selector now actually works \u2014 Cookie, Gear, Shield, Lock and Fingerprint each render their own crisp icon, and the icon size is now protected against theme CSS that previously distorted it.<\/li>\n
- Added (PRO): upload your own badge icon \u2014 paste custom SVG markup under Badge settings to replace the built-in icon. Sanitized through a strict allowlist (no scripts, event handlers or external references).<\/li>\n
- Added (PRO): a
cookieboxs_banner_template<\/code> filter so developers can ship a fully custom banner template (your own markup\/classes, styled freely from your stylesheet). The path is validated and safely falls back to the bundled template.<\/li>\n- Added (PRO): \"Minimal CSS mode\" toggle (Design tab) \u2014 one switch for developer styling. When ON it applies your Custom CSS and strips the banner's built-in cosmetic !important (colors, borders, radius, shadow, spacing, fonts) so your CSS fully controls the look without swapping the template. When OFF the banner uses only its built-in design and the Custom CSS is ignored (clean revert). Positioning, stacking and visibility always stay protected. The live design preview reflects your Custom CSS in real time while this mode is on.<\/li>\n
- Added (PRO): a built-in CSS selector cheat-sheet under the Custom CSS box (Design tab), so you can style the banner without opening the browser console.<\/li>\n
- Fixed: the corner branding \/ white-label logo no longer overlaps the title text in some layouts \u2014 it now floats so the text wraps cleanly around it, and a wide company logo is scaled to fit (aspect ratio preserved).<\/li>\n<\/ul>\n\n
3.3.6<\/h4>\n\n\n- Compliance: renamed the design editor's internal JavaScript globals to the cookieboxs- prefix (guideline: unique prefixes), sanitized the logging-toggle AJAX input, fully prepared all consent-record queries via the %i identifier placeholder (with explicit phpcs annotations), and escaped a banner output value at the point of output. No functional changes.<\/li>\n
- Added (PRO): full banner design editor parity \u2014 one-click style presets (incl. a full-width bottom \"bar\", dark and sidebar layouts), a 3x3 position grid plus full-width Top\/Bottom bar buttons, a width slider, screen backdrop (none\/dim\/blur), and segmented controls for font, shadow, spacing, buttons and animation. Two-column layout with a sticky live preview and an in-panel \"Save changes\" button.<\/li>\n
- Improved (PRO): the live preview now reproduces the frontend 1:1 (real template CSS), so the shadow and corner-radius controls are reflected immediately; \"Match my site\" normalizes the detected color and confirms when applied.<\/li>\n
- Fixed (PRO): the frontend now honors the custom background and text colors from the design editor \/ presets (e.g. the Dark preset renders a dark banner), with light\/dark UI accents derived from the background.<\/li>\n
- Fixed (PRO): the Sidebar layout is now a true full-height panel on desktop.<\/li>\n
- Improved (PRO): A\/B testing \u2014 Variant B can now also override the banner description (text A\/B), and you can preview a specific variant on any page with ?cb_ab=A or ?cb_ab=B.<\/li>\n
- Improved: clicking the floating settings badge now re-opens the preferences panel with the visitor's current choices, instead of clearing consent and reloading.<\/li>\n
- Added: a one-time review request notice after ~30 days; other plugins' admin notices are hidden on the CookieBoxs settings screen to keep it clean.<\/li>\n
- Added: consent-logging can be toggled directly from the Analytics tab (instant save), and the cookie scanner checklist now has tooltips and fix links.<\/li>\n
- Security: custom-script fields are now editable only by users with the unfiltered_html capability \u2014 non-privileged saves (e.g. Multisite site admins) can no longer inject executable JavaScript that runs for visitors.<\/li>\n
- Hardening: consent-record queries are fully prepared via the %i identifier placeholder, the logging-toggle AJAX input is sanitized, and a banner output value is escaped at the point of output.<\/li>\n<\/ul>\n\n
3.2.0<\/h4>\n\n\n- Added (PRO): Consent Records \u2014 a tamper-proof proof-of-consent log. Each consent stores a unique token, the chosen categories, the banner and policy version it was given against, a hashed IP, country, language and timestamp. Browse with date\/method filters, export to CSV (with formula-injection protection), and open a printable consent certificate for any record. A configurable retention period deletes old records automatically (GDPR storage limitation), and records can be deleted individually or in bulk.<\/li>\n
- Added (PRO): A\/B testing of the cookie banner. Visitors are split 50\/50 (sticky per visitor) between Variant A (your live banner) and Variant B (an override of the title, accept-button text and accept-button color). The variant is recorded with each consent and the dashboard shows the accept-all rate per variant, the winner and the relative lift \u2014 so you can optimise opt-in rates with real data.<\/li>\n
- Added (PRO): banner design editor. A dedicated Design tab with a real-time live preview and an \"Appearance & Buttons\" panel \u2014 choose a font (system\/geometric\/serif\/rounded\/mono\/condensed, no Google CDN), shadow depth, spacing, button style (filled\/outline\/soft\/pill), reject-button style (outline\/ghost\/link), button size, layout (row\/stacked\/full width), corner radius, uppercase, accept-button text color, and an entrance animation (fade\/slide\/scale, honoring prefers-reduced-motion). A one-click \"Match my site\" pulls a brand color from your theme (theme.json palette or Customizer). Every default reproduces the previous look exactly, so existing sites are unchanged until you edit something.<\/li>\n
- Added (PRO): granular per-service consent. With it on, the \"Customize\" modal lists each configured integration with its own toggle under its category, so visitors can allow some services and deny others within the same category (e.g. allow Google Analytics but deny Hotjar). A category master toggle still selects\/clears all of its services at once. Gating is client-side, so it stays compatible with page caching, and old consent cookies keep working (category-level decision applies until the visitor updates their choice).<\/li>\n
- Improved: automatic language detection (free). A fresh install now picks the banner language from your WordPress site language (Settings -> General) instead of a fixed default, and on a single-language site (no Polylang\/WPML\/TranslatePress) the banner follows the WordPress site language automatically \u2014 e.g. a German WordPress shows a German banner out of the box. The \"Auto-detect language\" toggle on the General tab is now always available, so you can switch back to a fixed language at any time. Any banner wording you customized is always preserved.<\/li>\n
- Security: the consent-logging endpoint is rate-limited per hashed IP; the banner\/policy version, consent token and A\/B variant are all stamped server-side (never trusted from the client); the method, language and A\/B variant are whitelisted; and the source URL is verified against your own site host.<\/li>\n
- Note: Consent Records, A\/B testing and granular per-service consent are PRO features. Automatic language detection is free.<\/li>\n<\/ul>\n\n
3.1.0<\/h4>\n\n\n- Added: 29 new interface languages, bringing the total to 40. New languages: Turkish, Russian, Japanese, Chinese (Simplified), Danish, Finnish, Norwegian, Greek, Romanian, Hungarian, Slovak, Slovenian, Bulgarian, Croatian, Estonian, Latvian, Lithuanian, Irish, Indonesian, Arabic, Korean, Hebrew, Maltese, Vietnamese, Thai, Hindi, Persian (Farsi), Malay, Serbian. CookieBoxs now ships complete translations (392 strings each) for all 24 official EU languages plus major global languages (Asia, Middle East) \u2014 no cloud, no external translation service, all bundled locally.<\/li>\n
- Added: right-to-left (RTL) layout support. When the banner language is Arabic, Hebrew or Persian, the banner and settings modal automatically render with dir=\"rtl\".<\/li>\n
- Added: multilingual compatibility. When Polylang, WPML, TranslatePress or qTranslate-XT is active, the banner automatically follows the language of the page each visitor is viewing (e.g. \/fr\/ shows the French banner, \/de\/ the German one). The fixed language in settings becomes the fallback. A toggle on the General tab lets you turn auto-detection off, and a
cookieboxs_current_language<\/code> filter is available for custom setups.<\/li>\n- Tested: full compatibility with WordPress 7.0.<\/li>\n
- Note: translations for smaller languages (Maltese, Irish, Baltic) are a best effort \u2014 community corrections are welcome via the support forum.<\/li>\n<\/ul>\n\n
3.0.14<\/h4>\n\n\n- Removed: noisy \"we disabled features for you\" admin notice that 3.0.9 shipped after the auto-migration of
script_blocker<\/code> \/ block_youtube<\/code> \/ block_vimeo<\/code> \/ block_maps<\/code>. The notice was sticky on every admin screen until dismissed, which became annoying. Settings \u2192 Blockers now carries a red warning card (added in 3.0.13) that explains the same information in-context, so the global banner is no longer needed.<\/li>\n- Cleanup: the
cookieboxs_show_3_0_9_migration_notice<\/code> option is now deleted on upgrade so leftover flags from previous installs don't accumulate. Removed show_3_0_9_migration_notice()<\/code> and maybe_dismiss_migration_notice()<\/code> methods together with their hooks (admin_notices<\/code>, admin_init<\/code> for dismiss).<\/li>\n<\/ul>\n\n3.0.13<\/h4>\n\n\n- UX: redesigned the Automatic Script Blocker card in Settings \u2192 Blockers and in the setup wizard. The card now has a red warning frame instead of the previous indigo \"recommended\" frame, the toggle label reads \"NOT recommended\" in red, and a prominent multi-line warning explains that the feature can prevent parts of the page from rendering (especially with page builders like Elementor or caching plugins like LiteSpeed\/WP Rocket) and that it must be tested on staging before enabling in production.<\/li>\n
- Defaults: the wizard checkbox is now unchecked by default, the wizard form handler stores
script_blocker = false<\/code> for fresh installs, and the wizard summary screen no longer mis-reports the off state as a problem (it now shows \"\u2717 Off (recommended)\" in neutral grey).<\/li>\n- Translated: 2 new translation keys (
sb_warning<\/code>, sb_not_recommended<\/code>) added to all 11 language files. The warning is fully localised in English, Polish, German, French, Spanish, Italian, Dutch, Czech, Portuguese, Swedish and Ukrainian.<\/li>\n<\/ul>\n\n3.0.12<\/h4>\n\n\n- Fixed: Plugin Check warning
upgrade_notice_limit<\/code> \u2014 the Upgrade Notice entries for 3.0.8, 3.0.9 and 3.0.10 exceeded the 300-character limit set by WordPress.org. The text has been trimmed without losing the essential information.<\/li>\n<\/ul>\n\n3.0.11<\/h4>\n\n\n- Hardening: wrapped 7 ternary-string
echo<\/code> expressions in templates\/admin.php<\/code> with esc_attr()<\/code> or esc_html()<\/code> even though they return hardcoded literal CSS classes \/ glyphs. Defends against future code changes that might accidentally let user data flow into those expressions, and satisfies the strict \"escape every echo\" rule enforced by WordPress.org Plugin Check.<\/li>\n- Hardening: when the cookie scanner extracts a
cookieboxsIntegrations = {...}<\/code> JSON fragment from the homepage HTML (the homepage is fetched server-side via wp_remote_get()<\/code>), the fragment is now passed through sanitize_text_field()<\/code> before json_decode()<\/code>. The output is still gated by an is_array()<\/code> check and only scalar keys are read, but the extra sanitization makes the defensive intent explicit.<\/li>\n<\/ul>\n\n3.0.10<\/h4>\n\n\n- Fixed: per-category custom code textareas (Necessary \/ Functional \/ Analytics \/ Marketing) silently dropped any snippet that included the surrounding
<script><\/code> tags. Site owners who copied the full official snippet from the provider's documentation (e.g. Microsoft Clarity, Google Analytics, Hotjar, Tawk.to) would see no error but the tracker would never run, because the JavaScript body was passed to new Function()<\/code> together with literal <script><\/code> text which causes a SyntaxError. The plugin now strips the wrappers (and legacy HTML comment \/ CDATA markers) before evaluation, so BOTH formats \u2014 pure JS body OR full <script>\u2026<\/script><\/code> snippet \u2014 work.<\/li>\n- Added: Google Ads \"Conversion label\" input field under the Google Ads ID input on the Integrations tab. The
int_gads_label<\/code> option had been stored and passed to the frontend conversion event since earlier releases but there was no UI to set it. Translated label placeholder added to all 11 language files.<\/li>\n- Improved: custom-code textarea placeholders now show concrete copy-paste examples (Microsoft Clarity snippet on the Analytics card) and the category headings on the custom-scripts tab are properly translated instead of being hardcoded in Polish.<\/li>\n<\/ul>\n\n
3.0.9<\/h4>\n\n\n- Fixed: Auto Script Blocker and the YouTube\/Vimeo\/Google Maps embed blockers were reported to break page rendering on sites that combine Elementor (4.x) with LiteSpeed Web Server \/ WP Rocket \/ other complex caching setups. The visible symptom was an empty hero \/ content area while the header and footer rendered normally.<\/li>\n
- Migration: when a site updates from 3.0.7 or 3.0.8 to 3.0.9, the four problem options (
script_blocker<\/code>, block_youtube<\/code>, block_vimeo<\/code>, block_maps<\/code>) are force-disabled. The cookie banner, Google Consent Mode v2, integrations and consent logging keep working as before. A one-time dismissible admin notice (translated to all 11 languages) explains the change and links to Settings where the options can be re-enabled after testing on staging.<\/li>\n- Added:
cookieboxs_db_version<\/code> option to track the last-migrated plugin version so future migrations run exactly once per upgrade, even when WordPress updates the plugin in place without firing register_activation_hook<\/code>.<\/li>\n- Translated: 3 new translation keys (
migration_3_0_9_notice<\/code>, migration_3_0_9_button_settings<\/code>, migration_3_0_9_button_dismiss<\/code>) added to all 11 language files (389 keys total per file).<\/li>\n<\/ul>\n\n3.0.8<\/h4>\n\n\n- Fixed: site rendering as \"footer only\" or blank after activation when a page builder or full-page cache plugin was active. The automatic script blocker now records its output buffer level and verifies stack alignment on shutdown, so it never closes a buffer that belongs to another plugin or theme.<\/li>\n
- Fixed: structural bug in 9 language files (cs, de, es, fr, it, nl, pt, sv, uk) \u2014 five wizard keys (wiz_gcm_enable, wiz_gcm_info, wiz_recommended, wiz_sb_enable, wiz_sb_info) were stored at top level but read from admin.* by the plugin, so existing translations were silently ignored. Keys moved to admin.* in all affected files.<\/li>\n
- Translated: filled all missing translations in 8 language files \u2014 fr (83), es (119), it (119), nl (130), cs (135), pt (135), sv (135), uk (135). All 11 languages now ship at 100% coverage. Brand and industry-standard names (Google Maps, Google Consent Mode v2, White Label, Marketing, Retargeting, Powered by CookieBoxs) are preserved as-is.<\/li>\n
- Fixed: 46 hardcoded Polish strings in PHP and JavaScript files (cookieboxs.php, templates\/admin.php, templates\/banner.php, templates\/news.php, assets\/js\/cookieboxs-admin.js) were appearing regardless of the user's language selection. Replaced with translation keys read from the language JSON files. 70 cookie scanner descriptions normalised to English (industry standard, matching Cookiepedia\/Termly conventions).<\/li>\n
- Translated: 26 new translation keys added to all 11 language files (386 keys total per file). Covers license activation messages, badge appearance options, scanner UI, GCM notices, news widget and Pixel-plugin detection notice.<\/li>\n
- Improved: cookie scanner now detects Facebook\/Meta Pixel installations made through dedicated manager plugins (PixelYourSite Free\/Pro, Pixel Manager for WooCommerce, Official Facebook Pixel, Meta for WooCommerce, Pixel Cat, Pixel Caffeine, WP Pixel Manager, Webby Pixel Master). When one of these plugins is active, _fbp, _fbc and fr cookies are added to the detected list \u2014 even if the Pixel snippet is loaded indirectly (via GTM or after consent) and would not appear in the HTML-only scan. Applies to both the free and PRO scanners.<\/li>\n
- Added: post-scan notice that lists detected Pixel manager plugins so site owners know which plugin is responsible for the marketing cookies.<\/li>\n
- Fixed: script blocker was corrupting its own
data-cookieboxs-src<\/code> attribute. The regex that strips the original src=<\/code> from a blocked script tag also matched src=<\/code> inside the freshly injected data-cookieboxs-src=<\/code> attribute (because the hyphen counts as a word boundary in PCRE), leaving a truncated data-cookieboxs-<\/code> and no URL. The result was that blocked third-party scripts (jsBarcode for WooCommerce product barcodes, TrustIndex review widget, etc.) could never be restored after the visitor accepted cookies \u2014 leading to \"the page is missing parts\" reports. Operations are now reordered: strip the original src=<\/code> first, then inject the new attributes.<\/li>\n- Improved: cookie blocker now recognises common UI \/ functional JavaScript libraries served from generic CDNs (jsBarcode, QRCode, Swiper, Owl Carousel, Slick, jQuery, Lodash, Popper, Moment, lazysizes, Flickity, AOS, Lightbox\/Fancybox, Leaflet, Chart.js, etc.) and routes them to the
functional<\/code> consent category instead of the default marketing<\/code> bucket. Visitors who decline marketing cookies will keep seeing product barcodes, sliders and other display features.<\/li>\n- Added:
cookieboxs_default_unknown_category<\/code> filter so site owners can change the fallback category for unknown external scripts (default remains marketing<\/code> for GDPR safety).<\/li>\n- Added: automatic detection of incompatible output-filtering plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, Autoptimize, Hummingbird, WP-Optimize, Cache Enabler, Breeze, SG Optimizer, Powered Cache, FlyingPress, NitroPack, Perfmatters). When one of these is active, the automatic script blocker is skipped and consent is enforced through the standard category gating instead.<\/li>\n
- Added:
cookieboxs_disable_script_blocker<\/code> filter so site owners and other plugins can opt out of the automatic blocker per request.<\/li>\n- Changed: automatic script blocker now defaults to OFF for new installs and for upgrades from versions that did not have the option. Existing users keep their current setting.<\/li>\n<\/ul>\n\n
3.0.7<\/h4>\n\n\n- Added two-phase Cookie Scanner: server-side HTML detection + browser-based JavaScript cookie detection via hidden iframe.<\/li>\n
- Browser scan detects cookies set by GTM-loaded scripts (Meta Pixel, TikTok Pixel, etc.) that server-side scanning cannot see.<\/li>\n
- Expanded cookie detection patterns: 55+ known cookies from 30+ providers.<\/li>\n
- Added PRO tools including geo-targeting, additional templates, declaration, analytics, branding controls, and custom CSS.<\/li>\n
- Improved PRO settings UI.<\/li>\n
- Bundled Chart.js locally for PRO analytics.<\/li>\n
- Fixed settings-saving issues across PRO sub-tabs.<\/li>\n
- Improved WordPress coding standards compliance.<\/li>\n<\/ul>\n\n
3.0.6<\/h4>\n\n\n- Added automatic script blocker and cookie cleaner.<\/li>\n
- Added optional PRO licensing, analytics, and export tools.<\/li>\n
- Removed non-functional placeholder integrations from the admin UI.<\/li>\n<\/ul>\n\n
3.0.5<\/h4>\n\n