Overview
KineticHub registers its blocks when WordPress initializes the plugin.
When a KineticHub block is missing from the editor, the most common causes are:
- KineticHub is inactive
- The individual block is disabled
- The editor was already open when the setting changed
- The installed plugin package is incomplete
- A user-role or allowed-blocks plugin is restricting the inserter
- A JavaScript error prevents the block editor from loading correctly
- A theme or plugin conflict affects block registration
- Cached editor assets are outdated
Do not immediately reinstall WordPress or delete existing blocks from pages.
Start with the checks below.
Confirm that KineticHub is active
Go to:
Plugins → Installed Plugins
Locate KineticHub and confirm that it is active.
Depending on the installed edition, you may see:
- KineticHub – Animated Blocks
- KineticHub PRO
When using KineticHub PRO, confirm that the premium package itself is active.
The license controls access to premium features and updates, but the plugin package must also be active for its blocks to be registered.
Do not keep both editions active
KineticHub PRO is the complete premium package.
Do not keep KineticHub Free and KineticHub PRO active at the same time.
When upgrading from Free to PRO:
- Deactivate KineticHub Free
- Install KineticHub PRO
- Activate KineticHub PRO
- Activate the license
- Reload the WordPress editor
- Confirm that the blocks are available
After confirming that PRO works correctly, the inactive Free package can be removed.
Search for the block correctly
Open a page or post in the WordPress block editor.
Select the block inserter and search for:
Kinetic
You can also browse the:
Kinetic Suite
block category.
KineticHub includes the following block types:
- Kinetic Ambient Aura
- Kinetic Audio Player
- Kinetic Before/After
- Kinetic Box
- Kinetic Cursor Reveal
- Kinetic Hero Mesh
- Kinetic Magnetic Button
- Kinetic Marquee
- Kinetic Scroll Divider
- Kinetic Split Scroll
- Kinetic Typography
- Kinetic Video Modal
Search using part of the name when the complete title does not return a result.
For example:
audiobeforemeshmagneticmarqueetypographyvideo
Check the individual block setting
KineticHub allows administrators to enable or disable each block separately.
Open:
KineticHub
Locate the missing block in the block manager.
Confirm that its control is enabled.
Then:
- Save the KineticHub settings
- Wait for the save confirmation
- Close or reload the editor
- Open the block inserter
- Search for the block again
When a block is explicitly disabled, KineticHub does not register that block type.
Reload the complete editor
An editor tab that was already open may continue using the block registrations loaded when the page was first opened.
After enabling a block:
- Save any unsaved page changes
- Reload the complete browser tab
- Reopen the block inserter
- Search for Kinetic
Closing and reopening the inserter alone may not be sufficient.
You can also open a new page in a separate browser tab to confirm whether the block is available there.
Check your WordPress user role
KineticHub dashboard settings require administrator permissions.
A non-administrator may be able to use enabled blocks but may not be able to change the global block manager.
Confirm whether the current account is:
- Administrator
- Editor
- Author
- Contributor
- A custom user role
A user-role or membership plugin may restrict which blocks are available to specific users.
Test the editor using an administrator account.
If the block appears for the administrator but not for another user, inspect the role or allowed-block configuration.
Check allowed-block restrictions
WordPress themes and plugins can restrict the list of blocks available in the inserter.
This may be implemented through:
- User-role plugins
- Editorial workflow plugins
- Membership plugins
- Page-builder compatibility settings
- Custom theme code
- Site-specific plugins
- The WordPress
allowed_block_types_allfilter
When all KineticHub blocks are missing but the plugin is active, check whether another system limits the permitted block types.
Temporarily test the editor without the restriction on a staging website.
Do not remove the restriction permanently until you understand why it exists.
Check the editing context
Some templates, widgets, navigation areas, and specialized editing screens allow only certain block types.
Test the missing block inside a normal WordPress page:
Pages → Add New Page
If the block appears on a normal page but not in another editing area, that context may restrict the blocks that can be inserted.
Examples can include:
- Navigation editing
- Template-locked regions
- Synced patterns with restrictions
- Specialized plugin content areas
- Inner block areas with an allowed-block list
The parent block may control which child blocks can be added.
Parent blocks can restrict child blocks
Some container blocks define a specific list of allowed inner blocks.
When a KineticHub block is visible in the main page inserter but not inside a particular container, the parent container may not permit it.
Test by:
- Selecting an empty area outside the parent block
- Opening the main block inserter
- Searching for the KineticHub block
- Inserting it at the top level
If it appears at the top level, KineticHub is registered correctly.
The limitation belongs to the selected parent or inner-block area.
Check whether all KineticHub blocks are missing
Determine whether the problem affects:
- One KineticHub block
- Several KineticHub blocks
- All KineticHub blocks
- All third-party blocks
Only one KineticHub block is missing
The individual block may be disabled, missing from the installed package, or restricted by the current parent block.
All KineticHub blocks are missing
Check:
- Plugin activation
- Editor reload
- Block manager settings
- User-role restrictions
- JavaScript errors
- Plugin file integrity
All third-party blocks are missing
The site may be using an allowed-block restriction or an editor compatibility setting unrelated specifically to KineticHub.
Check the KineticHub dashboard save request
When a block remains disabled after saving, the dashboard request may not have completed successfully.
Possible causes include:
- An expired WordPress login session
- An invalid REST nonce
- A security plugin blocking the REST API
- A firewall rule
- A server error
- A JavaScript error in the dashboard
- Insufficient administrator permissions
Reload the WordPress administration area and save again.
If the setting still does not save, open the browser developer tools and inspect the Console and Network panels.
Look for a failed request to the KineticHub settings endpoint.
Clear editor and browser caches
The WordPress editor may continue using older JavaScript or cached settings after a plugin update.
Clear:
- Browser cache
- WordPress object cache
- Server cache
- CDN cache
- Generated JavaScript cache
- Optimization-plugin cache
Then open the editor in a private browser window.
Normal frontend page cache usually does not control the block inserter, but object caching and optimized administration assets can affect the editor.
Check after a plugin update
When the block disappeared after updating KineticHub:
- Confirm that the update completed
- Check the installed plugin version
- Reload the WordPress administration area
- Clear generated JavaScript and object caches
- Open a new editor screen
- Confirm that the block remains enabled
- Check for WordPress or PHP errors
An interrupted update can leave the plugin package incomplete.
Do not repeatedly update or reinstall without first creating a backup.
Check the installed plugin package
KineticHub registers a block only when the corresponding block directory and its block.json file are present.
An incomplete plugin upload, failed update, or manually modified installation may leave one block missing.
For technical inspection, check the installed plugin directory under:
/wp-content/plugins/
The KineticHub build should contain a block directory for every included block under a path similar to:
build/blocks/
Each registered block directory should contain its required block.json file and generated assets.
Do not edit these files directly on a production website.
When files are missing, reinstall a clean official KineticHub package.
Reinstall KineticHub safely
Reinstall only after confirming that the plugin package may be incomplete.
Before reinstalling:
- Create a complete backup
- Record the installed KineticHub version
- Confirm whether the site uses Free or PRO
- Save any unsaved page changes
- Download the correct official package
For KineticHub Free, install the package from the official WordPress plugin directory.
For KineticHub PRO, download the latest package from the Freemius Customer Portal.
Replacing the plugin files should not remove KineticHub blocks stored inside pages, but always keep a backup.
Check for editor JavaScript errors
A JavaScript error can interrupt Gutenberg before all blocks are displayed correctly.
Open the browser developer tools and check the Console.
Look for:
- Red error messages
- Failed script requests
- Errors mentioning KineticHub
- Errors from another plugin
- React or Gutenberg errors
- Block registration warnings
- Duplicate block registration errors
The first error in the console may be more important than later errors caused by it.
Copy the complete error message before changing plugins or settings.
Test for a plugin conflict
Perform conflict testing on a staging website when possible.
Use this process:
- Create a backup
- Confirm the missing block problem
- Deactivate nonessential plugins
- Keep KineticHub active
- Reload the editor
- Search for the block
- Reactivate the other plugins one at a time
- Test after each activation
When the block disappears after one plugin is reactivated, inspect that plugin’s:
- Allowed-block settings
- User-role restrictions
- Gutenberg modifications
- JavaScript errors
- Optimization features
Do not run uncontrolled conflict testing on a busy live website.
Test for a theme conflict
Temporarily switch to a default WordPress theme on staging.
Then open a normal page and search for the KineticHub block.
A theme can affect the editor through:
- Allowed block filters
- Editor scripts
- Editor styles
- Custom block categories
- Template locking
- JavaScript errors
When the block appears with the default theme, the active theme or child theme requires further inspection.
Free and PRO controls versus missing blocks
A block can be present while some premium controls remain unavailable.
These are separate issues.
Block missing entirely
Check registration, block manager settings, plugin activation, files, and editor conflicts.
Block present but PRO settings missing
Check:
- KineticHub PRO is installed
- The premium package is active
- The license is active
- The site is connected to the correct license
- KineticHub Free is not active at the same time
- The editor was reloaded
Do not reinstall the block because a premium setting is missing.
Do not remove existing unavailable blocks
When opening an older page, WordPress may report:
- This block contains unexpected or invalid content
- Your site does not include support for this block
- Block unavailable
- Attempt Block Recovery
- Convert to HTML
- Remove Block
Do not remove, convert, or recover the block until KineticHub has been enabled and registered again.
The saved block content may still be intact.
First:
- Confirm that KineticHub is active
- Enable the block
- Reload the editor
- Clear caches
- Verify the installed version
Only investigate block recovery after registration has been restored.
Recommended troubleshooting sequence
Use this order:
- Confirm KineticHub is active
- Confirm the individual block is enabled
- Save the KineticHub dashboard settings
- Reload the complete editor
- Search for Kinetic
- Test on a normal new page
- Test outside the current parent block
- Test with an administrator account
- Check allowed-block restrictions
- Clear editor and object caches
- Check browser console errors
- Verify plugin files
- Test plugin conflicts on staging
- Test the active theme on staging
- Reinstall a clean official package when necessary
This order begins with the safest and most common causes.
Troubleshooting
One block is missing, but the others are available
Open the KineticHub dashboard and confirm that the specific block is enabled.
Then check whether its build directory and block.json exist in the installed package.
Also test outside the current parent block.
All KineticHub blocks are missing
Confirm that the complete KineticHub plugin is active.
Reload the editor and test using an administrator account.
Check for allowed-block restrictions and JavaScript errors.
The block appears on a new page but not inside a container
The parent block or inner-block area likely restricts allowed child blocks.
Insert the KineticHub block outside that container or use a compatible parent layout.
The block returns after reloading the editor
The editor was using an older registration state.
No further action is required unless the problem repeats after every login or page load.
The block toggle does not stay enabled
The KineticHub dashboard setting may not be saving.
Check administrator permissions, REST API requests, security plugins, and expired login sessions.
The block appears for administrators but not editors
A role-based block restriction is likely active.
Inspect the user-role, membership, editorial, or allowed-block configuration.
The block disappeared after an update
Clear editor caches and verify that the update completed successfully.
Check the installed plugin files and reinstall the official package when the build is incomplete.
WordPress reports an unsupported block on an existing page
Re-enable the affected block and reload the editor.
Do not remove or convert the saved block before restoring its registration.
The block is available, but its preview is blank
The block is registered, so this is not a missing-block issue.
Check frontend scripts, editor-preview compatibility, block dimensions, media settings, and browser errors.
Search does not return the full block title
Search for Kinetic or a shorter term and review the Kinetic Suite category.
Information to collect for support
Before contacting KineticHub support, collect:
- KineticHub version
- Free or PRO edition
- Missing block name
- Screenshot of the KineticHub block manager
- Screenshot of the block inserter
- WordPress version
- PHP version
- Active theme
- Current user role
- List of editor or allowed-block plugins
- Browser console errors
- Whether the block appears on a new page
- Whether the block appears outside the parent container
- Whether the issue continues with a default theme on staging
Do not include passwords, private access credentials, or complete license keys.
Next step
Continue with A Block Is Not Visible on the Frontend when the block is available inside Gutenberg but does not appear on the published page.