ConsentPilot

گزارش تغییرات

0.1.9

• Compliance: “Accept all” and “Decline all” now share the same
  visual weight as a matched pair of primary-coloured buttons.
  The previous default made “Accept all” more prominent than
  “Decline all”, which EDPB Guidelines 03/2022 on deceptive
  design patterns and the Norwegian Data Protection Authority
  identify as a pattern that can render consent invalid. The
  “Customize” button remains a lighter outline button, which is
  permitted since it is not a consent choice itself but a
  gateway to per-category selection. Existing custom-CSS
  overrides in the Pro version are not affected.
• Added a small stable public JavaScript API on window.ConsentPilot
  so other plugins and theme code can integrate without guessing
  at CSS class names. Methods:
  window.ConsentPilot.open() – open the consent panel
  window.ConsentPilot.getConsent() – read stored consent
  window.ConsentPilot.hasConsent(cat) – check a category
  The internal method name openSettings() introduced in 0.1.7
  is kept as an alias for backwards compatibility.

0.1.8

• Improved: raw tracking scripts embedded in themes or in
  “header/footer” plugin fields are now also caught. Previously
  ConsentPilot only blocked scripts that went through the
  WordPress script queue (wp_enqueue_script). A small guard is
  now written into the page head at priority 1 that watches the
  document for hardcoded tags from Site Kit,
  WPCode, Insert Headers and Footers, GTM plugins, and theme
  header code, and neutralizes matched patterns before the
  browser fetches them.
• Scripts placed literally in header.php before the wp_head()
  call still cannot be blocked – the plugin has no code running
  at that point. This is a rare setup; move the script into a
  wp_head hook or into WordPress’s enqueue system.

0.1.7

• Added a new setting to hide the floating “Cookies” reopen
  button. Site owners who prefer a discreet footer link over a
  permanently visible corner button can now switch it off under
  Settings > Appearance.
• Added a [consentpilot_link] shortcode that renders an “Change
  cookie settings” link anywhere in a page, post, or widget. The
  link opens the consent settings on click. Optional text and
  class attributes: [consentpilot_link text=”Cookies”].
• Added a data-consentpilot-open attribute so a theme developer
  can hook a menu item or footer link to the same open action
  without a shortcode.
• Added a small public JS API: window.ConsentPilot.openSettings()
  for cases where JavaScript is the right integration point.
• Cleaned up two leftover “(Pro)” comments that suggested Consent
  Mode v2 and geo-targeting were paywalled – both have been fully
  free since 0.1.1.

0.1.6

• Fixed: the floating “Cookies” reopen button now uses the primary
  colour you have configured under Settings → Appearance, instead
  of falling back to the default blue on returning visitors.
  Previously the colour was only applied when the full banner
  rendered, so the reopen button on returning sessions never
  picked it up.

0.1.5

• Fixed: when a visitor reopens the consent banner after having
  saved their choices, the checkboxes now reflect what was
  previously saved (e.g. all four categories checked after
  “Accept all”) instead of resetting to only “Necessary”. Their
  actual saved consent was never lost — only the UI display was
  incorrect — but the mismatch was confusing.

0.1.4

• The floating “reopen consent” button now uses an inline SVG
  cookie icon and a small “Cookies” label, so visitors can see
  what the button does at a glance. Previously it relied on a
  cookie emoji that did not render reliably on all platforms.
• The reopen button has a tooltip and a soft shadow for better
  affordance. On screens narrower than 480px the label collapses
  and only the icon is shown.

0.1.3

• Added an “Upgrade to Pro” box to the plugin dashboard so users
  can discover the optional Pro tier with the privacy-policy
  generator, cookie scanner, audit-report PDF and other features.
  The box is hidden automatically when Pro is licensed.
• No changes to core functionality.

0.1.2

• Added discreet “Powered by ConsentPilot” link in the banner, with a
  filter so Pro users can hide it (consentpilot_frontend_config).
• Added support for an optional custom logo above the banner text.
• No breaking changes, existing installations keep all behavior.

0.1.1

• Removed the output-buffer-based script blocker. All blocking now uses
  WordPress filters (script_loader_tag, wp_inline_script_attributes,
  the_content), which are predictable and do not interact with the global
  output-buffer stack.
• Removed all license gates from Google Consent Mode v2 and geo-targeting
  settings. Both features are fully functional in this release.

0.1.0

• Initial release.
• Consent banner with three layouts and per-category choice.
• Blocking of tracking scripts and iframes before consent.
• Consent log with hashed IP and CSV export.
• Custom blocking patterns and policy versioning.