Issue loading using ajax

It depends on how plugin code is rendered in block. Timer plugin needs to run some Ajax requests to get current settings, events, etc. If it fails to do so, it starts from scratch, i.e. for 0 seconds – looks like this is the issue you report.

I will check your link in my browser dev tools and come back here if I have suggestions.

Hi,

Thanks for that. So from checking dev tools, the ajax lookup url is this:
/wp-admin/admin-ajax.php?action=scd_query_next_event&smartcountdown_nonce=ea8fe56c87&unique_ts=1588600400050&id=smartcountdown-3

and the response is this:

{err_code: 100, err_msg: "Invalid Token!"}
err_code: 100
err_msg: "Invalid Token!"

Hi,

Any news on this?

Sorry for the late response. I remember entering earlier and for me it worked: https://haverickmeatstoyou.com.au/shop/

There are some layout issues, but the counter itself looks good. So I thought the problem was already solved.

However, I have you page open right now and there is no error in smartcountdown-3 AJAX response.

Maybe I’m missing something.

Hi Alex,

The issue is when you add something to the cart. The sidebar that opens up you’ll see the only box that is populated is the seconds and from the code inspector you can see a network error in the ajax response.

Weird thing is, that sometimes it works.

OK, now I get it. I cannot test it because a valid zip-code is required to proceed, I think. Can you provide a sample zip-code, so I can get to the shopping cart?

Okay yeah sure, just use 2001

Now I see the issue. I’m not sure why you display countdown timer in sopping cart – it is the same as you show on shop page.

Really, sometimes it works. It depends on which script is run first – sidebar shopping cart or Smart Countdown FX ajax. Smart Countdown admin ajax requires wp_nonce token, so if it’s not set in request, code_err: 100 is returned.

I’m not sure we can fix it. I propose that you keep shop page countdown that works and remove any additional counters from sidebar cart.

Hi,

Thanks. We’ve removed it from the sidebar. It was there as the client wanted it, but I agree it makes no sense there.