{"section":"troubleshooting","requestedLocale":"en","requestedSlug":"my-stores-site-editor-is-not-working","locale":"en","slug":"my-stores-site-editor-is-not-working","path":"docs/en/troubleshooting/data-access-and-security/my-stores-site-editor-is-not-working.md","branch":"main","content":"[Site Editor](https://developers.vtex.com/docs/guides/store-framework-working-with-site-editor) is the Content Management System (CMS) available for stores using [Store Framework](https://developers.vtex.com/docs/guides/store-framework). In some situations, you may encounter difficulties opening the Site Editor or saving content.\n\nBelow are some instructions to help you solve these issues in Site Editor.\n\n| Issue | Description | Instructions for resolving the issue |\n| ----- | ----------- | ------------- |\n| [Site Editor doesn't open](#site-editor-doesnt-open) | The Site Editor page displays a blank screen or the `Something went wrong` message. | - [Check the search integration](#checking-the-search-integration).
- [Check the tenant configuration (new accounts only)](#checking-the-tenant-configuration-new-accounts-only). |\n| [I can't manage my store's content in Site Editor](#i-cant-manage-my-stores-content-in-site-editor) | You can't edit, save, or delete content in Site Editor. | - [Check if the user role has the necessary permissions](#checking-if-the-user-role-has-the-necessary-permissions).
- [Check the domain's main location](#checking-the-domains-main-locale). |\n| [I lost the content stored in Site Editor](#i-lost-content-stored-in-site-editor) | Content saved in Site Editor was lost. | [Open a ticket with VTEX Support](https://supporticket.vtex.com/support). |\n| [I'm still experiencing issues with Site Editor](#i'm-still-experiencing-issues-with-site-editor) | You're still experiencing issues with Site Editor after trying to resolve them. | [Open a ticket with VTEX Support](https://supporticket.vtex.com/support). |\n\nTo understand and correct each error, see the solutions below:\n\n## Site Editor doesn't open\n\nThe following error may occur: when you go to **Storefront** > **Site Editor** in the VTEX Admin, the page may show a blank screen or the `Something went wrong` message.\n\n\n\nTo solve this issue, see the following instructions:\n\n1. [Check the search integration](#checking-the-search-integration).\n2. [Check the tenant configuration](#checking-the-tenant-configuration-new-accounts-only)\n\n### Checking the search integration\n\nThis issue may be related to [Intelligent Search](/en/docs/tracks/intelligent-search-overview) not being integrated with the store catalog. Follow the steps below to integrate it into your store:\n\n1. In the VTEX Admin, go to **Store Settings > Intelligent Search > Integrations**.\n\n2. On the **Integrations** page, make sure all statuses are checked, as shown in the image below.\n\n \n\n3. If all statuses are checked, and you still can’t open Site Editor, see the [Checking the tenant configuration](#checking-the-new-account-tenant-configuration) section. Otherwise, proceed to the next step.\n\n4. If the Integrations page doesn't look like the image above, here are the causes and how to fix them:\n\n- **The status `Enable search` isn't checked**: The integration hasn't been started. Click `Start integration`.\n- **One of the statuses failed and is not checked**: If you've already tried to start the integration but it failed, open a ticket with [VTEX Support](https://supporticket.vtex.com/support) to report the error.\n\n### Checking the tenant configuration (new accounts only)\n\nIf you already have the [search integrated](#checking-the-search-integration) and still see a blank screen when you click **Site Editor** in the VTEX Admin, the store might not have the tenant set, or there might be an error in this setting.\n\nVTEX uses a [SaaS multi-tenancy](https://developers.vtex.com/docs/guides/cloud-infrastructure#saas-multi-tenancy) architecture approach, where each account is a tenant that must be connected to the VTEX architecture through a binding to sync data.\n\nTo configure the tenant in your store, open a ticket with the [VTEX Support](https://supporticket.vtex.com/support) team to request it. Once you receive a response from Support confirming the tenant configuration, go to the VTEX Admin and click **Storefront > Site Editor** to verify that the site opens correctly. If the blank screen persists, add this information to the same ticket so the team can investigate further.\n\n## I can't manage my store content in Site Editor\n\nOne error that can happen in Site Editor is when you can't edit, save, or delete content. When you try to do one of these actions, you see the following message:\n\n```bash\nSomething went wrong. Try again.\n```\n\nTo solve this error, see the following instructions:\n\n1. [Check if the user role has the necessary permissions](#checking-if-the-user-role-has-the-necessary-permissions).\n2. [Check if the sales channel is configured in the catalog](#checking-if-the-sales-channel-is-configured-in-the-catalog)\n3. [Check the domain's main locale](#checking-the-domains-main-locale)\n\n### Checking if the user role has the necessary permissions\n\nOne possible reason for this issue is that a [role](/en/docs/tutorials/roles) used for content management doesn't include the `CMS GraphQL API` [resource](/en/docs/tutorials/license-manager-resources) in License Manager.\n\nMake sure that users have the `CMS GraphQL API` resource associated with their roles by either [creating a new role](/en/docs/tutorials/roles#creating-a-role) or editing an existing one.\n\nIf you still can't manage content even after adding the `CMS GraphQL API` resource to the user role, see the next section: [Check if the sales channel is configured in the catalog](#checking-if-the-sales-channel-is-configured-in-the-catalog).\n\n### Checking if the sales channel is configured in the catalog\n\nAnother possible reason for this error is that the account's sales channel isn't correctly associated with the store catalog, which prevents Site Editor from loading or saving content.\n\n1. In the VTEX Admin, go to **Store Settings > Channels > Sales channels**.\n2. Check whether there's a sales channel associated with your account and whether it's correctly configured for the store catalog.\n3. If no sales channel is configured, or if it isn't correctly associated with the store catalog, [configure a sales channel](/docs/tutorials/creating-a-trade-policy) for the account.\n4. If the sales channel is already configured and the problem persists, open a ticket with [VTEX Support](https://supporticket.vtex.com/support) to verify the association between the sales channel and the catalog.\n\nIf you still can't manage content, see the next section: [Check the domain's main locale](#checking-the-domains-main-locale).\n\n### Checking the domain's main locale\n\nThis error can also occur due to the locale configured for the account.\n\n1. [Install](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app) the `vtex.admin-graphql-ide@3.x` app using your terminal.\n\n2. In the VTEX Admin, go to **Store Settings > Storefront > GraphQL IDE**.\n\n3. In the dropdown menu, select the `vtex.tenant-graphql@0.1.2` app.\n\n4. In the text box, enter the following query:\n\n ```graphql\n query {\n tenantInfo {\n bindings {\n id,\n canonicalBaseAddress,\n defaultLocale\n }\n }\n }\n ```\n\n5. Check the main locale set for your store. This information is available in the `defaultLocale` field. See the example below.\n\n \n\n6. Now, go to **Store Settings > Channels > Sales channels**.\n\n7. On the **Sales channels** page, select the sales channel associated with your account and check the **Locale** field.\n\n \n\n The locale is considered incorrect in the following cases:\n\n - The locale is different from the one the account should use. For example, the locale is set to `pt-BR`, but it should be `pt-PT`.\n - The country code in the locale is lowercase. Since this configuration is case-sensitive, the locale must appear as `pt-BR` instead of `pt-br`.\n - The locale configured in the sales channel is different from the `defaultLocale` identified.\n\n8. In all cases, open a ticket with [VTEX Support](https://supporticket.vtex.com/support) to request an update to the locale configured in the sales channel. Remember to include evidence of the error, such as screenshots, message logs, and details of your prior investigation.\n\n## I lost content stored in Site Editor\n\nOpen a ticket with [VTEX Support](https://supporticket.vtex.com/support) to investigate the issue further.\n\nTo avoid losing content stored in Site Editor when changing the peer dependencies of the Store Theme app, follow the steps in the guide [Migrating CMS settings after a major theme update](https://developers.vtex.com/docs/guides/vtex-io-documentation-migrating-cms-settings-after-major-update).\n\n> ⚠️ In cases where content stored in Site Editor is lost, restoration is only possible if the loss is related to the known issue of [Intermittent Site Editor content loss](/known-issues/intermitent-site-editor-content-loss). In this case, open a ticket with [VTEX Support](https://supporticket.vtex.com/support) with `urgent` priority.\n\n## I'm still experiencing issues with Site Editor\n\nIf you've already tried the solutions mentioned above and are still experiencing issues with Site Editor, open a ticket with [VTEX Support](https://supporticket.vtex.com/support), including evidence of the problems encountered:\n\n- Error messages.\n- [Console log messages](https://developer.chrome.com/docs/devtools/console/understand-messages) (if any).\n- Changes made before the error.\n- Screenshots of the issue.\n- Date and time when the issue started.\n- Tests you've already performed and the steps to reproduce them."}