Any help is greatly appreciated? We are missing the functionality since it worked perfectly and was a great addition to the webshop.
Let me know.
Mark
I’ve also started getting this error.
Possibly could be to do with a caching plugin as seems to work after claring cache.
Using W3 Total Cache.
Hard to say exactly when it started – had the first report from a customer today.
Is this a known issue? Is there a particular setting within the cache plugin that could be tweaked (if that is indeed the cause)?
Thanks,
Simon
Helo!
I started to have this problem in the last few weeks. In some cases (I could not understand if there is a pattern) this error (“Something went wrong, please try after sometime”) is occurring.
I’m thinking of going back to some versions to see if it resolves.`
I have the same issue though I cannot clear it even when changing caching settings. Also filed a support ticket as I bought some of their extensions but no reply since a couple of days.
Hello there,
This week(tomorrow/day after tomorrow) we planned for major update v2.0 in this we added alternate solution to overcome this something weñt wrong error.
We will reply back here with detailed information about that option after our update.
Thanks.
We use one layer of security to our ajax request which is WP Nonce – but due to caching mechanism from third party plugins/hosting this security nonce also cached which cause this error “something went wrong, please try again after some time”, some cases by setting up cache timeout in plugin settings reduce this kind of issue.
How to get rid of this error?
From version 2.0 we added different techniques to avoid Something Went Wrong Error – If your site has encounter such issues we suggest you to try the below steps to get rid of Something Went Wrong Error
Go to Admin Dashboard -> Instock Notifier -> Settings -> Troubleshoot Settings Section -> Frontend Subscribe Form Submission via
It has two option one is WordPress AJAX(default) and another one is WordPress REST API Route
Try change that option to WordPress REST API Route and check it out(purge your cache and check it out).
If the above steps not helpful then follow the another method which is Google reCAPTCHA v3(Invisible Recaptcha) – For that you need Site key and Secret Key of v3 – Go to Admin Dashboard -> Instock Notifier -> Settings -> Google reCAPTCHA Settings -> Enable Google reCAPTCHA and Choose Version -> V3 followed by Site Key and Secret Key(both fields required in order to function properly)
If v3 not helps try v2 of Google reCAPTCHA
Thanks.
Thanks for the update.
Changing to the WordPress API route by itself didn’t seem to work, though after also activating the reCaptcha V3 my next attempt did.
Hard to know whether it’s truly fixed or not though as the problem appears to be intermittent anyway.
Fingers crossed this does the trick!
Thanks for looking into it.
