Before installing DigiConsent on your WordPress website, it’s important to ensure your hosting environment meets the necessary requirements. This comprehensive guide covers all technical requirements, compatibility information, and optimization recommendations to ensure DigiConsent runs smoothly and efficiently.
Minimum System Requirements
DigiConsent is designed to work on standard WordPress hosting environments. Here are the minimum requirements for running the plugin:
WordPress Version
Minimum: WordPress 5.8 or higher
Recommended: WordPress 6.4 or higher
Tested up to: WordPress 6.8
DigiConsent requires WordPress 5.8 as a minimum because it uses modern WordPress APIs and features introduced in that version. However, for the best experience, security, and compatibility, we strongly recommend keeping WordPress updated to the latest stable version. DigiConsent is actively tested with each new WordPress release to ensure compatibility.
PHP Version
Minimum: PHP 7.4
Recommended: PHP 8.0 or higher
Optimal: PHP 8.1 or PHP 8.2
DigiConsent requires PHP 7.4 as an absolute minimum, but this version reached end-of-life in November 2022 and no longer receives security updates. We strongly recommend using PHP 8.0 or higher for several important reasons:
- Security: PHP 8.0+ receives active security patches and updates
- Performance: PHP 8.0+ includes significant performance improvements, making your website faster
- Compatibility: WordPress itself recommends PHP 7.4 or higher, with PHP 8.0+ being optimal
- Future-proofing: Upcoming versions of DigiConsent may drop support for older PHP versions
Most modern hosting providers offer PHP 8.0, 8.1, or 8.2 as standard options. You can typically change your PHP version through your hosting control panel (cPanel, Plesk, etc.) or by contacting your host’s support team.
MySQL/MariaDB Version
MySQL Minimum: 5.6 or higher
MySQL Recommended: 8.0 or higher
MariaDB Minimum: 10.1 or higher
MariaDB Recommended: 10.6 or higher
DigiConsent creates custom database tables to store consent logs and analytics data. These tables use standard SQL features available in MySQL 5.6+ or MariaDB 10.1+. Modern database versions provide better performance, security, and reliability. Most hosting providers have upgraded to newer versions, but if you’re on an older database version, contact your host about upgrading.
Server Requirements
DigiConsent works on all standard web servers that support WordPress:
- Apache: Version 2.4 or higher (most common)
- Nginx: Version 1.18 or higher (increasingly popular)
- LiteSpeed: Any modern version
- Microsoft IIS: Version 10 or higher (less common for WordPress)
The plugin requires write permissions to the WordPress plugins directory during installation and to the database for storing consent logs. These are standard permissions available on all WordPress-compatible hosting.
Recommended Server Configuration
While DigiConsent will function on minimum requirements, these recommended settings ensure optimal performance:
PHP Configuration
Recommended PHP settings for DigiConsent:
- memory_limit: 256M or higher (WordPress default is 64M, but 128M-256M is better)
- max_execution_time: 300 seconds (5 minutes) or higher
- post_max_size: 64M or higher
- upload_max_filesize: 64M or higher
- max_input_vars: 3000 or higher (important for saving settings with many fields)
These settings are particularly important if you’re managing many cookie categories or importing/exporting large configurations. Most quality hosting providers set these values appropriately by default.
Required PHP Extensions
DigiConsent requires these PHP extensions, which are typically enabled by default on WordPress hosting:
- mysqli or pdo_mysql: For database connectivity
- json: For handling JSON data (consent preferences, analytics)
- mbstring: For proper string handling in multiple languages
- openssl: For secure connections and data handling
These extensions are part of standard PHP installations and are required by WordPress itself, so they should already be available on any WordPress-compatible hosting.
Browser Requirements for Admin Panel
The DigiConsent admin interface works in all modern browsers. For the best experience managing your consent settings, use:
- Google Chrome: Version 90 or higher
- Mozilla Firefox: Version 88 or higher
- Safari: Version 14 or higher
- Microsoft Edge: Version 90 or higher (Chromium-based)
The admin interface uses modern JavaScript and CSS features for the best user experience. While older browsers may work, you might experience degraded functionality or visual issues.
Browser Requirements for Frontend Banner
The cookie consent banner displayed to your website visitors is designed to work on virtually all browsers, including older versions:
- Chrome/Edge: Last 3 major versions
- Firefox: Last 3 major versions
- Safari: Last 2 major versions (iOS and macOS)
- Mobile Browsers: All modern mobile browsers on iOS and Android
- Internet Explorer: IE 11 (basic functionality only)
The banner uses progressive enhancement, meaning it works on older browsers but provides enhanced features and smoother animations on modern browsers. JavaScript is required for the banner to function, but this is standard for any interactive website element.
WordPress Theme Compatibility
DigiConsent is designed to work with all properly coded WordPress themes. The plugin integrates with WordPress through standard hooks and requires only one thing from your theme:
Required Theme Function
Your theme must include the wp_footer() function call in its footer template. This is a WordPress requirement that all valid themes must meet. DigiConsent uses this hook to insert the consent banner into your website.
To verify your theme includes this function, check your theme’s footer.php file for <?php wp_footer(); ?> just before the closing </body> tag.
Tested Theme Compatibility
DigiConsent has been tested and confirmed to work with:
- All default WordPress themes (Twenty Twenty-One, Twenty Twenty-Two, Twenty Twenty-Three, etc.)
- Popular commercial themes from ThemeForest, Elegant Themes, StudioPress
- Popular free themes from the WordPress.org repository
- Block-based themes using the WordPress Site Editor
- Classic themes using traditional PHP templates
Page Builder Compatibility
DigiConsent works seamlessly with all major WordPress page builders because it operates independently of page content:
- Elementor: Full compatibility with Elementor Free and Pro
- Divi Builder: Works with both Divi theme and Divi Builder plugin
- Beaver Builder: Compatible with all versions
- WPBakery: Full compatibility
- Gutenberg: Native WordPress block editor support
- Oxygen Builder: Compatible with Oxygen’s framework
- Bricks Builder: Works with Bricks’ modern architecture
The consent banner appears above all page builder content and doesn’t interfere with builder functionality or editing capabilities.
Plugin Compatibility
DigiConsent is designed to work alongside other WordPress plugins. Here’s what you need to know about plugin compatibility:
Caching Plugins
DigiConsent is fully compatible with popular caching plugins:
- WP Rocket: Automatically excludes DigiConsent’s JavaScript from minification and delay settings
- W3 Total Cache: Works correctly with all caching modes
- WP Super Cache: Compatible with all caching configurations
- LiteSpeed Cache: Works with LiteSpeed’s caching system
- Autoptimize: Compatible with script optimization
Important: After changing DigiConsent settings, always clear your cache to ensure visitors see the updated banner. DigiConsent’s consent banner must load on every page view to function correctly, so it’s excluded from aggressive caching by default.
SEO Plugins
DigiConsent works perfectly with all major SEO plugins:
- Yoast SEO
- Rank Math
- All in One SEO (AIOSEO)
- SEOPress
- The SEO Framework
The consent banner doesn’t affect SEO because search engines don’t interact with cookie consent dialogs. Your content remains fully accessible to search engine crawlers.
Security Plugins
DigiConsent is compatible with security plugins including:
- Wordfence Security
- Sucuri Security
- iThemes Security
- All In One WP Security & Firewall
DigiConsent follows WordPress security best practices and doesn’t conflict with security plugin functionality.
Analytics and Tracking Plugins
DigiConsent can manage cookies for analytics plugins, but you should understand how they work together:
- MonsterInsights: Instead of letting MonsterInsights add Google Analytics directly, disable its frontend tracking and add your GA code to DigiConsent’s Analytics category
- Google Analytics plugins: Similarly, disable automatic tracking and manage analytics through DigiConsent for proper consent management
- Google Tag Manager plugins: Use DigiConsent’s built-in GTM integration rather than a separate plugin
The key principle: Only one system should load your tracking scripts. Use DigiConsent to manage all tracking for proper consent control.
E-commerce Plugins
DigiConsent works excellently with e-commerce platforms:
- WooCommerce: Full compatibility. WooCommerce’s essential cookies work normally while marketing/analytics cookies respect consent
- Easy Digital Downloads: Compatible with all versions
- MemberPress: Works correctly with membership functionality
- WP Simple Pay: Payment forms function normally
Essential e-commerce functionality (cart, checkout, sessions) should be managed through the Necessary category, while analytics and marketing pixels go in their respective categories.
Multisite Compatibility
DigiConsent fully supports WordPress Multisite installations:
- Network Activation: Can be activated network-wide for all sites
- Individual Activation: Or activated on specific sites within the network
- Independent Settings: Each site maintains its own DigiConsent configuration
- Separate Data: Consent logs and analytics are stored per-site, not network-wide
This allows each site in your network to customize cookie consent according to its specific needs and audience.
CDN and Hosting Compatibility
DigiConsent works with all major hosting providers and CDN services:
Managed WordPress Hosting
Tested and confirmed working with:
- WP Engine
- Kinsta
- Flywheel
- Pressable
- Pagely
- SiteGround WordPress Hosting
- Bluehost WordPress Hosting
CDN Services
Compatible with all major CDN providers:
- Cloudflare (including APO – Automatic Platform Optimization)
- StackPath
- KeyCDN
- BunnyCDN
- Amazon CloudFront
Note: When using a CDN, ensure DigiConsent’s JavaScript files are not cached too aggressively, or clear the CDN cache after making configuration changes.
HTTPS/SSL Requirements
While DigiConsent technically works on both HTTP and HTTPS sites, HTTPS is strongly recommended for several important reasons:
- Privacy Compliance: GDPR and other privacy regulations expect secure data transmission
- Cookie Security: Consent cookies should be transmitted securely
- Browser Requirements: Modern browsers restrict cookie functionality on non-HTTPS sites
- User Trust: Security warnings on HTTP sites undermine consent banner credibility
- SEO Benefits: Google prioritizes HTTPS sites in search results
Most hosting providers offer free SSL certificates through Let’s Encrypt. If your site doesn’t have HTTPS, contact your host about enabling it before implementing cookie consent.
Performance Considerations
DigiConsent is optimized for performance and has minimal impact on your website:
- JavaScript Size: Approximately 15-20KB minified and gzipped
- CSS Size: Approximately 5-8KB minified and gzipped
- Database Impact: Optimized queries with proper indexing for consent logs
- Page Load Impact: Less than 50ms on properly configured hosting
- Asset Loading: Scripts load asynchronously without blocking page rendering
The banner is lightweight and loads after your page content, ensuring it doesn’t slow down your website’s perceived performance.
Checking Your Current Environment
To check if your WordPress installation meets DigiConsent’s requirements:
- Go to Tools → Site Health in your WordPress admin
- Click the Info tab
- Review the WordPress, Server, and Database sections
- Verify your PHP version, WordPress version, and database version meet the requirements
If any requirements aren’t met, contact your hosting provider about upgrading. Most quality hosts can make these changes quickly, often through your control panel.
Future Requirements
As WordPress and PHP continue to evolve, DigiConsent’s requirements may change:
- PHP Support: When PHP versions reach end-of-life, DigiConsent may drop support for them in future updates
- WordPress Version: Minimum WordPress version may increase as older versions lose support
- Modern Features: New features may require newer PHP/WordPress versions
We recommend keeping WordPress, PHP, and your hosting environment up-to-date for the best security, performance, and compatibility with DigiConsent and all your other plugins.
By ensuring your WordPress installation meets these system requirements, you’ll have a smooth experience installing and running DigiConsent, with excellent performance and compatibility across all aspects of your website.