Z

Thanks for your help.

Here’s what I get if I remove all the bot blocking from my .htaccess:

HTTP/2 200 
server: nginx
date: Fri, 16 Feb 2018 16:52:43 GMT
content-type: application/javascript
content-length: 15585
last-modified: Tue, 06 Feb 2018 22:26:09 GMT
etag: "3ce1-56492aa521243"
accept-ranges: bytes
vary: Accept-Encoding,User-Agent
host-header: 192fc2e7e50945beb8231a492d6a8024

I showed them this thread, yes – to no avail.

My hosts are actually great, but English is not their first language (typically) so perhaps some of this gets lost in translation.

I’d rather not post my URL here, but can say that the issue is still occurring. I hate to ask, but could you clarify exactly how to purge the cache you’re referring to?

If not, I guess I’ll remove or roll Stripe back, given the radio silence from the dev.

Yeap,

unfortunately this was meaningless. My hosts were like “why do this” and I couldn’t really explain. They tried it anyway, but were blocked form doing it by .htaccess (for some reason), they then deleted my .htaccess and replaced with a standard one, and told me that the above command worked (whatever that means).

I asked them to figure out what was blocking it in the original .htaccess, to which they said “We have put your old one back. Sorry. Tough.”

So I’m in the same position as before.

I’d actually love to see @royho chime in with a fix, because this issue arrived with the update and he hasn’t said a word (to me) regarding it yet.

Customers are bailing in the card because of the “no source” issue still. I even had one complaining that the error “Wasn’t very friendly.” WTF.

And how does one check that?

Same issue here.

Have intentionally excluded all woocommerce pages in case it was (as previously suggested) a caching issue and it intermittently persists.

A staging version of the live site with all but essential woocommerce plugins produces same issue.