Download the PHP package quebecstudio-mods/consent-kit-register without Composer
On this page you can find all versions of the php package quebecstudio-mods/consent-kit-register. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download quebecstudio-mods/consent-kit-register
More information about quebecstudio-mods/consent-kit-register
Files in quebecstudio-mods/consent-kit-register
Package consent-kit-register
Short Description Consent register shared by the Cookie Consent Kit CMS integrations: schema, storage and queries.
License proprietary
Informations about the package consent-kit-register
Cookie Consent Kit register — quebecstudio-mods/consent-kit-register
The consent register shared by the Cookie Consent Kit integrations that keep one: its schema, its storage and its queries.
| Integration | Package |
|---|---|
| Statamic 6 | quebecstudio-mods/statamic-consent-kit 6.x |
Requires PHP 8.2, illuminate/database, illuminate/support and
quebecstudio-mods/consent-kit-core. It holds no panel and no HTTP layer: an
integration decides what to record and how to show it, this keeps it.
quebecstudio-mods/laravel-consent-kit does not use it — it renders the
banner and leaves the register to the application. craftcms-consent-kit keeps
its own, in Craft CMS table and column conventions.
Contents
| Path | What it is |
|---|---|
src/Connection.php |
Which database the register is kept in |
src/Register.php |
Storage and queries: store, page, find, purge |
database/migrations/ |
The two tables, consent_decisions and consent_presentations |
Schema
consent_decisions holds one row per reported answer: the site, the language,
the user when the site records one, what was pressed, where from, the
categories granted and the resulting outcome.
consent_presentations holds one row per distinct banner screen, keyed by the
fingerprint Presentation computes in the core. Decisions point at it, so a
screen shown a million times is stored once, and a stored decision can be
replayed against the exact wording it answered.
Which database
Connection::name() resolves, in order:
cookie-consent.register.connection, when the site names one;- the site's own default connection, when it opens;
- a SQLite file in
storage/cookie-consent/register.sqlite, declared and migrated byConnection::migrate().
Using it
Reading a page, either from plain filters or from a query the integration has already filtered:
Retention is the core's: Registry::cutoff() gives the date beyond which a
record has outlived what it attests, and $register->purge($cutoff) deletes
those rows, then the screens no decision points at any more.
Licence
Proprietary. See LICENSE.md.
All versions of consent-kit-register with dependencies
illuminate/database Version ^11.0 || ^12.0 || ^13.0
illuminate/support Version ^11.0 || ^12.0 || ^13.0
quebecstudio-mods/consent-kit-core Version ^1.2