Troubleshooting and FAQ
This article collects the most frequent problems and questions about Lightweight Cookie Notice, with their solutions.
Before you test any change, clear the cache of your caching plugin and use a private browser window. The plugin saves the visitor’s choice in the browser, so a normal window can still hold the choice of a previous test.
Troubleshooting
The notice is displayed again on every page
The button that your visitors click does not save the choice.
- Go to Cookie Notice → Options → Content → Cookie Notice.
- Check the action of each button. Close Cookie Notice hides the notice only for the current page view.
- Assign Accept Cookies, Accept All Cookies, or Reject All Cookies to the buttons that must save the choice.
- Click Save settings.
Other possible causes:
- Expiration in Options → Advanced → Cookie Attributes is set to a short period, such as One Hour.
- (Pro) The Domain option contains a domain that does not match the domain of your site. The browser refuses the cookies and the choice is never saved. Clear the option or enter the correct domain.
- The browser is set to delete the cookies when it is closed.
See Understanding Button Actions.
The notice is not displayed
- You already made a choice in this browser. Use a private window, or click the revisit consent button.
- Test Mode is on and you are not logged in as administrator. Turn it off in Options → Advanced → Behavior.
- Geolocation is on and you are outside the selected countries, or the MaxMind database path is wrong. See Showing the Notice Only in Selected Countries.
- An optimization plugin delays or changes the JavaScript of the plugin. See the “JavaScript optimization” section of Using the Plugin with Caching Plugins.
- The page is an AMP page. AMP is not supported.
There is no button to reject the cookies
The default configuration has the Settings and Accept buttons. To add a reject button, set the action of one button of the notice, for example Button 3, to Reject All Cookies and enter its text. See Configuring the Cookie Notice.
I want to remove the Settings button
Set Button 1 Action to Disabled in Options → Content → Cookie Notice.
The dismiss button closes the notice instead of opening the cookie settings (free version)
In the free version before 1.23, the Open Cookie Settings action of Dismiss Button Action closed the notice. This is fixed in version 1.23.
If you selected Open Cookie Settings before the update, the option now shows Close Cookie Notice. To open the cookie settings from the dismiss button:
- Go to Cookie Notice → Options → Content → Cookie Notice.
- In Dismiss Button Action, select Open Cookie Settings again.
- Click Save settings.
The sections are displayed in a different order after an update
From version 1.23 (free) and 1.56 (Pro), the sections of the cookie settings window are displayed from the lowest to the highest Priority. Before, they were displayed in the order in which they were created. Edit your sections in Cookie Notice → Sections and set their Priority. See Creating Sections and Categories.
The visitor rejects, but the cookies are still set
The plugin controls only the scripts entered in the HTML Head and HTML Body fields of the categories. If a tracking script is added by your theme, by another plugin, or by a page builder, it runs regardless of the visitor’s choice.
Remove the script from where it is added and paste it in the category it belongs to. See Running Scripts Based on Visitor Consent.
Also note that the plugin cannot delete cookies that are already in the browser if they are third-party cookies or have the HttpOnly attribute. Rejecting stops the script, so the cookies are no longer updated or created.
The scripts are not added after the visitor accepts
Check these points in order:
- The category is assigned to a section.
- The accept button uses Accept All Cookies, or the category has Initial State on.
- You opened a new page after accepting, or Reload Page is on.
- Your caching plugin is configured as described in Using the Plugin with Caching Plugins.
The Google Tag Manager container is not loaded (Pro)
With Google Consent Mode on, the plugin loads the container only after the visitor grants at least one consent mode parameter. The container is not loaded before the visitor makes a choice, and it is not loaded when no parameter is granted. See Setting Up Google Consent Mode.
My custom revisit consent link does nothing
Check the class name. The free and the Pro version use different classes:
| Version | Class |
|---|---|
| Free | daextlwcnf-revisit-consent-trigger |
| Pro | daextlwcn-revisit-consent-trigger |
See Letting Visitors Change Their Preferences.
The text “daextlwcn_print_scripts(false);” is displayed on my pages
Page Fragment Caching Exception (W3TC) is on in Options → Advanced → Behavior, but W3 Total Cache is not configured to process it. Either complete the W3 Total Cache configuration described in Using the Plugin with Caching Plugins, or turn the option off.
Two notices are displayed
The free and the Pro version are both active. Deactivate the free version.
A JavaScript error is reported in the browser console
- Update the plugin to the latest version.
- If the error is still present, set Assets Mode to Development in Options → Advanced → Behavior and clear the caches. In this mode the plugin loads its non-minified files, and the error message shows the exact file and line.
- Contact support with the URL of the page and the text of the error.
Set Assets Mode back to Production when the investigation is finished.
The changes I make are not visible on the front end
- Clear the cache of your caching plugin and of your browser.
- If Transient Expiration is greater than 0, run Delete Transient in the Maintenance menu.
The consent log is empty
See the “If the records are not saved” section of Reviewing and Exporting Consent Records.
A security plugin reports the plugin as vulnerable
Update the plugin to the latest version. Security fixes are included in the updates and listed in the changelog. If the report is still displayed with the latest version installed, contact support and include the details of the report.
Frequently asked questions
Does the plugin make my site compliant with GDPR or CCPA?
The plugin gives you the tools to inform visitors, collect their consent per category, load scripts only after consent, and keep a log of the consents. Whether your site is compliant depends on the laws that apply to you and on how you configure the plugin. We cannot give legal advice.
Does the plugin scan my site and block cookies automatically?
No. The plugin does not scan the site and does not categorize or block existing scripts automatically. You add your scripts to the categories yourself. If you need automatic scanning and blocking, consider a Consent Management Platform.
Does the plugin support Google Consent Mode?
Yes, in the Pro version. See Setting Up Google Consent Mode.
Does the plugin work with AMP?
No. AMP pages are not supported.
Does the plugin work with caching plugins?
Yes. See Using the Plugin with Caching Plugins.
Does the plugin work on a multisite network?
Yes. You can activate it for the whole network or on single sites. Each site has its own options, sections, categories, and cookies, and the consent of a visitor is valid only for the site where it was given. There are no network-wide settings.
Can the consent be shared between subdomains?
Yes, in the Pro version, with the Domain option. See Advanced Settings Reference.
Which HTML tags can I use in the texts?
Message Text, Description Header, Description Footer, and the Purpose of the cookies accept these tags: p, a, strong, br, ol, ul, li. The a tag accepts the href, title, target, and rel attributes.
How do I translate the plugin?
- Texts displayed to visitors: the message, the button texts, the descriptions, and the names of sections and categories are the texts you enter in the plugin options and menus. Enter them in the language of your site.
- Multilingual sites: the texts can be translated with translation plugins such as WPML and TranslatePress.
- Admin interface: the plugin is translation ready. You can translate it with a tool such as Loco Translate. The text domain is
lightweight-cookie-notice-freefor the free version andlightweight-cookie-noticefor the Pro version.
Does the plugin load resources from external servers?
| Resource | When |
|---|---|
| Google Fonts | By default. To avoid it, clear Google Fonts Embed Code URL. See Customizing the Style. |
| HostIP.info | Only when Geolocation is on with the HostIP.info service. |
| Google Tag Manager | Only in the Pro version, when Google Consent Mode is on, a container ID is set, and the visitor has granted at least one consent mode parameter. |
Which cookies does the plugin set?
The plugin sets a few cookies to remember the visitor’s choice. They are listed in Technical Reference. You can describe them to your visitors by adding them to the Cookies menu, in your “Necessary” category.
Can I hide the notice with JavaScript in a specific situation?
Yes. If the acceptance cookie of the plugin is set to “1”, the notice is not displayed. For example, to hide the notice inside a page loaded in your own mobile app:
document.cookie = 'daextlwcnf-accepted=1; path=/';
Use daextlwcn-accepted with the Pro version. Run the code before the page has finished loading.
Setting only this cookie hides the notice without enabling any category and without creating a record in the Consent Log.
Can I use the free and the Pro version together?
No. Use one version at a time. To move to Pro, see Migrating from Free to Pro.
How do I get support?
- Free version: use the support forum on WordPress.org.
- Pro version: use the support page on daext.com. Questions about the Pro version cannot be answered in the WordPress.org forum.