Getting this message?
The In-Context Editor can sometimes fail to load due to certain browser security restrictions, due to its use of iframes. You may need to adjust your HTTP headers to resolve the issue. MSDN has a great article explaining the problem.
The simplest solution is to install the Localize Editor Chrome extension to bypass the browser security restrictions.
Please note that TLS/SSL connections are required for utilizing the In-Context Editor. "HTTP" only websites will no longer load within the editor due to security restrictions.
This often presents a problem when using the editor with localhost or staging environments. In these cases, you may utilize a SSL certificate to enable "HTTPS" on local or staging environments.
Alternatively, tools such as ngrok may be used to tunnel localhost connections through a public and secured temporary endpoint.
If using a self-signed SSL certificate, you may have to load the webpage outside of the editor to override browser warnings that may be triggered by self-signed certificates.
Updated 4 months ago