• Resolved simoncez

    (@simoncez)


    We are getting failed orders since updating on Friday, however not all orders fail?
    Cleared Cache tried on different browsers with no luck, currently turned off but here was a previous attempts logging info, any help greatly appreciated

    Card Processing failing Logging Info
    No such source: {\”id\”:\”src_1BnANHIZVKCfUBhxQBB48fLd\”,\”card\”:{\”exp_month\”:10,\”exp_year\”:2022,\”brand\”:\”Visa\”,\”card_automatically_updated\”:false,\”country\”:\”US\”,\”cvc_check\”:\”pass\”,\”funding\”:\”credit\”,\”last4\”:\”7355\”,\”three_d_secure\”:\”optional\”,\”address_line1_check\”:null,\”address_zip_check\”:null,\”tokenization_method\”:null,\”dynamic_last4\”:null},\”bitcoin\”:\”\”,\”flow\”:\”none\”,\”object\”:\”source\”,\”status\”:\”chargeable\”,\”type\”:\”card\”,\”usage\”:\”reusable\”}

    The page I need help with: [log in to see the link]

Viewing 12 replies - 16 through 27 (of 27 total)
  • Plugin Contributor royho

    (@royho)

    @dungey140 did you try clearing your cache on server side and from any plugins you may have?

    Can anyone advise which files need purging from caches? I’m guessing it’s /wp-content/plugins/woocommerce-gateway-stripe/assets/js/stripe.min.js?ver=4.0.4 but some confirmation would be helpful.

    Z

    (@killinski)

    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.

    @killinski, make sure /wp-content/plugins/woocommerce-gateway-stripe/assets/js/stripe.min.js?ver=4.0.4 is purged and not returning a cached version. That fixed it on my sites.

    Z

    (@killinski)

    And how does one check that?

    You could run curl -I https://yourdomain.com/wp-content/plugins/woocommerce-gateway-stripe/assets/js/stripe.min.js?ver=4.0.4 in a command line/terminal window and check the response, if you use Varnish you might see X-Cache: HIT for example. Or your browser’s dev tools.

    If that didn’t mean anything, or you don’t know what caching is active on your server, ask your host for help.

    Z

    (@killinski)

    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.

    Did you point your host to this page? It’s pretty simple – they need to purge https://yourdomain.com/wp-content/plugins/woocommerce-gateway-stripe/assets/js/stripe.min.js?ver=4.0.4

    If they can’t do that then please consider moving hosts. In the meantime, what’s your URL? I could check if it is indeed caching that’s causing the issue.

    Z

    (@killinski)

    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.

    Z

    (@killinski)

    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

    The process for clearing the cache depends on what caching system is active. For example I have Cloudflare, Varnish and WP Rocket caches. At this point if your host can’t help then you should hire a developer.

    Z

    (@killinski)

    Thanks for your help.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘Failed Orders’ is closed to new replies.