You will need to place the remote site behind HTTPS. If this is the case, your web browser is blocking the page. Check if Confluence is on HTTPS and the remote site is on HTTP. Try and disable any ad-blockers you are using.
Unlike Global/Space Stylesheets, Custom HTML only has a global configuration, at Confluence Administration > Look and Feel > Custom HTML. As Confluence Server does not come bundled with an iFrame or HTML macro by default, we need to first create one. (Unlike HTML Macros that allow you to insert the script/stylesheet to just a single page). However, changes to stylesheets have a space-wide or global impact to Confluence, and the stylesheet cannot be confined to just a single page. It can only be modified/inserted by administrators.This helps eliminate the security risk posed by HTML Macros, because: Global Stylesheets and Space Stylesheets allow Confluence administrators or space administrators to insert specific CSS styles into Confluence globally, or within a specific space. So let's review the cons associated with each of these approaches. While these options do work, they are not ideal and in some cases (like the HTML Macro), should be avoided at all costs.
#CONFLUENCE IFRAME HOW TO#
Confluence Community: How to add custom Javascript in Confluence pages.Check out the posts below for more background if you aren't already familiar with the options and process. Let's start by reviewing the conventional methods. Conventional Methods for Modifying Pages via CSS/HTML/Javascript
#CONFLUENCE IFRAME CODE#
User Macros are the most powerful, safest and most configurable option for single-page applications of CSS/Javascript.Īlthough the conventional way of modifying Confluence pages via CSS/HTML/Javascript is usually via HTML Macros, Global Stylesheets, or Custom HTML, this blog will explain why we believe User Macros are the best option. however the bigger problem is security Open HTML/Iframe Macro macro in Confluence and enter the copied Iframe code in textbox Iframe. It was last updated on September 28, 2020.
This blog was first published by Foogie Sim on June 12, 2019.