Lightweight Cookie Banner: setup and help

1. Check whether MPR Cookies Revolution is active. Installation refuses to proceed while that module is installed and enabled.
2. Open Modules > Module Manager > Upload a module and upload the Lightweight Cookie Banner ZIP.
3. Open Configure to reach Settings.
4. Set your text and policy link, review appearance and consent settings, then save.
5. Open the storefront in a browser without a saved consent choice and test Accept and Deny.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.

Closing the notice records denial. Clicking the overlay in Center Modal also records denial.

Edit these multilingual fields for each shop language:

The module includes default wording for English, German, French, Polish, Italian and Spanish. Missing wording falls back through the configured language defaults. Review the actual text in each storefront language.

On installation, the module reads theme CSS, including custom and theme CSS, Bootstrap properties and button/header rules. Detected theme colors take precedence over the fallback hex values. Change the settings after checking contrast in your store.

The header bootstrap reads the browser's valid saved mprcookie_consent choice first. It uses that choice for the initial ad_storage, ad_user_data, ad_personalization and analytics_storage states. Without a valid cookie, it uses Default consent state. It initializes functionality_storage, personalization_storage and security_storage as granted.

Accept sends an update with the four ads and analytics states granted. Deny or close sends them denied. When the shared coordinator assigns Consent Mode to another owner, this module suppresses both its bootstrap and its updates; the settings page reports the owner.

The module records a choice and sends signals. It does not scan cookies, classify categories or automatically prevent every unrelated script from running. Configure your other scripts to respect the stored choice and consent signals.

The module registers local assets through displayHeader and actionFrontControllerSetMedia. Banner markup uses displayFooter or displayFooterAfter, with a guard against duplicate rendering.

The markup is initially hidden. JavaScript shows it when there is no valid choice. Accept and Deny store granted or denied in mprcookie_consent on the shop host, with path=/, SameSite=Lax and Secure on HTTPS. A valid choice keeps the banner hidden on later visits until the cookie expires or is removed.

Test both choices in separate fresh sessions. Inspect the cookie and reload to verify the banner stays hidden. Inspect dataLayer to verify the initial state uses the saved choice and that clicking a button sends an update when this module owns Consent Mode.

If the banner does not appear, remove the consent cookie in your test browser, check Enable Cookie Banner, JavaScript errors and the footer hooks. Changing text or expiry does not invalidate visitors' existing choices. There is no policy-version setting or bulk consent-reset action in this module.

The browser dispatches mprcookie:consent after a choice:

document.addEventListener('mprcookie:consent', function (event) {
  if (event.detail.consent === 'granted') {
    // Start your consent-dependent script here.
  }
});

Also check the saved cookie when your custom script first starts. The event is not replayed on later pages for a visitor who already chose.

Use #mprcookiebanner, .mprcookie-policy-link, .mprcookie-accept and .mprcookie-deny for theme styling. Override markup at themes/your-theme/modules/mprcookiebanner/views/templates/hook/cookie-banner.tpl.

Turn off Enable Cookie Banner to stop its output. Uninstall from Module Manager to remove its menu and module configuration. Uninstall does not clear cookies already stored in visitors' browsers. Existing tracking scripts belong to their own integrations and are not removed by this action.