-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Real-time data update not working in deployed demo site #85
Comments
It's probably some CSP header or iframe security setting. One thing though is that if realtime updates is not enabled then the UI should not allow add and remove etc to be enabled. and probably there should be a warning to tell the user that updates are not enabled and so you won't see a change until after save. Can maybe split that out to seperate card though? |
Is it not specifying the frontend domain but using "*" here?
Other stuff talks about timing on adding hte event listening https://medium.com/@crookse/cross-domain-communication-parent-window-and-child-iframe-aaf90fcb3e26 and Cross-Origin-Embedder-Policy https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage |
@MAX-786 your frontend doesn't have CSP or Cross-Origin-Embedder-Policy so both of those probably need to include the CMS domain to allow messages to be received? |
So I hope its not an issue with Hydra Side :) Yeppp might be better if somehow we tell the editor if the realtime editing is enabled or not. Lets discuss the 'HOW' in separate issue ig. |
Yes it had the origin of iframe src as recipient's origin, but the issue was intact so i tried removing it. Guess I'll revert it back to how it was and do the CSP fixing on frontend side. |
If CSp is the fix then don't forget to document it in the readme |
Figured it out! |
@MAX-786 getting a new problem now I think
|
The deployed site is not recieving the realtime updates, because if you try the main branch locally it works fine but the deployed one doesn't,
I think it is because iframe is not recieving postMessage correctly or maybe it is an issue from frontend side idk, nd i tried to fix it but couldnt. Still looking into it.
The text was updated successfully, but these errors were encountered: