TypoScript constants 

| Data type: data-type-path | Default: EXT:cookieman/Resources | Example: EXT:mysitepackage/Resources |

Path to directory that holds the themes. Default enables the shipped demo themes. See Custom themes how to create a new theme.

| Data type: data-type-string | Default: bootstrap4-modal | Example: my-theme |

Name of the theme. It is used to extend the resourcesBasePath to create the full path to templates and assets.

The shipped default themes are these: Themes directory on Github

You can check them out on our demo page.

Of course you can use your own custom theme (see Custom themes).

| Data type: data-type-page-id | Example: 123 |

page UID of data privacy statement page - the Cookieman modal will not be automatically opened on this page (see When is the popup shown to users?).

| Data type: data-type-string | Example: c456 |

You can set an (optional) anchor (TYPO3-lingua "section") on the data privacy statement page.

| Data type: data-type-page-id | Example: 123 |

page UID of imprint page - the cookieman modal will not be automatically opened on this page (see When is the popup shown to users?).

| Data type: data-type-string | Example: c456 |

You can set an (optional) anchor (TYPO3-lingua "section") on the imprint page.

| Data type: data-type-string | Default: 365 | Example: 90 |

Number of days after which the consent cookie expires.

| Data type: data-type-string | Default: the domain of the TYPO3 site | Example: .example.com |

Domain of the consent cookie, without the protocol. Start it with a dot to share the cookie between subdomains (see Configuration of the cookie used by the extension itself).

| Data type: data-type-string | Default: Strict | Example: Lax |

SameSite attribute of the consent cookie. Use Strict, Lax or None.

Before cookieman 5.0.0 the default was Lax.

| Data type: data-type-string | Default: empty (= on) | Example: 0 |

Makes the consent cookie secure. Cookieman sets the attribute only when the page is served via https, so it is safe to leave this on.

Set it to 0 only if you have http/https subdomains that must be covered by the cookie (see Configuration of the cookie used by the extension itself).

| Data type: data-type-string | Default: 1 | Example: 2 |

Version of your cookie configuration. Cookieman writes it into the consent cookie. You can use any value, for example a date or the number of your release.

Change it every time you change your cookie configuration. Cookieman then shows the consent popup again to all users whose cookie holds a different version. Until such a user saves again, the old consent does not count and cookieman injects no tracking objects (see Show the consent popup again after a configuration change).

Consent that cookieman before 5.0.0 saved holds no version. Such a cookie gets the current version without a change for the user ("silent upgrade"). Thus the upgrade to 5.0.0 does not ask anybody again.

| Data type: boolean | Default: 1 |

Cookieman comes with both minified and regular stylesheets and JavaScripts for the demo themes.

It set to 1, the minified versions of the .css and .js files are used. You can set it to 0 for debugging purposes.