# \[Troubleshooting] Why is the editor not loading and how can I force it to open?
If your editor isn’t loading properly, you may encounter one of the following issue:
* [The editor loops and redirects to the login page](#h_01j01960cgw63j3nmga7wqhr0d)
* [Clicking on the editor loads the page from your website without the editor's layout and options](#clicking-on-the-editor-loads-the-page-from-your-website-without-the-editors-layout-and-options)
* [The editor loads its layout and options but the content of the page is not loaded correctly](#the-editor-loads-its-layout-and-options-but-the-content-of-the-page-is-not-loaded-correctly)
## The editor loops and redirects to the login page
In most cases, this behavior means that cookies are probably not enabled in your browser. However, AB Tasty needs them to open the editor and retrieve login details. Without them, we cannot identify you, which is why we redirect you to the login page. This is usually indicated by a crossed-out eye icon in the URL bar:
**How to find out and what to do:**
Go to your Chrome cookies settings (chrome://settings/cookies) and allow the cookies.
You can also add an exception specifically for AB Tasty if necessary using the following format: \[\*.]abtasty.com
## Clicking on the editor loads the page from your website without the editor's layout and options
Switch between tabs to test the different solutions:
{% tabs %}
{% tab title="The tag is not installed/loaded in the page" %}
It happens that the AB Tasty tag is loaded on your page only after the consent is given when landing on the website. If you decline cookies, the generic tag is not executed and the editor can't be loaded correctly.
**How to find out and what to do:**
* Inspect a page on your website (right click in the page -> "Inspect")
* Go to the "Application" tab
* Click the "clear site data" option
* Refresh the page and accept the cookies
* Try to load the editor again
If you still encounter the issue, you should check that the AB Tasty generic tag is installed in your page.
**How to check your tag:**
In your Chrome browser, you can install and use the [***AB Tasty Chrome extension***](https://chromewebstore.google.com/detail/ab-tasty/liaeijonjkogflicmmlcdhckabgmhjdp)***.*** Once installed, the AB Tasty plugin icon appears in your toolbar. If you click the AB Tasty plugin icon from any page of your website, information about whether the tag is installed or not will be displayed.
The tag is installed.
The tag is not installed.
For more information, consult the following article: [***How to check whether AB Tasty’s tag is installed on your website***](https://docs.abtasty.com/help-center/faq/how-to-check-if-the-ab-tasty-tag-is-installed-on-my-website).
If the tag is not present, add it, following our quick start guide : [Set-up your AB Tasty tag in than 5 minutes***.***](https://docs.abtasty.com/help-center/troubleshooting/broken-reference)
As a quick and a short-term workaround, try loading the AB Tasty tag locally in your browser using the AB Tasty Chrome Extension. By injecting your [account identifier](https://app2.abtasty.com/settings/installation-code/tag), you ensure that the visual editor loads the tag properly.
{% endtab %}
{% tab title="Content Security Policy / X-Frames is in cause" %}
If you notice CSP errors in the console when trying to load the editor, the server configuration is causing these problems. The security setting may be too high on your server. By default, many clients use a Content Security Policy that blocks everything on their website. This means that every external request has to be allowlisted in the server configuration.
If you see the following kind of errors, these are caused by CSP errors:
### **How to resolve this issue**
* Short-term solution: use the [Disable Content Security Policy Chrome extension](https://chromewebstore.google.com/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden) to temporarily bypass the CSP rules.
* Long-term solution: ask your IT Team to allow the AB Tasty domains and URLs from your[ Content Security Policy](https://app.gitbook.com/s/dG0EHdNiO40UVA7Bz9mR/tag/troubleshootings/tag-troubleshooting-csp)
### **Other console errors**
You may find other errors in the console that block the editor. For instance, if you notice an error related to **X-Frame Options**, like this:
### **How to resolve this issue**
* Short-term solution: you can temporarily use the [***Ignore X-frame headers***](https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe) extension to bypass this type of error.
* Long-term solution: ask your IT Team to change the server configuration accordingly.
{% endtab %}
{% tab title="A redirection applies" %}
In case a native redirection applies on your side, the editor may have difficulties to load because its parameters in the URL are automatically removed (?abtasty\_editor=XXXXXX). A redirection may happen if:
* The URL you set in the Main Information (1st step of the campaign) actually does not exist and automatically redirects to another page.
* You are trying to load a specific page from your checkout (delivery or payment page) which contains dynamic content and information.
**What to do?**
* Compare the URL you have set in the 1st step and the one you land on. **Edit the URL** in the step accordingly so the visual editor knows the correct URL to load.
* **Apply source code**: the most effective way of loading funnel pages, cart pages with added products, or personalized dashboards. It’s also the best way of fixing editor-loading issues caused by authentication (on a client account, for example) or a page that requires session information (e.g. products to be displayed on the cart page).
There are two ways of applying the correct source code:
**👉**[**With the AB Tasty extension**](https://app.gitbook.com/s/6Yw9IRJ6KbbucQPwZUCZ/web-experimentation-and-personalization/editors-and-widget/chrome-extension#h_01jtk5jwe093g7xemwhascpyrb)
**👉With the OuterHTML**
Copy the source code of the web page where you’re trying to load the editor using the **Copy outerHTML** command in the \ tag (in the first line of the source code).
Paste this source code into the **Sample URL to load in the editor field** in the [**Main information** step](https://app.gitbook.com/s/6Yw9IRJ6KbbucQPwZUCZ/web-experimentation-and-personalization/campaign-creation-and-dashboard/how-to-set-up-main-information-step#id-01j8hdwfg74rcxgjjxgmvnrth6) in AB Tasty:
* **Use the Chrome Extension**: try using the [***AB Tasty Chrome*** ](https://app.gitbook.com/s/6Yw9IRJ6KbbucQPwZUCZ/web-experimentation-and-personalization/editors-and-widget/chrome-extension)***extension.*** This extension forces your page to load fully before applying the editor, which solves a lot of common problems encountered with loading the editor. The add-on is available in the Chrome web store. You can download it [***here***](https://chromewebstore.google.com/detail/ab-tasty/liaeijonjkogflicmmlcdhckabgmhjdp)***.***
To use the Chrome add-on, follow these steps:
1. Go to the URL you want to load in the editor
2. Open the AB Tasty Chrome add-on
3. Search by campaign name or ID
4. Click **Open Editor**
{% endtab %}
{% endtabs %}
## The editor loads its layout and options but the content of the page is not loaded correctly
{% tabs %}
{% tab title="Switch to the Navigation Mode" %}
Depending on how the page is built, the content may take longer to load or may load dynamically. The visual editor is then loaded too fast compared to your content.
The navigation mode can temporarily enable you to interact with the website in order to trigger or to load certain elements that wouldn’t be otherwise visible. To do so :
* Click the pencil button to **Stop editing**
* Navigate on your website
* Click the same button to **Start editing** Your content is now accessible and fixed to let you work on it thanks to the contextual editor.
{% endtab %}
{% tab title="Apply the Source code" %}
Applying source code is the most effective way of loading **funnel pages**, **cart pages with added products,** or **personalized dashboards**. It’s also the best way of fixing editor-loading issues caused by authentication (on a client account, for example) or a page that requires session information (e.g. products to be displayed on the cart page).
There are two ways of applying the correct source code:
**👉**[**With the AB Tasty extension**](https://app.gitbook.com/s/6Yw9IRJ6KbbucQPwZUCZ/web-experimentation-and-personalization/editors-and-widget/chrome-extension#h_01jtk5jwe093g7xemwhascpyrb)
**👉With the OuterHTML**
Copy the source code of the web page where you’re trying to load the editor using the **Copy outerHTML** command in the \ tag (in the first line of the source code).
Paste this source code into the **Sample URL to load in the editor field** in the [**Main information** step](https://app.gitbook.com/s/6Yw9IRJ6KbbucQPwZUCZ/web-experimentation-and-personalization/campaign-creation-and-dashboard/how-to-set-up-main-information-step#id-01j8hdwfg74rcxgjjxgmvnrth6) in AB Tasty:
You can find more details on how to apply the source code our article dedicated to [introducing the Editor](https://app.gitbook.com/s/6Yw9IRJ6KbbucQPwZUCZ/web-experimentation-and-personalization/editors-and-widget/visual-editor/discovering-the-visual-editor).
{% endtab %}
{% tab title="Verify your console errors" %}
If you notice Content Security Policy (CSP) errors in the console when trying to load the editor, the server configuration is causing these problems. The security setting may be too high on your server. By default, many clients use a Content Security Policy that blocks everything on their website. This means that every external request has to be allowlisted in the server configuration.
To open the console, right click in the editor's page, then click "Inspect" and go to the "Console" tab. If you see the following kind of errors, these are caused by CSP errors:
### **How to resolve this issue**
* Short-term solution: use the [Disable Content Security Policy Chrome extension](https://chromewebstore.google.com/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden) to temporarily bypass the CSP rules.
* Long-term solution: ask your IT Team to allow the AB Tasty domains and URLs from your Content Security Policy:
### **Other console errors**
You may find other errors in the console that block the editor. For instance, if you notice an error related to **X-Frame Options**, like this:
### **How to resolve this issue**
* Short-term solution: you can temporarily use the [***Ignore X-frame headers***](https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe) extension to bypass this type of error.
* Long-term solution: ask your IT Team to change the server configuration accordingly.
{% endtab %}
{% endtabs %}
In case you're having issues loading the visual editor, don't forget to first try using our [Chrome Extension](https://chromewebstore.google.com/detail/ab-tasty/liaeijonjkogflicmmlcdhckabgmhjdp?hl=en-US\&utm_source=ext_sidebar). You will find all the information related to [how to open the editor with our extension in this article. ](https://docs.abtasty.com/web-experimentation-and-personalization/editors-and-widget/chrome-extension#h_01jtk5jwe0xdz6fqvx0nhssw3c)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.abtasty.com/help-center/troubleshooting/troubleshooting-why-is-the-editor-not-loading-and-how-can-i-force-it-to-open.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
The tag is installed.
The tag is not installed.
For more information, consult the following article: [***How to check whether AB Tasty’s tag is installed on your website***](https://docs.abtasty.com/help-center/faq/how-to-check-if-the-ab-tasty-tag-is-installed-on-my-website).
If the tag is not present, add it, following our quick start guide : [Set-up your AB Tasty tag in than 5 minutes***.***](https://docs.abtasty.com/help-center/troubleshooting/broken-reference)
As a quick and a short-term workaround, try loading the AB Tasty tag locally in your browser using the AB Tasty Chrome Extension. By injecting your [account identifier](https://app2.abtasty.com/settings/installation-code/tag), you ensure that the visual editor loads the tag properly.
{% endtab %}
{% tab title="Content Security Policy / X-Frames is in cause" %}
If you notice CSP errors in the console when trying to load the editor, the server configuration is causing these problems. The security setting may be too high on your server. By default, many clients use a Content Security Policy that blocks everything on their website. This means that every external request has to be allowlisted in the server configuration.
If you see the following kind of errors, these are caused by CSP errors:
