Bug #100795
closed
Content element "View" button does not reload page, when preview is hosted on different (sub-)domain
0%
Description
An Typo3 multidomain installation is hosted on typo3.domain.com, the sites are hosted for previewing on site1.domain.com, site2.domain.com,... Cookie Domain is set to *.domain.com. So all FE-previes show admin panel, etc.
When clicking on a view button a new tab/window is opened. When clicking again, while the window is still open, the backend will throw this JS error:
Uncaught (in promise) SecurityError: Blocked a frame with origin "https://typo3.domain.com" from accessing a frame with origin "https://site1.domain.com". Protocols, domains, and ports must match.
I think it's related to: https://forge.typo3.org/issues/93706
It worked fine in LTS 10, but after updating to LTS 11 editors have always to close the tab before clicking the view button.
Updated by Oliver Hader over 1 year ago
https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy explains what happens and also refers to the mentioned SecurityError (side-note: this is not caused by content-security-policy).
Updated by Oliver Hader over 1 year ago
- Related to Bug #93706: Content element "View" button does not reload page added
Updated by Oliver Hader over 1 year ago
- Status changed from New to Accepted
The change used for issue #93706 probably would help here as well, since it checks the URL for the same-origin (and skips the operation, in case of a mismatch).
Updated by Webadmin no-lastname-given over 1 year ago
11.5.27 does fix this problem! Thank you!
Updated by Annett Jähnichen over 1 year ago
- Status changed from Accepted to Needs Feedback
Can we close this issue?
Updated by Webadmin no-lastname-given over 1 year ago
From our point of view the problem is solved.
Updated by Riccardo De Contardi over 1 year ago
- Status changed from Needs Feedback to Closed
Thank you for your feedback. I close this issue as it looks solved.
If you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one.