Skip to content

Releases: devartgr/joomla-devart-consent

DevArt Consent 1.0.1 - First public release

Choose a tag to compare

@devartgr devartgr released this 10 Aug 19:09
d54bd78

DevArt Consent 1.0.1

First recommended stable release for Joomla 6 production sites. Cache-first consent management with server-side blocking, Google Consent Mode v2, and full-page cache / Cloudflare compatibility.

Requirements

  • Joomla 6.0.0 or later
  • PHP 8.3.0 or later

Install

  1. Download pkg_devartconsent_v1.0.1.zip
  2. Install via System → Install → Extensions
  3. Confirm plg_system_devartconsent is enabled
  4. Open Components → DevArt Consent → Settings

Package

  • com_devartconsent (component)
  • plg_system_devartconsent (system plugin)

SHA-256: f81f931e3d456b15de6fd16307ec27beed6e8bcc4d057c4d2ba339b19e155890

What's new in 1.0.1

  • Dynamic embed observer inspects direct script and iframe nodes synchronously (smaller pre-consent race window)
  • Server-side blocking skips <template> and <svg> segments (HtmlBlockingGuard)
  • CSP nonce verification checklist (qa/csp-verification.md)
  • Observer scheduling regression tests
  • PHP cleanups: PackageVersionHelper, lighter registry availability check, removed alpha Google *_mode parameter reads
  • Frontend engine 2.0.1

Included features

  • Cache-first banner: accept, reject, custom preferences, revoke
  • Server-side blocking: Google services, marketing pixels, external embeds, custom rules
  • Scoped dynamic embed observer for JavaScript-created nodes
  • Google Consent Mode v2
  • Automatic Joomla cache clear on policy version bump
  • Optional consent registry with CSV export
  • Built-in English and Greek frontend messages
  • DevArt appearance themes

Known limitations

Dynamic embed blocking is best-effort client-side protection. A browser may start a network request before the observer rewrites a dynamically inserted src. Use window.DevArtConsent.whenGranted() for custom widgets. See docs/limitations.md.

CDN / reverse-proxy cache purge remains manual after a policy version increase.

Upgrade

  • From 1.0.0 or any 1.0.0-beta.* / 1.0.0-rc.1 package: install over the existing package (upgrade).

Links

  • Documentation: docs/stable-release.md
  • QA checklists: qa/stable-signoff.md, qa/csp-verification.md