Troubleshooting and FAQ
The pop-up keeps appearing
- Once after going live (or after approving a service with blocking on): visitors are asked again once, with their choices ticked. This is by design.
- On every visit: the choice is saved in a cookie for 365 days. A browser that refuses or clears cookies asks again each time, and
www.example.comandexample.comcount as two sites.
The pop-up does not appear
- Check the status line: Banner off means the module is disabled or not hooked to
displayHeaderanddisplayFooter. Hook it again with Transplant a module in Design > Positions; some themes need it added to their own footer settings. - Open the shop in a private window: you may have chosen already.
- Search engine bots and headless browsers never see the pop-up.
A tracker still loads before consent
- The status line says Blocking on.
- The service is approved; new, ignored and unclassified items are not blocked.
- Its state in Review explains any exception (Necessary, Consent Mode, Banner only, your choice).
- Allow all modules by default is off.
- Your page cache is purged.
- If another script adds the tracker, try Strict mode in the preview.
A page cache module is installed
Purge its cache after you switch blocking on and after you approve new services. Until then, cached pages keep the old script tags and visitors are asked again only when the cache refreshes. No preview bar in Check the shop? Purge the cache too.
"Unable to install override" during installation
PrestaShop stops the installation when an override cannot be installed.
- "… is already overridden by …": another module overrides the same method. The overrides must be merged; contact our support.
- A file cannot be written: make PrestaShop's
overridefolder writable by the web server and install again.
Pages look wrong after an upgrade
Reload with Ctrl+F5. On the storefront, clear the cache in Advanced Parameters > Performance and purge any page cache or CDN. Since 2.6.1, the module's files carry their version in their address, so updates load the new files.
The scan stops with an error
- HTTP 400, 431 or 494: the browser sends more cookies than the server accepts. Clear this site's cookies and scan again.
- Session expired: sign in again and scan again.
- HTTP 403: a server security rule may block the scan; ask your host to allow it.
- Server error: check the logs and scan again.
If the shop is in maintenance mode, add your IP address in Shop Parameters > General > Maintenance so the scan sees the real pages.
Where to find the logs
In Advanced Parameters > Logs, filter the messages on "gdprpro". The module's messages start with "GdprPro", the scanner's with "gdprpro scanner".
Support
PrestaChamps develops and supports GDPR Compliance Pro. To contact us, open GDPR Config > Documentation and click Contact support. Please send:
- the module version and your PrestaShop and PHP versions;
- your theme and any cache, performance or consent module;
- what you did, what you expected and what happened, with the page address and screenshots;
- for blocking questions, the result of Run checks on the scanner page;
- the matching lines of Advanced Parameters > Logs.
If we need to look at your shop, create a separate employee account for us rather than sharing yours, and delete it afterwards.