Help / WP Rocket and unstyled banners
If your site uses WP Rocket and your cookie banner shows up as plain text at the bottom of the page, under your footer, one WP Rocket setting is hiding its design. The fix takes a couple of minutes.
What you might see:
Your tracking is still held back. CookieFlame keeps blocking tracking until a visitor makes a choice, so nothing runs before they agree. But because visitors don’t see a proper banner, hardly anyone makes a choice, and your analytics and ads stay off for them. So it’s worth fixing straight away.
WP Rocket has a speed feature called Remove Unused CSS. CSS is the part of a website that controls how things look. WP Rocket checks each page, keeps only the design rules it can see being used, and drops the rest. CookieFlame adds its banner just after the page has loaded, so WP Rocket doesn’t see the banner when it checks. It decides the banner’s design isn’t needed and leaves it out. The fix is to tell WP Rocket to always keep CookieFlame’s design file.
/wp-content/plugins/cookieflame/(.*).cssYou only need this one line, whether you use free CookieFlame or CookieFlame Pro. Pro uses the same banner, so it has no separate design file.
CookieFlame works with WP Rocket and other caching tools, so once this line is in place you keep your fast pages and a banner that looks right.
cookieconsent.css. If it’s there, CookieFlame’s design file is loading. If it isn’t, search for cc-banner instead: it should appear inside the block that starts with <style id="wpr-usedcss">.#cc-banner#cc-(.*).cc-(.*)Other speed plugins have a similar “remove unused CSS” feature, and it can cause the same problem. The fix is the same idea: tell the plugin to keep CookieFlame’s design. After the change, check your site the same way as above.
cookieflame/assets/css/ to UCSS Inline Excluded Files (called UCSS File Excludes and Inline in older versions). Save, then click Purge All.cookieflame/assets/css/ to Excluded Stylesheets. Save, click Clear Used CSS, then clear any other caches.#cc- and .cc- to Include CSS Selectors, each on its own line. Save, then clear the cache.*cookieconsent.css*, choose CSS as the type and Remove unused CSS as the operation. Save, then purge the cache.Moving a licence, renewals, caching, video placeholders and more.
→
Connect Tag Manager, choose Basic or Advanced Consent Mode and check every tag follows the visitor’s choice.
→
Confirm suggestions, run a check-up and keep your cookie list clean.
→
← All help topics · Still stuck? Send us a message.