Back to DigiConsent

Banner Not Showing

One of the most frustrating experiences with any cookie consent plugin is when the banner simply doesn’t appear on your website. You’ve installed DigiConsent, configured your settings carefully, but visitors to your site see nothing. This comprehensive guide walks you through every possible reason why your banner might not be showing and provides detailed solutions to get it working.

Understanding why banners fail to appear requires knowledge of how WordPress loads content, how browsers cache resources, and how various plugins and themes interact. The consent banner is added to your pages through JavaScript and CSS that must load correctly, execute in the right order, and not be blocked by other code. When any step in this chain breaks, the banner won’t appear.

Caching: The Most Common Culprit

Caching is hands-down the number one reason cookie consent banners don’t appear. Caching plugins and services store static versions of your pages to improve loading speed. When you install DigiConsent or change its configuration, visitors might still see cached versions of pages that were saved before the plugin was active. The cached HTML doesn’t include the banner code, so no banner appears.

There are multiple layers of caching that might be preventing your banner from showing. WordPress caching plugins like WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, and others create static HTML files. Your browser caches resources locally. Your hosting provider might have server-level caching. If you use a CDN like Cloudflare, it caches your entire site on edge servers worldwide. Each of these caches must be cleared.

Complete cache clearing procedure:

  1. Clear your WordPress caching plugin cache – Look in the plugin’s settings or admin bar menu for “Clear Cache,” “Purge Cache,” or “Delete Cache” buttons
  2. Clear your browser cache completely – In Chrome: Settings → Privacy and Security → Clear browsing data → Select “Cached images and files” → Clear data
  3. Clear your CDN cache if using Cloudflare or similar services – Log into your CDN dashboard and look for purge or cache clearing options
  4. Clear object cache if you’re using Redis or Memcached – These persistent caches can also store old data
  5. Clear server-side cache through your hosting control panel – Many hosts have their own caching layers

After clearing all caches, test in a private browsing window (Incognito in Chrome, Private Window in Firefox). Private browsing doesn’t use cached data from previous visits, so it shows you exactly what new visitors see. If the banner appears in private browsing but not in your regular browser, you have a browser cache issue. Clear your browser cache more aggressively or try a hard refresh with Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac.

JavaScript Errors Preventing Execution

JavaScript errors from other sources can prevent DigiConsent’s code from running. JavaScript is executed sequentially, and if an earlier script throws an error, it can stop subsequent scripts from executing. Even a single JavaScript error from your theme or another plugin can break the entire page’s JavaScript functionality, including your cookie banner.

To diagnose JavaScript errors, open your browser’s developer console. In most browsers, press F12 or right-click anywhere on the page and select “Inspect,” then click the “Console” tab. Look for messages in red, which indicate errors. These errors show you the file and line number where the problem occurred.

Common JavaScript errors that affect cookie banners include:

  • Uncaught TypeError: $ is not a function – jQuery isn’t loaded correctly or there’s a conflict between different JavaScript libraries
  • Uncaught ReferenceError: variableName is not defined – A script is trying to use a variable or function that doesn’t exist, often because scripts are loading in the wrong order
  • Cannot read property of undefined – A script is trying to access a property of something that hasn’t been created yet
  • Syntax error – Malformed JavaScript code, often from poorly coded themes or plugins

If you see errors that don’t mention DigiConsent but come from other plugins or your theme, those errors might still be preventing the banner from showing. JavaScript execution stops at errors, so even unrelated errors can break your banner.

Solution approach: Identify which plugin or theme file is throwing the error by looking at the file path in the error message. If it’s from a plugin, try updating that plugin to the latest version or temporarily disabling it to confirm it’s the cause. If it’s from your theme, contact the theme developer or switch to a default WordPress theme temporarily to test.

Plugin Configuration Issues

Sometimes the banner doesn’t show because of how DigiConsent itself is configured. While the plugin works out of the box with default settings, certain configuration choices can prevent the banner from appearing in specific scenarios.

Banner status check: First, verify the banner is actually enabled. Go to the DigiConsent settings page and confirm there’s not a toggle or checkbox that disables the banner. Some users accidentally disable the banner during testing and forget to re-enable it.

Geographic restrictions: If you’re using DigiConsent Pro with geolocation features, the banner might be configured to only show to visitors from specific countries or regions. If you’re testing from a location outside those regions, you won’t see the banner. Check your geolocation settings and ensure your current location is included in regions where the banner should appear. Use a VPN to test from different geographic locations if needed.

Page-specific display rules: Some configurations allow you to exclude the banner from specific pages or post types. Review any display rule settings to ensure you haven’t accidentally excluded the pages you’re testing. Common mistakes include excluding all pages when you meant to exclude specific pages, or using incorrect URL patterns in exclusion rules.

User role restrictions: Verify that the banner isn’t configured to hide for administrators or logged-in users. It’s common to test while logged in as an administrator, and if the banner is set to hide for admins, you won’t see it. Log out or test in a private browsing window where you’re not logged in to see what regular visitors see.

Theme Compatibility Problems

Your WordPress theme controls the structure and output of your pages. Some themes, particularly poorly coded ones or themes with aggressive optimization, can interfere with how plugins add content to pages. The consent banner needs to be inserted into your page’s HTML and rendered properly, and themes can block this in several ways.

Missing wp_footer hook: WordPress uses action hooks to allow plugins to insert code into pages. The wp_footer() hook is essential and should be called just before the closing </body> tag in your theme’s footer.php file. DigiConsent uses this hook to insert the banner code. If your theme doesn’t include this hook, plugins cannot add their code to the page.

To check if your theme has the wp_footer hook, use an FTP client or your hosting file manager to navigate to your theme’s directory, typically at wp-content/themes/your-theme-name/. Open the footer.php file and search for wp_footer(). It should appear before the closing </body> tag. If it’s missing, this is definitely your problem.

Solution: Add the wp_footer hook to your theme by editing footer.php (use a child theme to preserve changes during updates). Add this code right before the closing </body> tag:

<?php wp_footer(); ?>
</body>
</html>

Theme JavaScript conflicts: Some themes load JavaScript libraries like jQuery in non-standard ways or include their own versions that conflict with WordPress’s built-in libraries. This can break DigiConsent’s JavaScript functionality. Premium themes with extensive customization options are particularly prone to this issue.

Testing for theme conflicts: The most reliable way to test if your theme is causing the problem is to temporarily switch to a default WordPress theme like Twenty Twenty-Four. If the banner appears with the default theme but not with your custom theme, you’ve confirmed a theme conflict. This doesn’t mean you have to abandon your theme, but it tells you where to focus troubleshooting efforts.

Plugin Conflicts

WordPress sites typically run multiple plugins simultaneously, and these plugins don’t always play nicely together. Another plugin might interfere with DigiConsent in ways that prevent the banner from showing. The interference can be subtle, like loading scripts in an incompatible way, or obvious, like another plugin trying to manage cookies or consent.

Plugins particularly likely to conflict include other cookie consent or privacy plugins, aggressive caching plugins, JavaScript optimization plugins, security plugins that modify scripts, and plugins that heavily customize the WordPress admin or frontend output. Page builders, popup plugins, and chatbot plugins can also interfere.

Systematic conflict testing: The only reliable way to identify plugin conflicts is through elimination testing. This process takes time but is highly effective:

  1. Create a full backup of your site before making changes
  2. Deactivate all plugins except DigiConsent
  3. Test if the banner appears – if it does, you have a plugin conflict
  4. Reactivate plugins one by one, testing the banner after each activation
  5. When the banner stops appearing, the last plugin you activated is the culprit

This process won’t harm your site because deactivating plugins doesn’t delete their data or settings. Everything returns when you reactivate them. However, do this during low-traffic periods or on a staging site if possible, as some plugins might cause visible changes when deactivated.

Once you identify a conflicting plugin, you have several options. Check if both plugins have updates available, as compatibility issues are often fixed in newer versions. Contact support for both plugins and report the conflict. Look for alternative plugins that provide similar functionality without conflicting. Sometimes you can resolve conflicts by changing settings in one or both plugins, such as disabling script optimization features.

Script Loading and Optimization Issues

Many WordPress optimization plugins and services modify how JavaScript loads to improve performance. Features like script deferring, async loading, script combining, and minification can break DigiConsent if not configured correctly. These optimizations change the order and timing of script execution, which can prevent the banner from initializing.

Defer and async attributes: When JavaScript files are marked to load with defer or async attributes, they load differently than normal scripts. The defer attribute makes scripts execute after the page has finished parsing, while async makes them execute as soon as they’re downloaded. If DigiConsent’s scripts are deferred but they depend on other scripts that aren’t, you can have timing issues.

Optimization plugins like Autoptimize, WP Rocket, or Asset CleanUp often have settings to exclude specific scripts from optimization. If you’re using such plugins, try excluding DigiConsent’s JavaScript files from deferring, combining, or minification. Look for settings labeled “JavaScript exclusions,” “Scripts to exclude from defer,” or similar options.

Script concatenation: Some optimization plugins combine multiple JavaScript files into one large file to reduce HTTP requests. While this can improve performance, it can break scripts that expect to load separately or in a specific order. DigiConsent’s scripts need to execute at the right time relative to page loading, and concatenation can disrupt this timing.

Solution: In your optimization plugin settings, add DigiConsent’s JavaScript files to the exclusion list. The exact file names may vary by version, but typically look for files containing “digiconsent” in their names. After excluding them, clear all caches and test again. This ensures DigiConsent’s scripts load normally without optimization interference.

CSS Display Issues

Sometimes the banner is actually present in your page’s HTML but isn’t visible due to CSS issues. The banner code loads and executes correctly, but styling problems make it invisible, positioned off-screen, or hidden behind other elements. This is different from the banner not loading at all.

To diagnose this, use your browser’s developer tools. Right-click anywhere on the page and select “Inspect” or press F12. In the Elements or Inspector tab, press Ctrl+F (or Cmd+F on Mac) and search for “digiconsent” or whatever class name the plugin uses for its banner. If you find the HTML elements but don’t see the banner visually, you have a CSS problem.

Common CSS issues include:

  • display: none or visibility: hidden applied by theme or plugin CSS
  • z-index too low, causing the banner to appear behind other page elements
  • Incorrect positioning that moves the banner off-screen
  • Opacity set to 0 or near-zero, making the banner transparent
  • Overflow hidden on parent elements that clips the banner

When you inspect the banner elements in developer tools, you can see which CSS rules are being applied. Look for rules that might hide the banner and identify where they come from (theme stylesheet, plugin, inline styles). You can temporarily disable CSS rules in developer tools to test if removing them makes the banner appear.

Solution: Use design customization to override problematic rules. If you find that a theme rule sets display: none on the banner, you can add more specific CSS that sets display: block !important. The !important declaration gives your rule higher priority. Use design customization through your theme’s customizer (Appearance → Customize → Additional CSS) or through a custom CSS plugin.

Server-Side Issues

Server configuration problems can prevent the banner from appearing, though these are less common than the issues already discussed. Server-side issues typically manifest in other ways too, like general WordPress errors or functionality problems across the entire site.

PHP errors: If DigiConsent’s PHP code encounters an error, it might fail to output the necessary HTML and JavaScript for the banner. Check your error logs for PHP errors. You can enable WordPress debugging by adding these lines to your wp-config.php file:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

This creates a debug.log file in your wp-content directory that captures PHP errors without displaying them to visitors. Review this log file after trying to load a page with the banner to see if any errors appear.

Insufficient PHP resources: If your server has very low PHP memory limits or execution time limits, DigiConsent might not have enough resources to function properly. Modern WordPress sites need at least 256MB of PHP memory. Check your current limit in WordPress Site Health (Tools → Site Health → Info → Server).

File permission issues: If DigiConsent needs to write files (like cache files or logs) and doesn’t have permission, it might fail silently. Proper WordPress file permissions are 644 for files and 755 for directories. Incorrect permissions can cause various issues.

Testing Methodology for Diagnosis

When troubleshooting banner visibility issues, follow this systematic approach to efficiently identify the cause:

  1. Clear all caches and test in private browsing – This eliminates caching as a variable
  2. Check the browser console for JavaScript errors – Identify if scripts are failing
  3. Inspect the page HTML for banner elements – Determine if it’s a loading issue or a display issue
  4. Test with a default theme – Rules out theme conflicts
  5. Disable all other plugins – Identifies plugin conflicts
  6. Review DigiConsent configuration – Ensures the banner is enabled and configured correctly
  7. Check error logs – Reveals server-side PHP errors
  8. Test from different devices and browsers – Determines if it’s browser or device-specific

Each step either solves the problem or provides information that narrows down the cause. By working through this checklist methodically, you’ll identify why your banner isn’t showing and be able to implement the appropriate solution. Remember to test after each change to confirm whether it resolved the issue before moving to the next troubleshooting step.

Similar Articles

Back to DigiConsent