rchannelwp

Hello @leap13 thanks for following up.

Unfortunately, we cannot share additional information about our client’s site.

For now, we’ll keep that widget disabled until maybe the issue duplicates somewhere and a fix is implemented.

We don’t see any additional errors anywhere else so it is a bit strange. At least we were able to isolate it to the Blog Widget.

Thanks for your time and follow up. You can mark it resolved as far as we’re concerned.

Ok, with some trial and error so far this is what I did:

1) Switched ALL off, obviously editor loads (EDITOR LOADS)
2) Switched one at a time, and when I got to “Blog” widget, editor doesn’t load anymore (DOES NOT LOAD)
3) Switched ALL on (DOES NOT LOAD)
4) Switched ALL on, and “Blog” off (EDITOR LOADS)

Since we’re not using the Blog widget I suppose we can turn it off for us, but maybe others having this issue that use Blog widget that might not work. Also, I don’t receive any errors in console log when Blog widget is enabled and editor doesn’t load.

Hope this helps.

Interesting, thanks for quick reply.

We’re trying to find out if we can force 3d Secure for Google Pay (and alternatively Apple Pay) via Stripe.

It seems that with Payment Intent API’s we might be able to do this…

Thank you!

@mrclayton,

Thanks – I was hoping we would get to that point. I’ve sent a request via the Help button.

Best,
rchannelwp

@mrclayton Thanks, I never want to modify plugin source code.

The next release of the plugin will check to see if the customer has entered an email address and/or phone number in the checkout billing fields before requesting it in the Apple Pay wallet. That will ensure that if it’s a new customer and the values are blank, that info is requested in the Apple Wallet, but if it’s a returning customer and those values are pre-populated, then it won’t request them.

Perfect I think this will definitely help, thank you.

Regarding your custom fields like _billing_username there isn’t anything in the Stripe plugin that would prevent those from being populated when an order is created on the checkout page.

That’s what is weird, then regarding custom fields I’ll have to check if its not Cartflows plugin, but all other payment methods still include those fields so thats why I was thinking it could be the way this payment plugin changed.. Hmm.

Thanks for your continued replies and your hard work!

Best,
rchannelwp

Ok lets try…thanks for your patience!

From wp_postmeta (emails and usernames modified for privacy) see the data that is stored.

These are real orders and if you compare them, the wp_postmeta for the Apple Pay order (the last one listed) has the _billing_username and _billing_existinguser with blank values, and the _billing_email is populated with the contact from apple pay email (I know this cause I tried it myself and it used my contact apple pay contact email instead of my website account email).

Alipay:

"1261381"	"78141"	"_payment_method"	"stripe_alipay"
"1261387"	"78141"	"_billing_email"	"[email protected]"
"1261399"	"78141"	"_billing_username"	"username1"
"1261400"	"78141"	"_billing_existinguser"	"true"

Stripe:

"1263099"	"78217"	"_payment_method"	"stripe_cc"
"1263105"	"78217"	"_billing_email"	"[email protected]"
"1263117"	"78217"	"_billing_username"	"username2"
"1263118"	"78217"	"_billing_existinguser"	"true"

Apple Pay:

"1267993"	"78470"	"_payment_method"	"stripe_applepay"
"1267999"	"78470"	"_billing_email"	"[email protected]" <---this is actually the 'contact email' from apple pay wallet
"1268011"	"78470"	"_billing_username"	""
"1268012"	"78470"	"_billing_existinguser"	""

• This reply was modified 5 years, 9 months ago by rchannelwp.

@mrclayton ok we pulled a backup and the version we used with no issues was 3.1.1

-rchannelwp