=== DT-PM Consent Plus ===
Contributors: dtpmgmbh
Requires at least: 6.2
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.2
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Adds to DT-PM Consent. Requires the free version; without it this plugin does nothing.

== Description ==

DT-PM Consent Plus is the paid edition of DT-PM Consent. It never replaces the free
version - it adds to it, through the documented extension points the free
version offers to everyone.

This file is read by the update service (updates.dt-pm.eu). Everything in it
is escaped and shown as plain text, so HTML would appear verbatim.

= What it needs =

* DT-PM Consent, installed and active. Without it, DT-PM Consent Plus does nothing
  and says so.

= What it sends =

Only the licence key, the domain of this site and the product identifier - to
license.dt-pm.eu, and only from the admin area or a scheduled run. Never from
a visitor's page view, and never anything about a visitor.

= What starts the free period =

A button that a human presses, never the plugin on its own. The free period
runs for three months, once per domain, and cannot be started again for that
domain - the sentence next to the button says so.

== Changelog ==

= 1.0.2 =
Requires DT-PM Consent >= 1.1.3.

**The German wording now follows WordPress's own glossary.** On
translate.wordpress.org, *button* is "Button" and *site* is "Website" - this
edition said "Schaltfläche", "Knopf" and "Seite". 143 entries changed: 15
button terms, and 61 places where the English says "site" and the German said
"Seite". One name changed visibly with it: what was "Betreute Seiten" is now
"Betreute Websites", and so are the labels and the column heading that belong
to it.

* **Punctuation, in 103 places.** Between two clauses German takes an en dash
  - not a hyphen, not an em dash - and a non-breaking space before it. That
  same space goes into "z. B." and "d. h." so they cannot break across lines.
  Nothing inside a code example was touched.
* **The free edition's German, which this edition carries** for sites that did
  not get the free edition from the plugin directory, had the same treatment:
  101 entries, 9 terms, 8 of them "Seite" where the English says "site", and
  97 places of punctuation.
* **The same German text is now what we submit to translate.wordpress.org.**
  Until now the submitted files carried these corrections and the shipped
  catalogues did not. Two wordings for one plugin, and nothing to keep them
  together - that is over.

Nothing in English changed. Nothing you have configured is touched, nothing
behaves differently, and no visitor is asked again: the fingerprint that
decides that is built from your stored texts, not from these defaults.

= 1.0.1 =
Requires DT-PM Consent >= 1.1.3.

**The German wording of the free edition, brought up to date.** This edition
carries the free edition's German catalogues for sites that did not get it
from the WordPress plugin directory. Ten notices there were rewritten in
1.1.5; until now they stayed English on such a site. They are German again.

* The two calls into WordPress's own list of tools now say in the file itself
  that they need WordPress 6.9, instead of leaving it to the hook they hang
  on. Nothing changes for you - on an older WordPress that list does not exist
  and this edition never reached those calls. What changes is that a checker
  reading the file can see it.

Nothing you have configured is touched, and nothing behaves differently.

= 1.0.0 =
Requires DT-PM Consent >= 1.1.3.

**Your own AI assistant can now reach these tools a second way.** Where your
site runs WordPress 6.9 or newer, the 21 tools this edition already offered
over its bridge are also entered in the list of tools WordPress itself keeps.
Same tools, same answers, a second entrance - and a switch of its own on the
bridge page, next to the bridge's. It starts out open; close it and software
asking WordPress for these tools is told they do not exist.

* **The entrance is a WordPress login, not a key.** A tool is only run for a
  signed-in user who may manage this site's options - the same threshold as
  every settings page here. The bridge's own key is not used for it and is not
  needed: you do not have to switch the bridge on to use this.
* **Reading the list is a lower threshold than using it, and that is
  WordPress's rule, not ours.** While this way is open, any signed-in user -
  a customer with an account, for instance - can ask WordPress what tools
  exist and read their names, their descriptions and which arguments they
  take. Running one of them is refused unless that user may manage the site.
  Nothing of your configuration, your services or your consent records is
  readable that way. If even the list is more than you want visible, close
  this way and use the bridge, whose key answers nobody without it.
* **Nothing is taken away, and the two ways are independent.** The bridge
  works exactly as before, with its key, its lockout after failed attempts and
  its switch. Closing one way leaves the other as it was. For a site on an
  older WordPress, or one whose owner prefers a key over an account, the bridge
  stays the only way in - and the only one that needs no WordPress user at
  all.
* **Where the core has no Abilities, nothing happens.** No notice, and no
  prompt to install anything.
* **Your German stays German, wherever you got the plugin from.** The free
  edition no longer ships its own translation catalogues - WordPress.org
  generates and delivers them, which is the right way round for a plugin in
  the directory. It leaves out everyone who installed the free edition from
  our own download area, so this edition carries those catalogues and hands
  them to WordPress. Where a language pack from WordPress.org exists, it wins;
  ours is the fallback. That now includes the block editor's own panel for the
  cookie policy block: its texts come from a separate file which WordPress
  looks for elsewhere, and until this version it was never found.
* **Every writing tool now has to say what it changed.** Since 0.10.4 each
  write answer named whether a record was archived and whether consent given
  so far became invalid. That was a promise; it is now a checked one - an
  answer without those two fields is rejected.

**Why this version is 1.0.0 and not 0.10.7.** This edition has been sold since
October and had a number that read like something unfinished. The number moves
here, with the release in which its programmable interface is written down for
the first time, rather than in a release that changes nothing else. Nothing
about licences, product codes or stored settings changes with it.

= 0.10.6 =
Requires DT-PM Consent >= 1.1.3.

* **Follows the free plugin's new folder.** The free edition is now installed
  as `dt-pm-consent`, the name the WordPress.org directory assigned it, and
  this edition names that folder in its `Requires Plugins` header. Install the
  free 1.1.3 first: until the free plugin sits in a folder of that name,
  WordPress will not activate this one. Nothing else changes.

= 0.10.5 =
Requires DT-PM Consent >= 1.1.0.

* **The "Start free period now" button is gone once there is nothing to
  start.** It used to stand there unconditionally: you pressed it, the start
  was confirmed at the top of the page - and the button stayed exactly where
  it was, offering a second start that the sentence right next to it rules
  out. Where the free period has been started for this domain, or where a
  licence is running, the page now says so in one line instead. Where nothing
  cannot be told from the stored answer - the service has not answered, or its
  answer names a contract rather than the free period - the button stays, and
  the service itself declines a second start. A screen that locks you out of
  ignorance is worse than a service that says no.
* **The changelog entry for 0.8.0 was missing, and the reason was not what it
  looked like.** Its text was not lost: it had been folded into the 0.9.0
  entry, so 0.9.0 described two versions and 0.8.0 none. Each number now
  describes itself. Both packages stay untouched.

= 0.10.4 =
Requires DT-PM Consent >= 1.1.0.

* **Every writing tool now says what it did to your records.** The 0.10.3 note
  above said this was already the case for all of them. Counted: three of the
  twelve always said it, a fourth only on the calls where it saved something.
  The rest simply left both fields out, so an agent that changed your design
  or your languages could not tell from the answer whether anything had been
  archived or any consent had become invalid - it had to guess, and a guess is
  what caused this. Both fields are now in all twelve answers, measured before
  and after the change rather than assumed. Reading tools do not carry them:
  nothing changes, and two fields that always say "no" would be noise.
* **The hub rollout reports what happened at the sites, not at the hub.** It
  is the one tool that writes to other sites, so nothing changes on the hub
  itself. Measured there, the answer would have said "nothing was archived,
  no consent became invalid" while the per-site list said the opposite line
  by line. Both fields now mean "at one or more of the managed sites", and the
  list beside them still names every site. A dry run writes nothing, so both
  stay "no".

= 0.10.3 =
Requires DT-PM Consent >= 1.1.0.

* **The bridge screen is now only the list.** The one line that still stood
  above the writing tools is gone as well. What a change does to your records
  and to the consents you already have is in every writing tool's answer, as
  it always was - you read it after the change instead of before it.

= 0.10.2 =
Requires DT-PM Consent >= 1.1.0.

* **The bridge screen says what you can steer with it.** It used to open with
  five paragraphs about what the bridge is and what a change means. In their
  place is the list of what it can read and what it can change, with one
  sentence each - taken from the same registration the endpoint builds its
  tool list from, so it cannot go stale. That a change takes effect at once,
  and what it does to your records and consents, is still there: one line,
  above the tools that change something.
* **The hub section is gone where the hub role is not available.** On the
  "Advanced" tab it was a heading and a notice for a feature this installation
  does not have and cannot order there. On its own menu page - with an older
  free version alongside - it still explains why the role is missing.

= 0.10.1 =
Requires DT-PM Consent >= 1.1.0.

**Two findings from looking at the new tabs.**

* **One example banner on the "Banner" tab, not two.** There were two
  pictures of the same banner, with the same text and the same renderer - and
  only the lower one showed your colours. The one that stays is the better
  one: it follows the text fields as you leave them. It now shows your
  colours, font and logo as well, which it never did before.
* **Each screen of this plugin now sits in its own box**, so you can see
  where one function ends and the next begins. On "Advanced" four unrelated
  things sit under each other - licence, Consent Mode, hub and bridge - and
  until now a button there belonged to no visible section. Same box as the
  cards on "Overview".

= 0.10.0 =
Requires DT-PM Consent >= 1.1.0.

**No more menu items of its own.** The eight screens of this plugin used to
sit next to the free version's menu entry; now each one sits on the tab it
belongs to. Appearance and the per-language texts are under "Banner", the
service database under "Services", monitoring under "Scan". Licence, Consent
Mode, hub and bridge share a new "Advanced" tab.

* **Appearance and Banner were the same subject in two places.** How your
  banner looks and what it says are now on one screen.
* **On an older free version nothing disappears.** Below 1.1.0 the extension
  points do not exist yet, and this plugin falls back to its own menu items -
  the same eight screens, in the old place.
* Messages now stay with the section they belong to instead of jumping to the
  top of the page.
* Less text on every screen.

**Fixed, from a review of a live installation:**

* **The bridge key can be copied complete.** The header value, including the
  word "Bearer" and the space, now has its own field and a copy button - so
  does the key on its own, for clients that add "Bearer" themselves. Putting
  the two together by hand was the step that went wrong.
* **"Domains: 0 of 5" is gone when the licence service does not say.** A
  missing figure used to be printed as a zero, which looks like a count.
* German: "Freizeitraum" is now "Kostenlose Testphase". The old word means
  leisure time.
* Internal shorthand removed from screens.
* **The licence page says whether this website holds a slot**, not only how
  many of your domains are in use. The service has reported this since
  September; the plugin was throwing the answer away. It is shown, not acted
  on: a released slot does not switch anything off yet.
* **The link in the monitoring e-mail works again.** Under "What to do: open
  DT-PM Consent" the mail printed the address of the old menu item, which no
  longer exists - the page it opened said "you are not allowed to access this
  page". The same was true of "Check the licence" on the bridge screen.

= 0.9.0 =
**Your service database stays up to date, without waiting for a plugin
update.** Once a day this plugin asks our service for new service identifiers
and adds them to the ones it ships with.

**One rule carries this feature, and it is worth reading once:** the fetched
part only ever **adds**. It never changes and never removes an entry that
ships with the plugin. An entry whose identifier is already known is skipped.

* **So your own configuration cannot be rewritten from outside**, and a
  service can never end up recognised less well than before. Measured against
  a deliberately bad answer: our service claimed a different category for
  Google Analytics, and the visitor still got the one we ship.
* **Nothing enters your configuration by itself.** New entries make the
  detection and the suggestions better; a suggestion becomes a service of
  yours only when you take it over.
* **A licence running out does not take recognition away.** After it expires
  no new catalogue is fetched, and the one you have stays and keeps working.
* **Fetched entries are not translated.** The translations of the entries we
  ship sit in our own language files; for an entry we never shipped there is
  no line there. The page says so.
* The page keeps „last checked" and „last fetched something new" apart, and
  „entries fetched" apart from „new here" — a check that finds nothing is a
  successful check.
* Every failure leaves what you have standing. There is no path on which an
  unreachable service, a broken answer or an empty one results in an empty
  catalogue.

**And your AI assistant can now start a check.** Reading the last report was
already possible; now it can run one, see which third parties have no entry,
and enter them. **This one needs the free DT-PM Consent 1.0.17 or newer** —
with an older one the tool says so, naming both version numbers. Everything
else in this version works with 1.0.16.

= 0.8.0 =
Requires DT-PM Consent >= 1.0.16.

**You can now write your banner texts once per language.** A French visitor
reads your French sentence, an Italian visitor your Italian one - and both
read your own words, not a machine translation.

**Needs the free DT-PM Consent 1.0.16 or newer.** The seam these texts hang on
sits in the free plugin. With an older free version this page keeps your sets
saved and tells you which version is missing.

* **A language you have not maintained is not left empty.** It falls back to
  our translated default for that language - never to the text of your
  reference language, because a German sentence in an Italian banner is a
  sentence the visitor does not understand but is asked to agree to.
* **Next to every field the page says where that field comes from**: your own
  text, the translated default, or inherited from your reference language.
* **The privacy and imprint links are inherited, not translated.** Most sites
  have exactly one privacy statement, and a banner without that link has lost
  a mandatory item. Supply a different address for a language and it wins.
* **Your reference language is not maintained here.** Its texts stay on the
  free plugin's own settings page, where they belong: the consent fingerprint
  hangs on them. Two places for the same text means one of them silently
  invalidates consent and the other does not.
* **The two level-one buttons cannot be changed, in any language.** Same rule
  as always, and now it is a rule about wording too.

**Switching languages does not ask your visitors again.** Correct a
translation and nobody is asked; change the text of your reference language
and everyone is, exactly as before.

**Off without a valid licence, and nothing is lost.** Your banner then shows
what the free plugin shows on its own, and the sets you maintained stay saved.

= 0.7.0 =
**You can now let Google load before your visitor decides - if you want to,
and only then.** Google calls this "advanced consent mode". It is off, it is
never preselected, and switching it on takes two deliberate clicks.

**Needs the free DT-PM Consent 1.0.15 or newer for this one switch.** Without
it the switch stays disabled, and the page says so with both version numbers -
a switch that said "on" and did nothing would be worse than none, because you
would hold Google for loaded and your numbers for complete.

* **What it does:** your Google tags load immediately, before anyone has
  agreed, and send measurements without cookies. That is still a connection to
  Google, with your visitor's IP address. In exchange, Google models your
  conversions more precisely.
* **You carry the liability for that, and it may be a breach of data
  protection law.** That sentence is on the switch, not in a manual, and the
  second click is you confirming you read it. **The legal question is not
  settled:** among the best-known alternatives, one makes this the factory
  setting and another tells its customers it may be unlawful. We leave the
  decision to you and we do not preselect it.
* **Only your Google services are let through, and they are named on the
  page.** Every other third party stays blocked until your visitor agrees -
  switching this on is not a general amnesty.
* **A tag and the snippet beside it are freed together.** Freeing only the tag
  would mean a connection to Google and still no measurement.
* **Switching it off needs no confirmation**, and your licence running out
  switches it off by itself. The safe direction never has a hurdle.
* Google is told to wait briefly for the real consent signal, so it does not
  report a refusal your visitor never gave.

Nothing about your banner, your blocking or your stored consents changes. The
consent your visitors already gave stays valid: the service list is the same,
so the configuration fingerprint is the same.

= 0.6.0 =
**Google Consent Mode v2.** Your Google tags stay blocked until a visitor
agrees - that does not change. What changes is that Google is now told about
the decision, instead of assuming it may do everything.

**Needs the free DT-PM Consent 1.0.14 or newer for this one feature.** With an
older free version the setting is saved and nothing is sent; the page says so,
with both version numbers. Everything else in this plugin is unaffected and
still needs only 1.0.11.

* **Nothing goes to Google before your visitor decides.** No tag is loaded
  early, and no "cookieless ping" is sent. Google learns the decision at the
  moment your Google tags are released - not before.
* **All seven of Google's consent signals are set explicitly.** A signal that
  is not set counts as *granted* at Google, so leaving one out would quietly
  grant it. Advertising signals follow your Marketing category, analytics
  follows Statistics, and the two that need no consent - security and basic
  functionality - are always granted.
* **The mapping cannot be changed**, not on the page and not through the
  bridge. Whoever can change it can tell Google about a consent that was never
  given.
* **Ad click identifiers are redacted** while advertising consent is missing.
  Passing them on through URL parameters is not offered at all - that would be
  tracking without a cookie.
* **There is deliberately no "advanced" mode.** Advanced means loading Google
  before your visitor has agreed, which is what this plugin exists to prevent.
  Three of the four best-known alternatives also default to the safe mode; we
  go one step further for now and leave the other one out until the legal
  question is settled.
* **And the page tells you when your own setting undoes all of it:** if you
  have set a Google service to load without consent, it loads before anyone
  agrees and sends data to Google, including your visitor's IP. You carry the
  liability for that, and it may be a breach of data protection law. Consent
  Mode does not stop it - it only reports the decision.

**New in the bridge** for your own AI assistant: it can read whether Consent
Mode is on, which signal follows which category, and whether a Google service
is set to load without consent. It can switch Consent Mode on and off. It
cannot touch the mapping.

= 0.5.0 =
**Your website is watched now, and you do not have to do anything for it.**
Needs the free DT-PM Consent; no new requirement on its version. Monitoring is
off until you switch it on.

* **Automatic monitoring with a message.** When a third-party service appears
  on your pages that is not in your service list - and is therefore not
  blocked - you get an email. Whenever a plugin or theme changes here it is
  looked at straight away, and on a schedule it is looked at again, so a
  change that comes from outside is caught too.
* **You do not click through your pages for it.** The pages it looks at are
  the ones you walked through once when you set the plugin up; monitoring
  fetches exactly those by itself, from then on. If you never did that run, it
  says so and looks only at the pages WordPress knows by itself - better than
  nothing, and worse than the real thing, and the page tells you which one you
  are getting.
* **The fetch is a visitor without consent**, deliberately: what you want to
  see is what loads BEFORE anyone has agreed to anything. No consent cookie
  goes along, and nothing is done to bypass your page cache - what the cache
  serves is what a visitor gets.
* **Only things that actually load are reported.** A plain link to another
  site loads nothing, so it is not a finding. Scripts, stylesheets, fonts,
  images, iframes and embedded media are.
* **A service you have already set up is not a finding.** It is blocked until
  a visitor agrees, and that is the state you wanted.
* **No "all clear" emails.** You hear from monitoring when there is something
  to say, and the rest stands on its own page: when it last looked, what the
  reason was, when it last wrote to you, and whether the mail got out. If
  sending mail does not work on your installation, the page says so after the
  third attempt - and the findings are kept until it works.
* **"Weekly" or "daily" is your choice**, on the same page, whatever your
  plan. The extra look is for everything that changes without anything
  happening on your site.
* **Nothing is changed for you.** Monitoring reads; it never edits your
  service list. Adopting a service, or marking it as irrelevant, stays your
  decision in the check - because your consents are built from that list.
* Nothing from monitoring leaves your installation in our direction.

= 0.4.1 =
* **This edition is now called DT-PM Consent Plus**, and the free one DT-PM
  Consent. The addition "for WordPress" is gone from both: the plugin
  directory does not allow that term in a plugin name at all, and the free
  edition is heading there.
* Nothing else changed. Not the folder, not the text domain, not your licence
  key, not a single setting. The update path is unaffected - your licence is
  tied to your domain and the product, never to the name.

= 0.4.0 =
**Needs the free DT-PM Consent 1.0.11 or newer for the accent colour and the
font.** With an older free version those two are saved and shown in the
preview, but the banner on your pages keeps the colour and font it takes from
your theme; the page tells you so. The logo works with any version.

* The appearance of the banner can be set: accent colour, font and a logo.
  Before this, the banner took its colour and font from your theme and there
  was no way to say otherwise.
* **The lettering on the buttons always reaches a contrast of 4.5:1.** If the
  colour you pick cannot carry readable lettering, the banner uses the nearest
  shade that can - your entry is kept, and the page tells you which colour
  goes out and why. This is what the accessibility rules require, and it is
  checked where the colour is used, not only in the form.
* **There is deliberately no way to colour "Accept all" differently from
  "Reject all".** Two buttons that ask the same question must look the same; a
  bright green one next to a grey one is a nudge, and a nudged consent is not
  a consent. The same reason the wording of those two cannot be changed
  either.
* The font can only be one your theme already loads. The banner never fetches
  a font from another server - a consent plugin that did would be loading a
  third party before anyone agreed to it.
* The logo comes from your own media library and is decorative: screen readers
  skip it, because your brand is already on the page behind the banner. An
  image delivered by a CDN is refused, with the reason named - the banner
  would otherwise load from another server before anyone has agreed to
  anything.
* A preview that does not save. It renders the real banner with the values in
  the form, through the same output path as your pages.
* Nothing you set here is in the record archive and nothing invalidates a
  consent you already have. Colours do not change what someone agreed to.
* **The licence page no longer says your licence is valid when it is not.**
  There is a new state for the case that this site has not asked the licence
  service for a while - it says what the stored answer was, how old it is, and
  that the licence may well be valid. Next to it a button that asks right
  away. The button costs nothing: it does not use up your free period.
* The grace-period message now distinguishes "the service did not answer"
  from "this site did not ask" - the second is usually WP-Cron not running on
  your installation, and the message says so instead of blaming our service.
* The bridge page says plainly that a change through your assistant takes
  effect at once, on the live banner, without being put to you for
  confirmation first.

= 0.3.0 =
* German. Until now this edition spoke English in every admin area, in every
  language setting - it had a text domain but no translation at all, and
  nothing measured that. A complete German translation now ships with it,
  including for "Deutsch (Sie)" and for Austria and Switzerland.
* A template for further languages ships with it as well
  (languages/dt-consent-plus.pot). Anyone who wants this edition in their own
  language does not have to ask us for it. This edition is not on
  WordPress.org, so the package is the only way that template reaches you.
* A bridge for your own AI assistant. It lets your own Claude - or another MCP
  client - read your configuration and change services, categories and banner
  texts, through the same checks as the forms on these pages. It is off until
  you switch it on, it needs a key you create here, and the key is shown once.
  Nothing about it goes to us.
* The bridge page explains itself. Nine sections, collapsed: where the setting
  is in your assistant, what the connection consists of, what the key allows
  (it is not tied to a WordPress user - read that before you hand it on), what
  a change does to consents you already have, and what to do when it does not
  work.
* Changes made through the bridge are treated like any other change: services
  and categories appear in the record archive and invalidate the consents
  given so far; banner texts take effect at once and do neither. Every answer
  says which of the two happened.

= 0.2.4 =
* A new name: the plugin is now called DT-PM Consent Plus for WordPress. Only
  what you read changes - the folder, the text domain, the licence key and the
  domain it is bound to all stay as they are. Nothing to re-enter.
* The free version it needs is now called DT-PM Consent for WordPress;
  the notice shown when it is missing says so.
* Tested against WordPress 7.1, the same version the free edition names.

= 0.2.3 =
* Rides along in a release that also carries the free version's ZIP. The free
  version has no Update URI in its header, and the update service must skip it
  silently - that is what this release measures.

= 0.2.2 =
* The version 0.2.1 is meant to find. Two releases are needed to show that the
  update path carries: one only shows that a package can be downloaded.

= 0.2.1 =
* The update path itself. The Update URI header alone does nothing: WordPress
  never calls that address, it dispatches to a filter - and without a plugin
  on that filter the answer is "no update", silently. 0.2.0 shipped without
  it and would never have found anything.

= 0.2.0 =
* Licence connection: key field, status with three states, seven cases with a
  sentence and an action each.
* The free period is started by a button, never automatically.
* Daily check through the effect-free endpoint; after a disruption, no retry
  for an hour.

= 0.1.0 =
* First version. Adds a CSS class to the banner through the documented filter.
