[FRONTIFY-17] Issues with frontify-dam-connector Created: 31/May/23  Updated: 04/Dec/23

Status: Open
Project: Frontify
Component/s: None
Affects Version/s: 1.0.2
Fix Version/s: 1.0.3

Type: Story Priority: High
Reporter: Yamini Karuturi Assignee: Riste Drangovski
Resolution: Unresolved Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File image-2023-05-31-12-19-35-273.png     PNG File image-2023-05-31-12-25-33-748.png     PNG File image-2023-05-31-12-25-43-740.png     PNG File image-2023-05-31-13-00-47-213.png    
Template:
Start Date:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Tried to install frontify dam connector for analysis purpose, but facing issue with it. 

 

After getting this widget  tried to click on "open finder" button to add some images from frontify DAM but there is no action is happening and getting this below error in web console.

"Cannot read properties of undefined(Reading 'create')" 

 

 


Specifications included:

Local Host Url: http://localhost:8080/dev/

Magnolia version: 6.2.33 

Edition: Magnolia DX core
Frontify version: 1.0.2



 Comments   
Comment by Yamini Karuturi [ 31/May/23 ]

There is one more issue, initially it is not able to load the script. It is throwing error as "Refused to load the script" Pasting the error screenshot.

 

Could you please have a look and suggest how to proceed further?

Comment by Riste Drangovski [ 31/May/23 ]

Hi Yamini,

I tried to reproduce the issue that you are describing locally, but without success.
Is it possible to attache your magnolia log file to this ticket?

Regards,
Riste

Comment by Riste Drangovski [ 31/May/23 ]

Another idea would be to use magnolia's AddHeadersFilter:
https://docs.magnolia-cms.com/product-docs/6.2/Administration/Architecture/Request-processing-and-filters/Filters.html#_adding_http_headers
where you can set Content Security Policy Headers based on your browser errors.

Generated at Mon Feb 12 02:03:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.