Ajay Ghaghretiya

It Redirecting correctly on my end. Please check by deactivating other plugins & check with the default theme.

Hi @kokkieh

Thanks for your response.

No, we have not done any custom code for this method stats_get_csv. We just call it to get pageview stats. Our site is managed by the WordPress VIP Server where we are unable to access Jetpack directly.

Check the screenshot: https://drive.google.com/file/d/1cKCvuK4Dggf4EXKHwGVvtq8ZUKt23p_S/view

Site: https://sneakernews.com

We think issue is occurring randomly.

Regards,
Ajay

Hello Roshni,

Thanks for looking into this.

I followed the steps that you have explained. but still, I am facing the issue.

I debug the code and found that the issue is occurring from the dokan pro plugin while the dokan pro plugin calls the function dokan_get_store_info() from the dokan-lite plugin.

We have a dokan-pro plugin with the version 2.7.0

Kindly check the dokan-lite with the mentioned dokan-pro version of the plugin.

And please update us so we can fix this issue asap.

Thanks

Hello

Anyone here for looking into this??????

This is the major error that we are facing.

The suggestion will be appreciated.

Thanks

• This reply was modified 6 years ago by Ajay Ghaghretiya.

Hello @achchu93

Thank you so much.. It’s working fine now.

@roshni07 Is there any updated in the dokan pro plugin for fixing this issue?

Please do let us know if you have fixed this issue.

Thanks

Fixed..!!

Thanks

Hello Luminus,

Thanks for your replay..!!

We have installed the Health Check plugin on our live server and we have tried to troubleshoot the issue but we can not activate some plugins using this troubleshooting functionality it is displaying the notice that we can not enable this plugin and it causes the issue and we have reverted it. We just need to catch the error from wc setting page.

As we have discussed with our server support team they told us that woocommerce support team will provide you to the element arguments that need to exclude from that page.

And also break the woocommerce setting page while we are updating the plugin to the latest version of the plugin and it is displaying the PHP Fatal error: Cannot declare class WC_Settings_General But as we have reviewed the code we can to found the WC_Settings_General.

We have configured the same setup on our local server for troubleshooting this issue but we are not facing these issues on our local server.

Please do assist us here in fixing this issue. And How we can troubleshoot this issue?

Thanks,
Ajay

Hello Josh,

We have fixed this issue by updating the Origins from Auth0 application. And It is working as expected.

Thanks for your support.
Ajay

Hello Josh,

Thanks for your detailed information about this issue.

Yes, It would be great if you can provide us the URL of the ticket of Allowed Origins (CORS) Issue.

Also, we will look into the settings that you have suggested.

Thanks,
Ajay

Hello Josh,

I disabled the legacy API and tried to login, which gave me this:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thinkscience.au.auth0.com/co/authenticate. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thinkscience.au.auth0.com/co/authenticate. (Reason: CORS request did not succeed).

Please do let us know your inputs about the same.

Thanks
Ajay

Hello Josh,

I have not the Auth0 dashboard details but I have all the details about the Auth0 plugin details and website environment.

Can we need to change anything from the Auth0 dashboard? or from the plugin to working with the new lock APIs.

What details you need?

• This reply was modified 6 years, 4 months ago by Ajay Ghaghretiya.

Hello Josh,

Today Auth0 shut off the legacy endpoint, and our logins stopped working. They have a switch that allows us to use this old endpoint until August 6, but after that nobody will be able to log into our website. (I enabled this switch, so our site is fine right now.)

I had hoped that updating to the latest plugin would fix this, but it hasn’t.

We are using the latest version of the plugin(Version 3.6.2) and using the Lock js https://cdn.auth0.com/js/lock/11.5/lock.min.js.

What do we need to do now? please suggest…

Thanks,
ajay

Hello Josh,

Thanks for your replay!!

We will look into this and let you know if we will face any difficulty for the same.

Thanks,
Aj

Hello Josh,

our developer has more looked into this and found that some code of our functions.php that are checking the [‘DOING_AJAX’] every time when you called the Ajax. but we were not getting this parameter from the ajax call of “Resend Verification Email” that’s why it prevents your ajax call.

We are using the [‘DOING_AJAX’] for the security purpose can we add this to the plugin when calling Ajax. Please do let me know your thoughts about the same.

Thanks,
Aj

Hello Josh,

Thanks for your supports. We have fixed this issue.

Much appreciated.

Thanks,
Aj

• This reply was modified 6 years, 4 months ago by Ajay Ghaghretiya.