Something went wrong, please try after sometime

  • If cache is on, it’s always “Something went wrong, please try after sometime” error when trying to
    subscribe. Are you going to do something to this? Your solution to change WordPress AJAX (default) to WordPress REST API Route doesn’t work. Totally useless plugin because developer doesn’t do anything to it. Could you really do something to it? I don’t want to clear cache every 12 hours. One star plugin because I cannot give zero star. Thank you very much.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support CodeWooGeek Support

    (@codewoogeeksupport)

    Hello there,

    Good Day!!

    We apologize for the inconvenience caused, and we’re here to assist you with this issue.

    We have used one layer of security for our ajax requests, which is WP Nonce, but due to the caching mechanism from third party plugins/hosting, this security nonce is also cached, which causes this error “Something Went Wrong,Please try again after some time.” 

    Since you’re using the REST API Route, here are some alternative suggestions:

    1. Cache Timeout: Adjust the cache timeout settings in your caching plugin to reduce conflicts. This may help prevent the caching of nonce data, which can lead to errors.
    2. Google reCAPTCHA: Consider using Google reCAPTCHA v2 or v3. You will need a Site Key and a Secret Key for this. (Go to Admin Dashboard -> Instock Notifier -> Settings -> Google reCAPTCHA Settings -> Enable Google reCAPTCHA and select Version -> v2/v3. Enter both the Site Key and Secret Key for proper operation.)

    These adjustments are aimed at mitigating caching conflicts and enhancing performance. We would appreciate it if you could revisit your review after trying these solutions. If the issue persists, please let us know, and we’d be happy to assist further.

    Thanks.

    Plugin Author CodeWooGeek Dev Team

    (@codewoogeekdev)

    Hello there,

    We’d like to share some updates that should help with the issues you’ve been experiencing.

    1. Updated Google reCAPTCHA Settings Pathway:
      Admin Dashboard -> Instock Notifier -> Settings -> Bot Protection -> Bot Protection through -> Google reCAPTCHA -> Enable Google reCAPTCHA in Subscribe Form (Enable) -> Enable Google reCAPTCHA Version -> v2/v3. Enter both the Site Key and Secret Key for proper operation.
    2. Introducing Turnstile as an Alternative: We’re also pleased to offer Turnstile as an additional option for bot protection. You will need a Site Key and a Secret Key for this. Go to Admin Dashboard -> Instock Notifier -> Settings -> Bot Protection -> Bot Protection through -> Turnstile -> Enable Turnstile in Subscribe Form (Enable) -> Turnstile Site Key -> Turnstile Secret Key.

    Thanks.

    Thread Starter temporaryfailure

    (@temporaryfailure)

    I’m not using recaptha at all. Shortening cache time is odd because it starts to make cache useless if I have to purge it under every 12 hours.

    deVOS

    (@damiandevos)

    I had the same issue. Adding Google reCAPTCHA to the back in stock notifier form did the trick.

    Thread Starter temporaryfailure

    (@temporaryfailure)

    It works now. I edited

    $security = wp_create_nonce(‘codewoogeek-product_id-‘ . $product_id);

    and changed $security to a fixed string.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this review.