CORS and Live Preview

[versed sky]

When checking the console on the frontend I noticed this error:

Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://localhost:3001') does not match the recipient window's origin ('http://localhost:3000').

(payload = 3001, next = 3000)

Which seems like some sort of CORS issue with live preview? Any insights?

Also, referencing this example it seems like data is coming from useLivePreview at all times. Is this okay? Should there be a draft mode or some sort of conditional so that it isn't trying to subscribe outside of the admin?

[earnest briar]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• relationships-and-or-uploads-are-not-populating
• available-plugins
• blog

Community-Help:

• [Live preview] Relationship fields and images returning null
• Cannot create admin user
• Live preview with NextJS
• Fetch user from custom endpoint

[dense portal]

Hi, yes, data should come from the live preview on your front end. You don't need a draft mode. You should also add your frontend address to the cors in your payload config. Something like cors: [http://localhost:3000]. I hope this helps

[versed sky]

Figured, but just wanted to make sure. Thanks @dense portal !