Submit a Ticket

Loading support form...
Skip to content
  • There are no suggestions because the search field is empty.

Troubleshooting iFrame Embeds That Disappear After Saving

If an iFrame saves in preview but disappears after publishing, the source domain likely needs to be added to the site’s iframe allowlist. Providing the full iframe or src URL allows the correct domain to be approved.

How do HTML and iframe embeds work?

HTML and iFrame embeds can be added in a Custom HTML block, and iframe content may appear in preview but be removed when the page is saved if the source domain is not on the site’s approved iframe allowlist. In that case, the iframe is stripped during save, while plain text can still save successfully.

Remember: you can only embed this content within the uConnect Block Editor, powered by WordPress, which can only be found on your front page, custom pages, Community pages, Blogs, and Resources. 

What happens when an iFrame is blocked?

If an iframe is not approved, the editor may show it correctly at first, but after saving the page the iFrame can disappear and the Custom HTML block may be left empty. This behavior is specific to the iframe element.

What should I check if an embed is not saving?

  1. Navigate to the location of the embed code in your uConnect platform admin dashboard.
  2. Confirm whether the embed is being entered as a standard <iframe> tag or as an iframe shortcode format such as [iframe src="..."].
  3. Check whether the iframe appears in preview but disappears after saving.
  4. Compare the behavior with plain text in the same Custom HTML block.
  5. Share the full iFrame or the src URL so the correct domain can be added to the iFrame allowlist.

How is an iFrame embed approved?

The iFrame source domain must be added to the site’s approved iFrame allowlist. Once the correct domain is allowlisted, the same embed code can save and display normally without changes to the code itself.

What information is needed to allowlist an iFrame?

The full iFrame exactly as generated, or at minimum the src="..." URL, is needed so the correct source domain can be identified and approved. Power BI, for example, can use different hosts depending on how the report is published.