The notice Your site doesn’t include support for the “ub/…” block means the WordPress editor could not load that Ultimate Blocks block. Your content is safe. In most cases a reload of the editor fixes it, and if not, the block is turned off in the Ultimate Blocks settings or the plugin that provides it is not active.
The notice looks like this (the block name, such as ub/content-toggle-block, changes with the block):
What you need #
- Access to the WordPress editor and, for some fixes, an administrator account.
How to fix it #
- Do not click Keep as HTML or remove the block yet. Leave it as it is while you try the steps below.
- Reload the editor. Press Ctrl + R (Windows or Linux) or Cmd + R (Mac). This fixes most cases, because the editor sometimes fails to load all block scripts (for example after a network hiccup or when a browser tab is restored).
- Do a hard refresh. Press Ctrl + Shift + R (Windows or Linux) or Cmd + Shift + R (Mac) to load fresh files instead of cached ones.
- Check the block is turned on. Go to Ultimate Blocks > Blocks in your WordPress admin and make sure the toggle for that block is on. A turned-off block shows this exact notice in posts that use it. See how to turn a block back on.
- Check the plugins are active. Go to Plugins > Installed Plugins and make sure Ultimate Blocks is active. For Pro blocks (Timeline, Coupon, Image Hotspots and Summarize with AI), Ultimate Blocks Pro must be active too.
- Update everything. Update WordPress, your theme, Ultimate Blocks and Ultimate Blocks Pro to the latest versions.
Still showing? Check these #
- Try a private window or another browser. This rules out browser extensions and old cached files.
- Turn off optimization for logged-in users. Some caching and optimization plugins, or a CDN, combine or delay JavaScript in the admin area. Turn that off for logged-in users or clear the plugin cache, then reload the editor.
- Look for errors. Open your browser’s developer tools (F12), go to the Console tab and reload the editor. Red errors about blocked or missing files point to a caching, security or migration problem.
- After a site migration, make sure your site address uses https everywhere, so scripts are not blocked as mixed content.
When to contact support #
If the notice comes back on every reload, contact us through Ultimate Blocks > Contact Us and include:
- a screenshot of the notice,
- your WordPress, theme, Ultimate Blocks and Ultimate Blocks Pro versions,
- your browser and operating system,
- any errors from the browser Console.
Frequently asked questions #
Will I lose my content?
No. The block content is still saved in your post. The notice only means the editor could not load the block on this page load.
Should I click Keep as HTML?
Usually no. Keep as HTML turns the block into a Custom HTML block, so you can no longer edit it with the Ultimate Blocks settings. Reload the editor first.
Why does the block work on the live site but not in the editor?
The live page is built on the server, while the editor needs the block scripts to load in your browser. If those scripts fail to load, only the editor shows the notice.
Can this happen to any Ultimate Blocks block?
Yes. It can affect any block, depending on which script did not load or which block is turned off.
Does turning off a block in Ultimate Blocks cause this notice?
Yes. When a block is turned off in Ultimate Blocks > Blocks, posts that already use it show this notice in the editor. Turn the block back on to fix it.
