> For the complete documentation index, see [llms.txt](https://shoppad.gitbook.io/blogstudio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shoppad.gitbook.io/blogstudio/troubleshooting/blog-studio-editor-not-working.md). # Blog Studio Editor Not Working *** #### **The Issue:** If you can't scroll, click, or edit content in the Blog Studio editor, another app on your store is likely the cause. Some apps inject overlays or styles into every page, including the editor preview. When that happens, the app's element can cover the editing area and block interactions entirely. \ \ Common examples include email marketing popups, cookie consent banners, geo-redirect tools, and spin-to-win widgets. #### **What to do** Contact our support team and we'll take it from there. \ \ We'll send a collaborator request to access your store and add a CSS adjustment that prevents the app from loading inside the editor. It won't affect how your store looks to customers. Once you receive the collaborator request, you can approve it in your Shopify admin under Settings > Users and Permissions > Collaborators. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://shoppad.gitbook.io/blogstudio/troubleshooting/blog-studio-editor-not-working.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.