Frequently Asked Questions (FAQ) 

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.

Navigate to Web > Prive 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 automatically on all frontend pages by a PSR-14 event listener as soon as the extension is installed. No site set, TypoScript, or template changes are needed.

No. The extension ships a site set called oliverkroener/ok-prive-consent (shown in the backend as [kroener.DIGITAL] Prive Consent), but it is empty and optional. The banner is injected by a PSR-14 event listener that is registered through the extension's Services.yaml, so it works whether or not the set is referenced.

If your site's config.yaml already lists the set under dependencies, you may keep it or remove it.

See chapter Site set.

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.

Yes. The button is styled via Resources/Public/Css/prive-cookie-button.css. You can override these styles with custom CSS in your site package.

See chapter Cookie button styling.

See chapter Contact.