Plugin conflicts occur when another plugin interferes with DigiFlash’s functionality, causing display issues, broken features, or Site Editor problems. Identifying and resolving these conflicts requires systematic testing.
Identify If a Plugin is Causing Issues
Deactivate all plugins to determine if a plugin conflict exists. Go to Plugins > Installed Plugins, select all plugins using the checkbox at the top, choose “Deactivate” from the bulk actions dropdown, and click Apply.
Check if the issue is resolved with all plugins deactivated. If DigiFlash works correctly, a plugin conflict exists. If the problem persists, the issue isn’t plugin-related.
Systematically Identify the Conflicting Plugin
Reactivate plugins one at a time to pinpoint the specific conflict. After activating each plugin, test if the issue returns. When the problem reappears, you’ve identified the conflicting plugin.
For sites with many plugins, use a binary search method: activate half your plugins, test for the issue, then activate or deactivate half of the remaining plugins based on results. This reduces testing time significantly.
Caching Plugin Conflicts
Caching plugins like WP Super Cache, W3 Total Cache, or WP Rocket can cause DigiFlash to display outdated content or prevent style changes from appearing.
After making changes in DigiFlash, always clear your caching plugin’s cache completely. Configure your caching plugin to exclude the Site Editor and admin pages from caching to prevent editing conflicts.
Disable CSS and JavaScript minification/combination features if you experience broken layouts or missing functionality. These optimization features sometimes break DigiFlash’s styling and scripts.
Security Plugin Conflicts
Security plugins like Wordfence, Sucuri Security, or iThemes Security may block the Site Editor’s AJAX requests or REST API calls required for DigiFlash to function.
Access your security plugin settings and whitelist these WordPress endpoints:
- /wp-json/wp/v2/
- /wp-admin/admin-ajax.php
- All URLs containing /wp-json/
Disable XML-RPC blocking and REST API restrictions in your security plugin settings, as DigiFlash’s Site Editor requires REST API access.
Custom CSS and JavaScript Plugin Conflicts
Plugins like Simple Custom CSS, Insert Headers and Footers, or Custom CSS/JS can override DigiFlash’s styles or cause JavaScript errors.
If using DigiFlash Pro, migrate your custom code to DigiFlash Pro’s Code Editor instead of using separate plugins. This ensures better compatibility and prevents conflicts.
For custom code added by other plugins, verify it doesn’t target the same elements or functions as DigiFlash. Use more specific CSS selectors and wrap JavaScript in proper scope to avoid conflicts.
Performance Optimization Plugin Conflicts
Plugins like Autoptimize, Asset CleanUp, or Perfmatters that control script and style loading can break DigiFlash’s functionality.
Configure these plugins to exclude DigiFlash’s assets from optimization. Add digiflash to the plugin’s exclusion list or disable optimization for theme files entirely.
Disable features that defer or delay JavaScript loading, as these can break the Site Editor and block patterns functionality.
Contact Plugin Developer
If a specific plugin conflicts with DigiFlash and you need both to work together, contact the plugin developer. Provide details about:
- The specific conflict or error
- Your WordPress version
- Your DigiFlash version
- Steps to reproduce the issue
Plugin developers can often provide compatibility fixes or workarounds.
Use Alternative Plugins
If a plugin conflict can’t be resolved, search for alternative plugins with similar functionality that are compatible with block themes. Many plugins now offer block theme-specific versions or compatibility modes.