Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #enter-issue-number
What changes did you make and why did you make them?
Fix: Storyblok visual editor preview and click-to-edit
Two issues were preventing the Storyblok visual editor from working on staging:
CSP headers blocking the Storyblok iframe — frame-ancestors was hardcoded to 'self' and X-Frame-Options was set to DENY, preventing app.storyblok.com from embedding the staging site. Fixed by adding https://app.storyblok.com to the frameAncestorsUrls allowlist in scriptUrls.js and updating next.config.js to use it.
Click-to-edit not working — All Storyblok page components were receiving story.content spread as props from server components, so the Storyblok Bridge was never activated client-side. Fixed by adding useStoryblokState directly into each page component (StoryblokPage, StoryblokCoursePage, StoryblokSessionPage, StoryblokResourceSingleVideoPage, StoryblokResourceShortPage, StoryblokResourceConversationPage, StoryblokWelcomePage, StoryblokMeetTheTeamPage, HomePage). Each component now accepts a full ISbStoryData story object and activates the bridge internally, enabling live content updates and click-to-edit in the visual editor.