Kadence Blocks adds a collection of powerful blocks to the Gutenberg editor, including advanced galleries, accordions, tabs, and forms. After installing and activating the plugin, the blocks should appear in the block inserter under the Kadence category. However, sometimes the blocks do not show up at all, and the Kadence category is completely missing from the block inserter panel, leaving only the default WordPress blocks available for use.
This problem can be incredibly frustrating because the plugin appears to be activated, and there are no error messages to explain why the blocks are missing. The settings page may be accessible, but the blocks themselves refuse to appear in the editor. The most common cause of this issue is a JavaScript conflict with another plugin or theme that prevents Kadence Blocks from registering properly with Gutenberg.
Another common cause is that the Gutenberg editor is loading in compatibility mode, or the WordPress REST API is not accessible. Kadence Blocks uses the REST API to register blocks and fetch settings, so any restriction on API access will break block registration. Caching plugins that serve old versions of JavaScript files can also cause blocks to disappear after updates.
Why Kadence Blocks are missing from the Gutenberg editor
Kadence Blocks registers its blocks using JavaScript during the Gutenberg editor initialization process. When the editor loads, it requests block definitions from the server via the REST API, and Kadence Blocks responds with information about which blocks are available. If any JavaScript error occurs during this process, the block registration fails, and the blocks never appear in the inserter. Plugin conflicts are the most common source of JavaScript errors, especially when multiple block plugins try to register blocks at the same time.
The WordPress REST API must be fully accessible for Kadence Blocks to function correctly. Some security plugins block REST API access for non-authenticated users, which can interfere with block registration. Additionally, if the REST API has been disabled through filters or hosting configuration, Kadence Blocks cannot communicate with the server to register its blocks. Checking REST API accessibility is an important diagnostic step when blocks are missing.
Caching plugins can also cause blocks to disappear, especially after updating Kadence Blocks or WordPress. When JavaScript files are cached, the editor may load old versions of the block registration scripts that are incompatible with the current version of the plugin. Clearing all caches usually resolves this issue, but sometimes the CDN or server cache needs to be purged as well.
How to check if Kadence Blocks are properly registered
Open the Gutenberg editor on any page or post and open the browser developer tools by pressing F12. Navigate to the Console tab and look for JavaScript errors that mention Kadence or Kadence Blocks. Red error messages like “kadenceBlocks is not defined” or “Cannot read property of undefined” indicate that the block registration script failed to load or execute properly. Also, check the Network tab for requests to wp-json/kadence or similar endpoints to verify that the REST API is returning block data.
Step by step guide to fixing missing Kadence Blocks
Follow these steps in order to restore Kadence Blocks in the Gutenberg editor. Start with the simplest solutions before moving to more advanced troubleshooting steps.
- Clear all caches including plugin cache, CDN cache, and browser cache completely
- Deactivate all plugins except Kadence Blocks and Kadence theme to test for conflicts
- Switch to a default WordPress theme like Twenty Twenty-Four for testing purposes
- Check that the WordPress REST API is accessible by visiting /wp-json/ on your domain
- Disable all security plugins temporarily to test if they block REST API access
- Regenerate Kadence Blocks assets from the Kadence settings panel if available
- Update Kadence Blocks to the latest version available from the WordPress repository
- Update WordPress to the latest version and ensure PHP version is 7.4 or higher
- Check that the site URL and WordPress address settings match in general settings
- Contact Kadence Blocks support with specific details about the missing blocks
How to test for plugin conflicts with Kadence Blocks
Go to the WordPress admin dashboard and navigate to Plugins → Installed Plugins. Deactivate all plugins except Kadence Blocks and Kadence theme (or any default WordPress theme). Open the Gutenberg editor on a test page and check whether the Kadence Blocks appear in the block inserter. If the blocks appear, re-activate the other plugins one by one, testing the editor after each activation. When the blocks disappear again, the last activated plugin is causing the conflict. Keep that plugin deactivated or contact its developer for a compatibility fix.
Kadence Blocks missing troubleshooting reference table
Here is a quick reference table for diagnosing missing Kadence Blocks problems based on specific symptoms you might encounter.
| Symptom | Most likely cause | Recommended solution | Blocks missing in editor, no console errors | REST API blocked or asset caching issue | Check REST API access and clear all caches | Console shows JavaScript errors with Kadence | Plugin or theme conflict | Deactivate plugins one by one to find culprit | Blocks appear sometimes but not always | Caching issue or intermittent REST API problem | Clear caches and check server error logs | Blocks missing only on certain pages | Page-specific corruption or user role restrictions | Check user permissions and recreate the page |
|---|
For more information about Kadence Blocks troubleshooting, visit the Kadence Blocks page on wpwizzy.com.
Preventing Kadence Blocks registration problems in the future
Keep Kadence Blocks and all other plugins updated to their latest versions on a regular weekly schedule. Clear all caches immediately after updating Kadence Blocks or WordPress, and test the Gutenberg editor after each update to catch problems early. Choose a hosting provider that properly supports the WordPress REST API without blocking access, and configure security plugins to allow REST API requests from authenticated users.
Document the working configuration of plugins for quick recovery if problems appear after an update. Use a staging website to test major plugin updates before applying them to the live production site, and regularly check the browser console for JavaScript errors that might indicate emerging issues. Consider using the Kadence Blocks standalone plugin with a lightweight theme for the best compatibility and performance.