Dev Kabir

If the plugin isn’t working on your site, please uninstall it, as it’s not designed for your site. Feel free to leave a one-star review if you find it appropriate.

If the plugin isn’t working on your site, please uninstall it, as it’s not designed for your site. Feel free to leave a one-star review if you find it appropriate.

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.

Hey @jennhaven

Thank you for reaching out and bringing this to my attention. I’m sorry to hear that you’re experiencing issues with the dropdown areas in the main menu and the display of social icons.

Are you confirming that CORS has been enabled on the https://alexandertechniqueusa.org/ site, and

• you’re aiming to fetch data from there to members.alexandertechniqueusa.org?
• https://alexandertechniqueusa.org/ and https://members.alexandertechniqueusa.org are different site ?

Thank you for your patience and understanding!

Hey @nicolas-landgraf

Thank you for reaching out and providing detailed information about the issue you’re encountering with fetching images on your Next.js site after migrating from Siteground to Hostinger.

While our plugin can enable support for apache server, but Nginx server has some server configurations, which may need to be manually adjusted.

To troubleshoot further, I recommend reaching out to Hostinger’s support team for assistance. They should be able to provide insights into any server configurations or services that might be affecting the Fetch API requests on your site.

Additionally, you may want to double-check any server-side settings, such as CORS configurations, to ensure they are correctly configured for your new hosting environment on Hostinger.

If you have any further questions or need assistance with anything else, feel free to let me know. I’m here to help!

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.

Dear Sebastian Joey Lamprecht,

Thank you for bringing this issue to our attention. We appreciate your thorough investigation and proposed solution regarding the Access-Control-Allow-Credentials header in our plugin.

We want to assure you that this issue has been previously reported, and we have added this to our to-do list. Your detailed findings will undoubtedly contribute to resolving it effectively.

If you have any further questions or require additional information, please don’t hesitate to contact us. Your input is valuable to us as we strive to improve our plugin.

Thank you once again for your diligence and cooperation.

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.

Hi @webqiu,

Thanks for reaching out about this issue. Before flushing the cache, could you please confirm whether the plugin is still activated? I’ve checked the API namespaces on your https://qiu.edu.my/wp-json and couldn’t find any entry related to this plugin.

It’s possible that the plugin might have been deactivated, causing the CORS to get blocked again. Once we ensure the plugin is active, we can further investigate the CORS issue.

Looking forward to your confirmation.

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.

Hey @rahul294yadav,

Thanks for reaching out! I attempted to visit your site, but it seems to be unavailable at the moment. Could you please enable it so I can check the issue you’re experiencing?

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.

Dear @zajac007

Thank you for reaching out to me regarding the CORS policy blocking issue with the Facebook Customer Chat Plugin on your WordPress website.

The error message you’re encountering indicates that the request from your website to Facebook’s servers is being blocked due to CORS (Cross-Origin Resource Sharing) policy restrictions. This commonly occurs when the server hosting the requested resource (in this case, Facebook’s servers) does not include the appropriate CORS headers to allow requests from other origins.

To resolve this issue, you can try the following steps:

1. Contact Facebook Support: Since the resource being blocked is hosted on Facebook’s servers, it’s best to reach out to Facebook support or consult their documentation to ensure that the Customer Chat Plugin is configured correctly to allow requests from your website’s origin.
2. Use a Proxy Server: You can set up a proxy server on your own server to forward requests to Facebook’s servers. This way, the request will originate from your server’s domain, bypassing the CORS restrictions. However, setting up and maintaining a proxy server requires technical expertise and may not be feasible for all users.
3. Utilize a CORS Proxy Service: There are third-party CORS proxy services available that can help bypass CORS restrictions by proxying requests through their servers. You can explore these services as a temporary workaround, but keep in mind that relying on third-party services may introduce additional latency and security concerns.
4. Check Plugin Settings: Ensure that the settings for the Facebook Customer Chat Plugin within your WordPress dashboard are configured correctly. There might be an option to specify allowed origins or domains from which requests are permitted.

Since we haven’t received a response from you, I’m proceeding to close this thread. Please know that you’re welcome to contribute to this thread at any time by adding your message.