If the Experiments Editor keeps loading and never initializes, your website's Content Security Policy (CSP) may be blocking it. This article explains how to identify a base-uri 'self' conflict and update the CSP so the editor can load.
Check the request and console errors
This issue usually applies when:
The page request with
?exponea-editor-paramsloads successfully and returns200 OKThe browser later requests JavaScript files, such as
polyfillsandmain, from your website's domain instead of the Bloomreach domain.Those requests fail, often with
404errors
You might also see console errors such as:
Setting the document's base URI to 'https://examplepage.com/editor/' violates the following Content Security Policy directive: "base-uri 'self'". The action has been blocked.This article covers CSP-related loading failures. It doesn't cover cases where a redirect removes the exponea-editor-params query parameter.
Understand why the editor fails
A restrictive CSP can prevent the page from setting the editor base URL correctly.
A common example is:
base-uri 'self'When this policy is enforced, the page blocks the Experiments Editor from setting its base URI to the Bloomreach editor URL. Because of that, the browser tries to load the editor assets from the website domain, for example:
https://www.examplepage.com/editor/...Instead of loading them from the Bloomreach editor host, those requests resolve against the wrong host and fail. As a result, the editor can't finish loading.
Solution
Update your website's CSP to add the Bloomreach API domain used by your project to the base-uri directive.
After the CSP is updated, reload the page and reopen the editor.