vuster
Forum Replies Created
-
Forum: Plugins
In reply to: [Super Page Cache] Error: undefined swcfpc_ajax_url is not definedI am also getting this error after upgrading to the latest.
Error: undefined swcfpc_ajax_url is not defined
In my experience, this plugin’s Apple Pay does not work. It will just result in Payment Failed no matter what. The plugin author suggested contacting PayPal Technical Support and I did, but never got a reply. I hope the next update they will address it. They can’t even confirm (or deny) if Apple Pay works on their end.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Google Pay and Apple Pay not workingHappy to report that the new update (Version Version 2.8.2) has fixed this for both Apple Pay and Google Pay. HOWEVER, the digital wallets (both Apple and Google) are NOT requesting contact information (email address), or shipping address, so the transaction comes through as blank for billing and shipping fields. It needs to require these pieces of information in order to process an order. Could you please look into this.
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Apple Pay “Payment Failed”For Apple Pay, there’s no specific error message other than “Payment Failed”. See screenshot. I suspect it couldn’t be processed because there’s no “paymentSource”? Can you confirm on your end that Apple Pay is working? I’ve tested with a fresh install with only WooCommerce and WooCommerce PayPal Payments plugin in the default theme, so I’ve ruled out plugin/theme conflict
View post on imgur.com
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Apple Pay “Payment Failed”here it is https://privatebin.syde.com/?06975d6afc7ed8c5#ACPEVb3Fr1yRpfLLrExkwnqG4eriDsooi2G7C5FhhR3F
i’ve also discovered that google pay is not working. getting this error in the web console:
checkout-block.js?ver=2.8.1:1
TypeError: Cannot read properties of undefined (reading ‘paymentSource’)
at checkout-block.js?ver=2.8.1:1:116856
at l (checkout-block.js?ver=2.8.1:1:107943)
at Generator. (checkout-block.js?ver=2.8.1:1:109299)
at Generator.next (checkout-block.js?ver=2.8.1:1:108306)
at bt (checkout-block.js?ver=2.8.1:1:113953)
at a (checkout-block.js?ver=2.8.1:1:114157)
at checkout-block.js?ver=2.8.1:1:114218
at new Promise ()
at checkout-block.js?ver=2.8.1:1:114097
at checkout-block.js?ver=2.8.1:1:117564
(anonymous) @ checkout-block.js?ver=2.8.1:1Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Google Pay and Apple Pay not workingI’m having the same issue, both Google Pay and Apple Pay not working. Apple Pay would not show any error message (just Payment Failed), but Google Pay would give this error:
“Cannot read properties of undefined (reading ‘paymentSource’)
This has become widespread. Can you work on a fix ASAP?
I’m having the same issue where Apple Pay keeps getting “Payment Failed” error. Has this been resolved?
Yes, would appreciate a follow-up post here when the bug is fixed and update is available. Thank you.
I’ve already done that, but it doesn’t change anything. I believe the Debit/Credit Card button is from the “Advanced Card Processing” tab. To be clear, I want to use the Advanced Card Processing feature of PayPal, but just want to hide the “Debit or Credit Card” button that appears in the “Express Checkout” section because it is redundant.
- This reply was modified 5 months, 1 week ago by vuster.
Forum: Plugins
In reply to: [Super Page Cache] Does it work with Fastcgi cache?Very useful plugin. Thank you. Would you recommend FastCGI instead of the plugin’s Fallback Cache? FastCGI should be faster in case CF is a MISS, right?
Got it. Thank you.
And yes I have “”CF-Connecting-IP” HTTP header” option selected for IP Detection
perfect. Thank you
This works great, but on pages where there’s no instagram feed, it gives this error
Uncaught TypeError: Cannot set property ‘resized_url’ of undefined
Forum: Plugins
In reply to: [Statically] statically cdn cloudflare cname problemThat’s good to know re canonical headers. Thank you.
It just seems a little unfair to me that a high traffic site would pay the same as a low – medium traffic site. But I like your simple pricing. Maybe there’s a happy medium somehow.
As for the price, Cloudflare charges $20 for the Pro plan which basically does what you do AND includes WAF. Just my 2 cents.
Thanks!