Back to Community
Home / Community / Plugin → Gutenberg blocks with ai by kadence wp – page builder features

Troubleshooting Common Kadence Blocks Plugin Conflicts and Errors

47 threads Sep 10, 2025 Plugin → Gutenberg blocks with ai by kadence wp – page builder features

Content

Users of the Gutenberg Blocks with AI by Kadence WP – Page Builder Features plugin occasionally encounter conflicts or errors that prevent blocks from loading, cause performance issues, or break site functionality. This guide compiles the most common issues and their solutions based on community reports.

Common Symptoms

Problems often manifest in a few key ways:

  • Blocks not appearing in the editor, showing a "Your site doesn't include support for..." error.
  • A white rectangle or fatal error in the WordPress editor.
  • Specific browser-related display issues, particularly in Safari or on mobile.
  • High server load or slow page generation times.
  • Conflicts with other plugins like WPML, Ninja Forms, or WooCommerce extensions.

Why These Issues Happen

These problems typically arise from one of three sources:

  1. Plugin or Theme Conflicts: The most common cause. Another plugin or your theme can load scripts or styles that interfere with how Kadence Blocks operates.
  2. Caching Issues: Outdated cached files (CSS, JavaScript) from a previous plugin version can conflict with new code after an update.
  3. Browser-Specific Bugs: Occasionally, CSS or JavaScript may render differently in certain browsers, like older versions of Safari.

Step-by-Step Troubleshooting

1. Perform a Conflict Check

This is the most critical step for diagnosing the root cause.

  1. Switch to a Default Theme: Temporarily activate a standard WordPress theme like Twenty Twenty-One. If the issue resolves, the conflict is with your theme.
  2. Deactivate Other Plugins: Disable all plugins except Kadence Blocks. If the problem is fixed, reactivate your plugins one by one to identify the culprit. Common conflicting plugins mentioned in reports include WPML, Twentig, Ninja Forms, Lazy Blocks, Polylang, and various WooCommerce extensions.

2. Clear All Caches

If blocks break after an update, clear these caches:

  • Browser Cache: Hard refresh your browser (Ctrl+F5 or Cmd+Shift+R).
  • Server Cache: Clear any caching from your hosting dashboard or caching plugin (e.g., WP Rocket, W3 Total Cache).
  • Object Cache: If using Redis or Memcached, flush the object cache.

3. Check the Browser Console for Errors

Technical error messages can pinpoint the exact problem.

  1. Open the page where the error occurs.
  2. Right-click and select Inspect, then go to the Console tab.
  3. Look for red error messages. Phrases like "TypeError," "ReferenceError," or "Block validation failed" are crucial clues. Note these down as they can be used to search for more specific solutions.

4. Address Performance Issues

If the class-kadence-blocks-css.php file is causing high server load, ensure you have a persistent object caching solution (like Redis) properly configured. This can help cache the dynamically generated CSS.

Specific Scenarios and Workarounds

  • Error: "Block validation failed" / Missing CSS class: This often occurs after a plugin update. Try saving the post or page again. If that fails, temporarily switch to a default theme and back to your theme to regenerate styles.
  • Conflict with Twentig Plugin: This is a known compatibility issue. As a temporary workaround, you may need to deactivate one of the plugins until a compatibility update is released.
  • Fatal Error on WPML Page: A conflict with WPML can cause a fatal error on the localization page. The only current workaround is to deactivate Kadence Blocks before accessing that specific WPML admin page, then reactivate it afterward.
  • Issues in Safari: For display bugs specific to Safari, check if the issue is present in other browsers. If it's isolated to Safari, it may require a CSS fix from the Kadence team.

When to Report an Issue

If you have identified a specific conflict through troubleshooting (e.g., the error only occurs when Plugin X and Kadence Blocks are both active), it is helpful to report it. Be prepared to provide:

  • The exact error message from your browser console.
  • The name and version of the conflicting plugin or theme.
  • Steps to reproduce the issue.

By methodically working through these steps, you can usually identify and resolve most conflicts affecting the Kadence Blocks plugin.

Related Support Threads Support