Hi, Storyblok is making requests to the Preview URL when the story’s parent folder is set to “disable visual composer”.
For example, when I am editing a story whose parent folder is set to set to “disable visual composer”, I can see in the Chrome dev tools network panel that Storyblok is making requests to the preview URL. Since the visual composer is disabled, there is no need for Storyblok to make a request to the preview URL.
The expected result is that no requests to the preview URL are made if “disable visual composer” is selected on the parent folder.
Side notes: The folder that is set to “disable visual composer” contains files that are for data retrieval and are not associated with any specific URLs. Also, some stories in the folder have a real_path value.
Storyblok making requests to the preview URL when the story is set to “disable visual composer” causes me the following issue:
While editing stories, Storyblok undesirably makes requests to preview URLs that do not exist. This triggers our error notification system and my inbox fills up with error notification emails.
Is there a way to prevent Storyblok from making requests to the preview URL when story’s parent folder is set to “disable visual composer”?
I checked that with my colleagues and this doesn’t happen in the V2 of the UI. I will check with the developers if this will still be change in V1 as the release of the v2 UI is already pretty close (End of Q1 2022 - Storyblok V2 - Storyblok)
I checked this with my colleagues and unfortunately, we can’t deactivate the iframe as we have customers who are having a callback logic in their preview apps that rely on the iframe being active even when in form only mode but this will be considered for V2.
Got it, thanks @Hannes. As a solution, we could update our code to check routes corresponding to the stories where the visual composer is disabled. But, yes, that would be great if this could be fixed in V2.