Support

Paddle sends two e-mails after the purchase. It can take up to 15 minutes for the e-mails to arrive. Please also check your spam folder.

Paddle sends 2 e-mails, one of which contains a link to the invoice. Click on the link in the e-mail to save your contact details for your invoice. If you forgot your VAT ID, please read the article Specify VAT ID after purchase.

If you were unable to enter your VAT ID during the checkout process, or if you forgot, please read the article Specifiy VAT ID after purchase.

If the option for merging JavaScript is activated for caching, inline JavaScript such as AdSense code is also written to the merged JavaScript file. To prevent this, the JavaScript must be marked to be excluded from the optimization. You can read how this works here.

Caching systems generally increase the amount of storage space used because each page is stored as a file on the server. If it should come to a consumption of several GB, there is probably a problem with the JavaScripts. Some plugins change their JavaScript code for each page, which causes a merged JavaScript file to be created for each page when JavaScript merging is activated. In this case, it is advisable to disable the Merge option under Advanced Settings > JavaScript.

To find the cause, use your browser in incognito/private mode to visit your website. After each test, close all incognito windows and open a new incognito window to make sure that no data is loaded from the cache. In your regular browser window, you stay logged in to WordPress, only the test visits are performed in the incognito window. Now proceed as follows to find the cause: Using the developer tools, check whether a JavaScript error is displayed in the console (errors are displayed with red text). If there is an error, disable Borlabs Cache and try again. If the error is gone, disable the Merge option in the Advanced Settings under JavaScript and CSS, enable Borlabs Cache, and reload your website in incognito mode. If the website is working now, there is an error in one of your JavaScript or CSS files.

First of all an important information: not all WordPress themes are WooCommerce + Caching compatible, therefore it can happen that all WooCommerce pages have to be excluded from caching. Exclude all URLs, such as shopping cart or checkout URLs, from caching. To do this, add the URLs under Advanced Settings > Cache Exceptions.

Please remove the code you have stored in Borlabs Cookie from all other places. Only Borlabs Cookie is allowed to deliver the code of e.g. Matomo/Piwik.

In Borlabs Cookie please click on the tab Styling and then on Save. Then reload the page in the incognito mode/private mode of the browser. If this does not help, please check under Settings > General whether the URLs are set correctly to https. Please disable caching and optimization plugins (Borlabs Cache, WP Rocket, WP Fastest Cache, Autoptimizer, Fast Velocity Minify, etc.) while setting up Borlabs Cookie.

If the cookie selection appears again and again, please check the entry of Domain under Multisite Network Cookie Settings. Here the domain (without https://) of your website must be deposited. If your URL is e.g. https://www.example.com enter www.example.com there.

In order for the cookie selection to appear, a form of tracking must be stored. Please read the setup article here: Setting up Borlabs Cookie. Please disable caching and optimization plugins (Borlabs Cache, WP Rocket, WP Fastest Cache, Autoptimizer, Fast Velocity Minify, etc.) while setting up Borlabs Cookie. Please check under Settings > General whether the URLs are set correctly to https. Alternatively, you can always select the value in the settings under Show cookie box. If the cookie box appears only in some browsers, check whether you have enabled the Do Not Track option in Borlabs Cookie. If enabled, browsers with Do Not Track active will not display a cookie box.

If the cookie box does not disappear after a selection, this can usually have two causes. Cause 1: please check if you use the plugin Table of Contents, if yes, please read this article. Cause 2: check if the JavaScript you have placed in Borlabs Cookie contains a syntax error.

Please deactivate all other plugins that embed the Google Analytics or Facebook code or remove the tracking JavaScripts. Only Borlabs Cookie is allowed to deliver the JavaScripts for Google Analytics and Facebook. Plugins such as MonsterInsights must be deactivated.

The Google Analytics opt-out does not remove the tracking code, but places a special Google cookie that tells Google that the visitor does not want to be tracked. The name of the cookie is ga-disable-UA-yourTrackingID-1 and is set when the opt-out button is clicked. Tools like Ghostery continue to report that Google Analytics is present, but Google will no longer track the visitor. This is the default procedure for opting out of Google Analytics.

The AdSense code to display the banners you usually don't insert into Borlabs Cookie, but use the shortcodes of Borlabs Cookie to block the banners first. At the place where your previous AdSense code is, you insert it in between the shortcode [borlabs_cookie_third_party]Your AdSense Code[/borlabs_cookie_third_party].

Currently only Google Maps, which is integrated via iframe, can be detected and blocked automatically. Google Maps, which is integrated via JavaScript API, cannot currently be blocked, as is the case with WP Google Maps Pro. Update 1.9 will provide a way for third parties to block Google Maps embedded via JavaScript.

The validation in Google Search works without problems via meta tag or via .html file. If you want to perform the validation via Google Analytics code, this can lead to problems. You can try enabling Cookies for bots/crawlers. If this does not work, you will need to use the other validation options mentioned above.

Information about your license, such as validity (Updates & Support), can be seen after you have stored the license key in Borlabs Cookie. 32 bit outdated servers erroneously display the "valid to" date with the current date. This is because 32 bit servers cannot display a date greater than 2038. The incorrect display will be corrected shortly and has no influence on the behavior of the plugin.