AriConsent

Changelog

0.4.1

• Fixed: Norwegian, Swedish, Danish and Finnish sites showed the banner and cookie policy in English. AriConsent now ships its translations and uses them when WordPress.org has no language pack for your language yet; a language pack from translate.wordpress.org still takes priority.

0.4.0

• Added: optional switches for single services in the cookie settings, so a visitor can for example allow statistics but keep Hotjar off. Off by default; switch it on under Banner. Turned-off services stay blocked, their cookies are deleted, Google and Microsoft consent signals follow the choice, and the consent log records it (“Yes, except Hotjar”). Plugins that ask the WP Consent API still see the category as a whole.
• Added: consent signals for Microsoft Clarity (Consent API v2) and Microsoft Advertising (UET consent mode), which Microsoft requires for visitors in the EEA, the UK and Switzerland. Microsoft Advertising’s UET tag is now recognised and blocked until marketing consent. Switch the signals off under Google & Microsoft if you don’t want them.
• Changed: the scan now checks your homepage plus up to nine other pages (newest posts and pages, the privacy page, the shop) and runs by itself once a week, so trackers added later show up in the health check. It still only loads pages from your own server.
• Added: a health score (0–100) above the health check.
• Added: copy settings to another site with “Download settings” and “Import settings” on the General tab. Each site keeps its own privacy page and consent revision.
• Added: WP-CLI commands: wp ariconsent status, scan, reconsent, export and import.
• Added: any link to #cookie-settings, such as a custom link in a menu, opens the cookie settings.
• Added: saving AriConsent settings or asking everyone again now clears the page cache of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Optimizer, Cache Enabler, Breeze, Hummingbird and Nginx Helper, so visitors see the change straight away.
• Added: WooCommerce Order Attribution (the sbjs_ cookies) now waits for marketing consent. With the WP Consent API plugin installed, WooCommerce already waits by itself, and AriConsent leaves it to WooCommerce.
• Added: resource hints (preconnect, dns-prefetch, preload) to trackers that wait for consent are switched off, so the browser no longer contacts them before the visitor chooses.
• Added: Global Privacy Control. When a visitor’s browser asks sites not to share their data, “Accept all” leaves marketing off and the banner says so; the visitor can still allow marketing under “Choose cookies”. On by default; switch it off under Banner.
• Added: when a visitor refuses or withdraws a category, cookies its trackers already left (such as _ga or _fbp) are deleted from the browser. Your own and WordPress cookies are never touched.
• Fixed: the consent log now stores a choice in full when a visitor turns off many single services; before, such a choice could fail to be logged.
• Fixed: Safari visitors were asked again every week, because Safari keeps cookies written by JavaScript for 7 days only. The site now also sends the consent cookie itself, so the choice lasts as long as you set.

0.3.3

• Changed: translations now come from WordPress.org language packs and update automatically. Norwegian, Swedish, Danish and Finnish follow as soon as they are published on translate.wordpress.org.
• Changed: the invitation to run setup appears only on the Plugins screen and AriConsent’s own screens, no longer on the dashboard.
• Fixed: the Vimeo privacy policy link in the cookie declaration.
• Added: an “External services” section in the readme, explaining that AriConsent itself contacts no outside service.

0.3.2

• Changed: the plugin is now named “AriConsent” everywhere, ready for the WordPress.org directory. Nothing else changes.

0.3.1

• Fixed: after a visitor chooses in the banner or the cookie settings, keyboard focus moves to the cookie settings button instead of jumping to the top of the page.
• Fixed: loading a blocked video from its placeholder moves keyboard focus to the video.
• Changed: each video placeholder is announced by screen readers as a group named after the service (“Content from YouTube is blocked”), so its buttons make sense on their own.
• Changed: the placeholder’s “Load content” button is now “Load this time only”, and its two buttons sit side by side.
• Fixed: the consent log percentages always add up to 100.
• Added: a security policy. Report security bugs through the Patchstack Vulnerability Disclosure Program or to security@arihub.com.

0.3.0

• Added: proof snapshots. Each consent record links to an exact copy of the banner text, categories and services the visitor saw. View it from the consent log; the CSV export includes it.
• Added: health check on the AriConsent screen and in Tools → Site Health. It flags trackers that load before consent, a missing way to change the choice, an unpublished privacy policy or cookie declaration, low button contrast, and Google tags without Consent Mode.
• Added: Polylang and WPML support. Banner texts you type, and the cookie purposes and durations of services you add, can be translated per language in the translation plugin’s string list (group “AriConsent”). The privacy policy link goes to the page in the visitor’s language.
• Added: guided setup in three steps (what your site uses, how the banner looks with a live preview, privacy policy and Google). An invitation shows on the dashboard and the Plugins screen until you finish or skip it; setup stays available under AriConsent → Setup.
• Added: cookie policy page generator. One click creates a draft page in your site language that explains cookies and consent, with the live list of services and a button to change the choice. Review it and publish it; the list keeps itself up to date. Offered on the AriConsent screen, at the end of setup and from the health check.
• Added: [ariconsent_declaration intro="no"] shows the list without its opening sentence and button, for pages that already explain them.
• Changed: the button text on the banner now turns white or dark by itself, whichever is easier to read on your button colour. Light brand colours such as yellow are now readable without changes.
• Fixed: AriConsent’s early scripts now carry the attributes that Autoptimize, LiteSpeed Cache, WP Rocket, Cloudflare Rocket Loader and Jetpack Boost use to leave a script alone (tested with Autoptimize). Before, an optimiser that deferred them could let trackers run first.
• Fixed: trackers that an optimiser has rewritten into data: URLs (as Autoptimize does with inline scripts) are now recognised and blocked.
• Fixed: embedded videos and maps added through HTML strings (innerHTML and similar) are now stopped before the browser can request them, not just afterwards.
• Added: Elementor’s YouTube video widget shows a placeholder with “Allow and load” and “Load content” until the visitor agrees, instead of an empty box.
• Added: Jetpack Stats waits for statistics consent.
• Added: Google reCAPTCHA is listed in the cookie settings and declaration as necessary, so forms that use it keep working. To make it wait for consent instead, change its category under Services.
• Fixed: a cookie declaration with plugin-registered cookies but no known services no longer shows a PHP warning.

0.2.0

• Added: trackers and embeds that other scripts add after the page loads are now blocked until consent.
• Added: placeholders for videos and maps that are added to the page later.
• Added: ariconsent_update dataLayer event for Google Tag Manager.
• Added: automatic detection of popular plugins that add tracking services.
• Added: cookies registered through the WP Consent API are listed in the cookie declaration.
• Changed: the consent log accepts up to 100 records per IP address per 10 minutes, so offices and mobile networks that share an address are not cut off.
• Fixed: the CSV export stops cleanly if it cannot start.
• Fixed: no browser console error when the consent log cannot be reached.

0.1.0

• First release.