You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pimcore version: 6.8.7 (but also existed on 6.7.3)
Expected behavior
New Data Object is created and listed in the Data Objects overview list.
Actual behavior
Data Object is not created and following errors are printed in the browsers console. This only happens in Google Chrome, not in Firefox or Safari or Edge. When I try to access the url mentioned in the DOMException Message I do get a response with the string I entered in the name field earlier like {"filename":"driver123"}.
Steps to reproduce
Open pimcore admin in Google Chrome (Version 87.0.4280.141 or Version 88.0.4324.96)
Open Google Chrome debug console
Try creating a new Data Object by right clicking on Home -> Add Object -> Select any object that exists in your system
Enter name for object and click "OK"
Console will show errors from above screenshot
Important note: The pimcore demo only shows xhr request failed messages without any further details multiple times.
The text was updated successfully, but these errors were encountered:
If anyone sees this thing here and needs a solution... Remove the sync-xhr=(), and sync-xhr 'none' values from your webservers permissions-policy and feature-policy CSP (content security policy) response headers.
Bug Report
Pimcore version: 6.8.7 (but also existed on 6.7.3)
Expected behavior
New Data Object is created and listed in the Data Objects overview list.
Actual behavior
Data Object is not created and following errors are printed in the browsers console. This only happens in Google Chrome, not in Firefox or Safari or Edge. When I try to access the url mentioned in the DOMException Message I do get a response with the string I entered in the name field earlier like
{"filename":"driver123"}
.Steps to reproduce
Important note: The pimcore demo only shows
xhr request failed
messages without any further details multiple times.The text was updated successfully, but these errors were encountered: