Frequently Asked Questions (FAQ)
See chapter Installation.
You need a Prive account. After configuring your consent banner in the Prive dashboard, copy the JavaScript snippet and paste it into the TYPO3 backend module at Web > Prive Consent.
Navigate to Web > Prive Consent in the TYPO3 backend. Select a page in the page tree -- the module automatically resolves the site root. From there you can edit the script, enable or disable the consent banner, and save.
See chapter Usage.
No. The consent script and cookie button are injected before the
closing </body> tag by a PSR-14 event listener that ships with the
extension. Nothing has to be included, configured or overridden.
The static TypoScript template [kroener.DIGITAL] Prive Consent is empty since version 4.2.0 and only kept so existing includes do not break.
No. The set oliverkroener/ok-prive-consent is empty -- it defines no
TypoScript, no dependencies and no settings. Adding or removing it makes
no difference to the frontend output.
See chapter Site set.
No. Site sets were introduced in TYPO3 13.1. On TYPO3 12 the
Configuration/Sets/ directory of this extension is ignored by the
core. The banner is rendered by the event listener on both TYPO3 12 and
13, so nothing is missing on TYPO3 12.
The settings moved from the sys_template record to the site root's
pages record. Run the database analyser, then the upgrade wizard
EXT:ok_prive_consent: Move consent banner settings from
sys_template to pages in Admin Tools >
Upgrade.
See chapter Upgrading from version 4.1.1 or older.
Yes. In a TYPO3 multi-site setup, the backend module resolves the correct site root page automatically. Each site can have its own independent consent script and enable/disable state.
In the backend module, uncheck the Enable Prive script toggle and click Save. The saved script is preserved but no longer rendered on the frontend. Re-enable it at any time by checking the toggle again.
See chapter Contact.