Every WordPress plugin can encounter issues due to the diverse ecosystem of themes, plugins, and server configurations. DigiConsent is designed to work seamlessly with most WordPress installations, but occasionally you might experience problems. This comprehensive guide addresses the most common issues users face and provides clear, actionable solutions to get your cookie consent banner working perfectly.
Understanding why these issues occur helps you prevent them in the future and troubleshoot more effectively. Most problems fall into a few categories: caching conflicts, JavaScript errors, theme compatibility, plugin conflicts, or configuration mistakes. By working through these common scenarios systematically, you can resolve most issues quickly without needing support.
Banner Not Appearing on Your Website
The most frequently reported issue is when the cookie consent banner simply doesn’t show up on the website. This can be frustrating, but there are several common causes, each with straightforward solutions.
Caching is the primary culprit. When you first install or configure DigiConsent, your caching plugin or CDN might serve an old version of your pages that doesn’t include the consent banner code. WordPress caching plugins like WP Rocket, W3 Total Cache, or WP Super Cache store static versions of your pages for faster loading. If the cached version was created before you installed DigiConsent, visitors see the old page without the banner.
Solution: Clear all caches immediately after installing or configuring DigiConsent. This includes your caching plugin cache, browser cache, and any CDN cache like Cloudflare. In your caching plugin settings, look for buttons labeled “Clear Cache,” “Purge Cache,” or “Delete Cache.” After clearing, test in a private browsing window to ensure you’re seeing the fresh version.
JavaScript conflicts are another common reason. If another plugin or theme loads JavaScript that has errors, it can prevent DigiConsent’s scripts from executing properly. Open your browser’s developer console (F12 in most browsers) and look for red error messages. If you see errors mentioning “undefined” or “not a function,” there’s likely a JavaScript conflict.
Solution: Temporarily disable other plugins one by one to identify the conflict. Start with plugins that add functionality to your frontend like sliders, popup builders, or chat widgets. If the banner appears after disabling a specific plugin, you’ve found the culprit. Contact that plugin’s support or look for alternative plugins that work better with DigiConsent.
Scripts Not Being Blocked Properly
A critical function of DigiConsent is blocking tracking scripts until users provide consent. If Google Analytics, Facebook Pixel, or other tracking tools continue running even when consent is denied, your cookie management isn’t working correctly.
This usually happens because the scripts are being loaded by multiple sources. For example, you might have Google Analytics installed through DigiConsent’s integration, but also through another plugin, your theme, or hardcoded in your template files. When scripts are loaded through these alternative methods, DigiConsent cannot control them.
Solution: Audit all the places where tracking scripts might be loaded. Check your theme’s header.php and footer.php files for any hardcoded script tags. Review other plugins that might inject analytics code. Disable all alternative methods of loading tracking scripts and manage everything exclusively through DigiConsent. This centralized approach ensures proper consent management.
Additionally, verify that you’re using the correct script blocking method in DigiConsent. The plugin offers automatic script blocking which wraps scripts in special code that checks for consent. If you’re using custom code, ensure the type="text/plain" attribute is properly applied and the data-category attribute matches your cookie categories.
Consent Choices Not Saving
When users make their consent choices but those preferences don’t persist across page loads or browsing sessions, the problem typically relates to cookie storage. The DigiConsent plugin stores user preferences in browser cookies, and several factors can prevent this from working correctly.
Browser privacy settings are increasingly strict. Modern browsers like Safari and Firefox block third-party cookies by default and may have settings that prevent all cookies from being set. If users have enabled “Block all cookies” in their browser settings, consent preferences cannot be saved.
Solution: While you cannot control user browser settings, you can add clear messaging explaining that cookies must be enabled for the site to remember their preferences. Include this in your cookie policy and consider adding a notification when the plugin detects it cannot set cookies.
Cookie domain configuration issues also cause problems. If your WordPress site is configured with an incorrect site URL or you’re using a subdomain configuration that doesn’t match your cookie domain settings, consent cookies might be set for the wrong domain. Cookies set for www.example.com won’t be read on example.com and vice versa.
Solution: Verify your WordPress site URL in Settings → General matches your actual domain. Ensure consistency between www and non-www versions. DigiConsent automatically handles domain configuration, but if you’ve modified cookie settings or have a complex multi-domain setup, check the cookie domain settings in the plugin configuration.
Styling Conflicts and Display Problems
Visual issues where the banner appears broken, misaligned, or with incorrect styling usually stem from CSS conflicts between your theme and DigiConsent. WordPress themes load their own stylesheets, and sometimes their CSS rules are too broad or use !important declarations that override the plugin’s intended styling.
Common manifestations include banners that are too narrow or wide, buttons that don’t align properly, text that’s the wrong color or size, or spacing that looks wrong. These problems often appear only on specific page templates or device sizes.
Solution: Use your browser’s developer tools to inspect the banner elements. Right-click on the problematic element and select “Inspect” to see which CSS rules are being applied. Look for rules from your theme that are affecting the banner. You can use the design customization options.
For example, if your theme applies max-width: 100% to all div elements and this makes your banner too wide, you can add custom CSS targeting the banner specifically with a more specific selector and your preferred width. Always use your browser’s developer tools to test CSS changes before adding them permanently.
Mobile Responsiveness Issues
The banner might look perfect on desktop but appear broken or unusable on mobile devices. This happens because mobile browsers have different viewport sizes, touch interactions, and sometimes apply different CSS rules. Mobile Safari, for instance, has unique behaviors around fixed positioning and viewport units.
Solution: Test your banner on actual mobile devices, not just by resizing your browser window. Mobile browsers behave differently than desktop browser responsive mode. If the banner is cut off or buttons are too small to tap comfortably, you may need to adjust the banner’s position or size specifically for mobile viewports using CSS media queries.
DigiConsent includes responsive styling by default, but themes can interfere. Check if your theme is setting viewport meta tags correctly and not preventing the banner from displaying properly. The minimum tap target size should be 44×44 pixels according to accessibility guidelines, so ensure buttons are large enough on mobile devices.
Settings Not Saving in Admin Panel
When you configure settings in the DigiConsent admin panel but they don’t save when you click the save button, this typically indicates one of several backend issues. You might see a loading indicator that never completes, an error message, or the page might reload with your changes lost.
PHP memory limits can prevent settings from saving, especially if you have many options or large text fields. WordPress needs sufficient memory to process and store settings. If your server’s PHP memory limit is too low (below 128MB), complex operations may fail.
Solution: Check your PHP memory limit in your hosting control panel or by viewing the WordPress Site Health page (Tools → Site Health → Info → Server). If it’s below 256MB, contact your hosting provider to increase it or add this line to your wp-config.php file: define('WP_MEMORY_LIMIT', '256M');
Server timeout issues occur when the server doesn’t allow enough time for the save operation to complete. This is more common on shared hosting with strict resource limits. The request times out before WordPress can write the settings to the database.
Solution: Try simplifying your configuration. If you have very long privacy policy text or many custom scripts, save in smaller batches. Contact your hosting provider about increasing the max_execution_time PHP setting. Quality hosting providers can adjust these limits for your account.
Plugin Conflicts with Page Builders
Page builders like Elementor, Beaver Builder, or Divi load their own JavaScript frameworks and sometimes modify how WordPress outputs content. This can interfere with how DigiConsent initializes and displays the consent banner. The banner might not appear in the page builder preview, or it might appear but not function correctly.
Solution: Most page builders have an “edit mode” and a “preview mode.” The banner typically won’t appear in edit mode because page builders disable many frontend scripts to improve editor performance. Always test the banner in preview mode or on the actual published page, not in the builder’s editor.
If the banner still doesn’t work, check if your page builder has script optimization features that might be bundling or deferring JavaScript in ways that break DigiConsent. Look for settings related to “JavaScript optimization,” “defer JavaScript,” or “combine scripts” and try disabling them. These features, while beneficial for performance, can cause execution order issues.
Translation and Multilingual Issues
If you’re running a multilingual site using WPML, Polylang, or similar plugins, you might encounter issues where the banner doesn’t translate properly or shows the wrong language. This happens because the plugin needs to detect the current language and load the appropriate translations.
Solution: Verify that DigiConsent is configured to work with your multilingual plugin. Most translation plugins require you to register strings for translation. In DigiConsent settings, you should be able to configure different text for each language. Ensure you’ve set up translations for all banner text, button labels, and cookie descriptions in each language your site supports.
Clear your cache after setting up translations, as cached content might still show the default language. Test by switching languages on your site and checking that the banner updates accordingly. If using a language switcher, verify it’s not reloading the page in a way that bypasses the consent banner.
Database Errors After Plugin Update
Occasionally, after updating DigiConsent to a new version, you might see database errors or the plugin may stop working. This happens when database schema changes aren’t applied correctly during the update process. WordPress should automatically run update routines, but sometimes these fail on certain server configurations.
Solution: Try deactivating and reactivating the plugin. This forces WordPress to run the activation routine again, which should create or update necessary database tables. Your settings are stored in the database and won’t be lost during this process. Before doing this, it’s wise to backup your database using a plugin like UpdraftPlus or your hosting control panel’s backup tool.
If errors persist, check your error logs (typically found in wp-content/debug.log if debugging is enabled) for specific database error messages. These might indicate permission issues where the database user doesn’t have rights to create or modify tables. Contact your hosting provider if you see permission-related errors.
Quick Diagnostic Checklist
When troubleshooting any issue with DigiConsent, work through this systematic checklist. These steps resolve the majority of problems and help you gather information if you need to contact support.
- Clear all caches (plugin cache, browser cache, CDN cache)
- Test in a private/incognito browser window to eliminate browser cache issues
- Check browser console for JavaScript errors (press F12, look at Console tab)
- Temporarily switch to a default WordPress theme like Twenty Twenty-Four to rule out theme conflicts
- Disable other plugins one by one to identify conflicts
- Verify your WordPress version is supported (DigiConsent requires WordPress 5.0 or higher)
- Check PHP version meets minimum requirements (typically PHP 7.4 or higher)
- Review error logs for specific error messages
- Test on different devices and browsers to see if the issue is device-specific
- Verify your license key is valid and activated if using the Pro version
By following this methodical approach, you can isolate the cause of most issues. Each step either resolves the problem or provides valuable information about what’s causing it. If you make it through the entire checklist without resolving the issue, you’ll have excellent diagnostic information to provide when contacting support, which will help them assist you much more quickly.
Preventing Future Issues
Many common issues can be prevented with good practices. Always test plugins in a staging environment before updating on your live site. Keep WordPress, your theme, and all plugins updated to their latest versions, as updates often include compatibility fixes. When adding new plugins, test them with DigiConsent to ensure they don’t conflict.
Maintain good documentation of your configuration. Take screenshots of your DigiConsent settings so you can quickly restore them if needed. Regularly backup your database so you can roll back if an update causes problems. Choose quality hosting that provides adequate resources for your WordPress site, as many issues stem from insufficient server resources.
Understanding these common issues and their solutions empowers you to maintain a smoothly functioning cookie consent system. Most problems have simple solutions, and with the knowledge in this guide, you can troubleshoot effectively and keep your site compliant without frustration.