Enable or Disable Individual Blocks

Overview

KineticHub includes a central block manager that allows administrators to enable or disable individual KineticHub blocks.

This is useful when a website uses only part of the KineticHub collection and you want to keep the WordPress block inserter easier to navigate.

KineticHub currently includes:

• 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

Individual block management is separate from activating or deactivating the complete KineticHub plugin.

Open the block manager

Sign in to the WordPress administration area.

In the left WordPress menu, select:

KineticHub

Open the dashboard section that lists the available KineticHub blocks.

Only users with administrator permissions can save the global KineticHub settings.

Disable an individual block

To disable a block:

1. Open the KineticHub dashboard
2. Locate the block you no longer want available
3. Turn off its block control
4. Save the KineticHub settings
5. Reload any open WordPress editor screen

After the setting is saved, KineticHub no longer registers that block type.

The disabled block should no longer appear when you search for it in the WordPress block inserter.

Enable an individual block

To restore a disabled block:

1. Open the KineticHub dashboard
2. Locate the disabled block
3. Turn its block control back on
4. Save the settings
5. Reload the WordPress editor

The block will be registered again and should return to the block inserter.

When KineticHub has no saved individual block configuration, its supported blocks are enabled by default.

What disabling a block actually does

Disabling an individual block prevents KineticHub from registering that block type during WordPress initialization.

It does not:

• Uninstall KineticHub
• Delete the complete plugin
• Remove the block files from the server
• Delete the page or post containing the block
• Delete the saved block attributes from WordPress content
• Deactivate the KineticHub license
• Disable every other KineticHub block

The setting affects only the selected block type.

Existing pages using a disabled block

Check whether a block is already used before disabling it.

When an existing page contains a block that is no longer registered, WordPress may treat it as missing or unsupported in the editor.

Depending on how that block stores and renders its output, the frontend may:

• Stop rendering the block
• Display incomplete content
• Lose its interactive behavior
• Lose block-specific styling
• Continue showing only previously saved static markup
• Look different from the editor

Do not assume that disabling a block is safe only because the page itself remains published.

Review every important page that uses the block.

Restore an unavailable block

When WordPress reports that a KineticHub block is unavailable:

1. Do not remove the block from the page
2. Do not convert it to HTML
3. Do not attempt block recovery immediately
4. Open the KineticHub dashboard
5. Enable the affected block
6. Save the settings
7. Reload the editor
8. Check the frontend page

If the original block data is still present, registering the block again should allow WordPress to recognize it.

Removing or converting the unavailable block may permanently change its saved content.

Check whether a block is already in use

KineticHub does not currently provide a complete site-wide usage report showing every page that contains each block.

Before disabling a block, manually review likely locations such as:

• Pages
• Posts
• Landing pages
• Templates
• Template parts
• Synced patterns
• Reusable layouts
• Headers
• Footers
• Client or product pages

Also check pages where the block may be nested inside:

• Group blocks
• Columns
• Cover blocks
• Kinetic Box
• Hero sections
• Split Scroll content
• Patterns

On a large production website, test the change on staging first.

Recommended use

Disable blocks that:

• Are not used anywhere on the website
• Are not planned for upcoming pages
• Make the inserter unnecessarily crowded
• Should not be available to content editors
• Are being temporarily removed during controlled testing

Keep a block enabled when:

• It is used on a published page
• It appears inside a template or pattern
• You are unsure whether it is still in use
• Another administrator or editor may need it
• It is currently being tested
• The site is being migrated or redesigned

When uncertain, leaving the block enabled is safer.

Block manager and website performance

Disabling an unused block prevents that block type from being registered.

This can also prevent WordPress from registering and using assets that are specifically attached to that block definition.

However, disabling one block does not deactivate KineticHub’s complete shared system.

The plugin may still register or load shared resources used by the remaining KineticHub blocks, including:

• Shared motion behavior
• Shared animation styles
• Global CSS variables
• Dashboard settings

Use the block manager primarily to control availability and organization.

Do not treat it as a guarantee that every shared KineticHub resource will disappear from the frontend.

Block-specific assets

KineticHub blocks register their own metadata, styles, scripts, and server-side rendering where required.

When a block is disabled, its block definition is not registered.

As a result, its block-specific rendering and interactive files may no longer be available to pages containing that block.

This is why disabling an already-used block can affect both the editor and the public page.

Free and PRO behavior

The block manager controls the available KineticHub block types.

KineticHub PRO uses the same main block collection and adds premium controls and effects to supported blocks.

Disabling a block prevents access to that complete block type, not only to its Free or PRO settings.

For example, disabling Kinetic Typography removes the Kinetic Typography block registration rather than hiding only its premium controls.

Disabling a block for testing

The block manager can help during troubleshooting.

For example, you may temporarily disable a block when testing:

• An editor conflict
• A theme compatibility issue
• An optimization conflict
• A frontend JavaScript problem
• An issue caused by several animated sections

Use this process:

1. Create a backup or use staging
2. Confirm which pages use the block
3. Disable only one block
4. Save the settings
5. Clear relevant caches
6. Test the affected page
7. Re-enable the block after testing
8. Confirm that the page returns to normal

Do not disable several blocks simultaneously when trying to identify one problem.

Changes inside an open editor

An editor tab that was already open may still contain old block registration data.

After enabling or disabling a block:

1. Save any unsaved page changes
2. Close or reload the editor
3. Open the block inserter again
4. Search for the block

A simple sidebar refresh may not be sufficient.

Cache considerations

The block manager setting is stored in WordPress, but cached editor or frontend resources may continue showing old behavior temporarily.

After changing block availability, clear relevant caches when necessary:

• Browser cache
• WordPress page cache
• Object cache
• Server cache
• CDN cache
• Generated CSS or JavaScript cache

Then test in a private browser window.

The block inserter itself normally requires an editor reload after the setting changes.

Recommended workflow before disabling a block

Use this checklist:

1. Confirm that the block is not used on published pages
2. Check templates, template parts, and patterns
3. Create a current backup
4. Test on staging when the website is important
5. Disable only the intended block
6. Save the KineticHub settings
7. Reload the editor
8. Check the block inserter
9. Review important frontend pages
10. Keep a note of which blocks were intentionally disabled

This prevents another administrator from mistaking the missing block for a plugin error.

Troubleshooting

The block still appears in the inserter

Save the KineticHub settings again.

Then completely reload the WordPress editor.

Also check whether:

• Another editor tab was already open
• Browser cache is serving an older editor state
• The setting request failed
• A security plugin blocked the WordPress REST API request
• Another plugin registers a block with a similar name

Open a new page and search again.

The block is missing unexpectedly

Open:

KineticHub

Confirm that the block is enabled.

Save the settings even when the toggle already appears enabled, then reload the editor.

Also verify that the KineticHub plugin itself is active under:

Plugins → Installed Plugins

The dashboard settings do not save

Confirm that you are signed in as a WordPress administrator.

The KineticHub settings endpoint requires administrator permissions and a valid WordPress REST nonce.

A firewall, security plugin, expired login session, or blocked REST request may prevent saving.

Reload the WordPress dashboard and try again.

WordPress shows an unsupported or missing block

Do not delete or convert the block.

Re-enable its KineticHub block type, save the settings, and reload the editor.

If the block remains unavailable, confirm that the installed KineticHub version still contains that block.

The block returns to the editor but not the frontend

Clear page, browser, generated asset, server, and CDN caches.

Also confirm that:

• The block remains enabled
• KineticHub is active
• The page was updated correctly
• An optimization plugin is not removing its script or style
• No browser console error prevents initialization

Existing content disappeared after disabling a block

Re-enable the block immediately and reload the page.

The saved WordPress content may still contain its original block attributes even when the frontend output is unavailable.

Avoid editing or resaving the affected page while the block remains unregistered.

The block is enabled but cannot be found by its full title

Search the inserter for:

Kinetic

Then review the KineticHub block category.

Also confirm that another editor setting or user-role plugin is not restricting allowed blocks.

A block was disabled accidentally

Enable it again from the KineticHub dashboard and save the settings.

Reload the editor and verify the affected frontend pages before making further changes.

Information to collect for support

Before contacting KineticHub support, collect:

• KineticHub version
• Free or PRO version
• Name of the missing block
• Whether the block is enabled in the dashboard
• WordPress version
• Active theme
• User role
• Screenshot of the block manager
• Screenshot of the editor message
• Browser console errors
• Whether the block returns after re-enabling it

Do not include passwords or complete license keys.

Next step

Continue with Performance Modes and Asset Loading to configure KineticHub’s shared motion and stylesheet behavior.