[Simon Thomas]

Hello there,
we have to integrate facebook chat through which a customer will be able to chat to a vendor from whom they want to purchase a product. Its a multi-vendor store we are developing at the moment.

The chat function comes up with theme we have purchased but we are facing some restrictions to make it work.
I have recorded a video that show how are we replicating this error; https://capture.dropbox.com/iiqtgpIfPzLI01te

Page URL : https://closet-drop.sitepreviews.dev/vendor/samparker1411/

When I searched this, I found this URL (https://stackoverflow.com/questions/43871637/no-access-control-allow-origin-header-is-present-on-the-requested-resource-whe/43881141#43881141) as the best answer.

Thank you in advance.

Attachments:

1. 

   closedrop-issue.png
   

[Sangita Support Squad]

Hello @Simon Thomas, Sorry to hear that you are facing an issue on your end.

But on the store page shared by you, we are not getting the chat option. Hence we are not able to see the errors that you are getting on your end.

So kindly create a staging site that should be an exact replica of your live site and share the staging site url, temporary admin and ftp access with us.

Also while sharing the access don’t forget to mark your reply as private.

[Simon Thomas]

This reply has been marked as private.

[Sangita Support Squad]

@Simon Thomas Thanks for sharing the access with us. Our team is looking into the issue. Kindly provide us some time.

[Simon Thomas]

Hi Sangita,
No worries for the time required to look into this but can you please share a rough ETA or something so we can plan it accordingly.

[Sangita Support Squad]

@Simon Thomas Hopefully by next week we will be able to provide you with a fix for this issue. As our team is already occupied with some previously scheduled work.
Not to worry, once we add a fix for this we will keep you updated.

[Sangita Support Squad]

@Simon Thomas Our development team has examined the configuration issue with the live chat module and Facebook Messenger. The error in the console is attributable to the fact that the meta team has not made the necessary modifications to their API on their end. Our team has already contacted the meta team regarding this matter. The resolution of the errors from our end is contingent upon the meta team updating their API, and we will proceed accordingly once they make the necessary changes.

[Simon Thomas]

Alright, thanks for a response on this.
We need to go live with this feature next week so we are expecting a quick resolution here.

Please keep me posted Sangita.

Thank you and have a good day ahead.

[Sangita Support Squad]

@Simon Thomas, Upon further investigation, we’ve identified that the error is related to Facebook’s own API. We confirmed this by testing Facebook’s plugin for WordPress, and the same issue occurred.

I regret to inform you that, unless Facebook releases an update with a fix, there is very little we can do to address this issue. You can check this link for further update https://developers.facebook.com/community/threads/1005499880601235/

[Simon Thomas]

Hi Sangita,
good afternoon.

Do we have any update on this issue?
This is one of the vital reasons we finalise to purchase this plugin and its not working.

This reason has been a roadblock for us to go live, can you please do the needful here to show us a progress and let us know when can we expect a solution here?

[Sangita Support Squad]

Our team has already replied over the chat for this.

[Sangita Support Squad]

It’s been long and we have not heard back from you. We presume your query is resolved now. We are closing this thread. If you need help or face issue in future please create a new support topic.

[Author]

Posts