Troubleshooting

Start with the Setup status panel at the top of the module settings. It often already shows what is missing.

Check in turn:

1. Is it on? In Settings, Show the cookie banner must be on.
2. You have already consented. Consent is stored in the browser (the mv_cookie_consent cookie). The banner appears again only after it expires. Try an incognito window or delete this cookie.
3. An ad blocker with a filter against cookie banners hides the banner from visitors too. Turn it off for a test.
4. A tool reporting itself as a robot. Robots and speed-measuring tools do not see the banner by default (Do not show the banner to robots). If you test with such a tool, turn this option off.
5. The module has no valid license. It does not work without one. Look at the License panel.
6. Cache. After changing the settings, clear the PrestaShop cache and the browser cache.

(e.g. chat, a payment gateway, a product filter)

1. In the Scripts panel find the affected module or service and set it to Do not block. Save.
2. If you do not know which one it is, temporarily turn off Block scripts before consent. If the problem disappears, blocking was the cause. Turn it on again and disable rules one by one.
3. Do not assign modules that only display content to categories. Only what sends data to an advertising or measuring service should be blocked.

The shop probably contains another Consent Mode code or Google Tag Manager before the module.

• Check that the theme or another module does not insert its own Consent Mode (the “default” setting) or GTM. If so, remove it from the theme or module.
• If GTM is inserted by another module, leave the Google Tag Manager field in the module empty.
• Check that Google Consent Mode v2 is on.
• Set non-Google tags in GTM according to the mv_cookies_consent event.

The list fills as pages of the shop are visited, at most once every 10 minutes. Open several pages (home, category, product, cart), wait and refresh the module settings.

JavaScript merging (CCC) is on in PrestaShop, so module scripts are in one file and cannot be blocked by module. Turn merging off under Advanced Parameters → Performance, or block the specific service instead of the module.

After consent is withdrawn the module deletes the cookies of services it knows (the list in the Scripts panel), also on the parent domain. For an unknown service or a custom script it may not know which cookies it creates. Assign it to a category (via Custom rules) so it does not run before consent, and list it in your Cookie Policy. If cookies persist, contact support.

• Check that Store consent records is on in Advanced.
• Check that a firewall or security add-on does not block calls to /module/mv_cookies/consent.
• Records older than the set number of months are deleted automatically. If the list is empty, look at Keep records.

If an update fails, it usually rolls back by itself. If it did not, the original version is saved in this folder:

modules/.mvkit/backup/mv_cookies@<version>

Rename the modules/mv_cookies folder (e.g. to mv_cookies_new) and rename the backup folder to mv_cookies. The settings remained in the database. If you are unsure, contact support or your server administrator.

• Texts: Settings → Title and Banner text for each language. An empty field means the default text.
• Colors and corner radius: the Appearance panel.
• Position: Banner position.
• Font: taken from the theme. It cannot be set in the module.

If you cannot solve a problem, write to support via the contact page and include:

• the module version (shown in the License panel) and the PrestaShop version,
• the exact error text (ideally a screenshot),
• a description of what you did and what you expected,
• the address of your shop.

Support and updates are included for the first 12 months after purchase.