286blue

Thanks anbluk, that’s most helpful.

Thanks for the SCA link Melinda.

Am assuming the latest version of the Woocommerce Stripe Payment Gateway takes care of this?

Yes, I tested it on an old mac running OS x 10.7.something with an old version of Safari (possibly 6? I’ve packed it away now). I know that shoppers should be using the latest supported systems but in reality, people hold on to devices, without updating them, longer that we think so I like to test if sites & plugins work across all systems rather than excluding potential business.

BUT, if it’s the case that Stripe doesn’t have backwards compatibility to work with older browsers, so be it – I’ve advised that it’s more important for the checkout page to be SCA-ready in preparation for September 14th rather than working on older browsers (however nice that might be).

I tested it an old mac running 10.7.something.

Aha, I think I’ve narrowed it down to a browser issue.

It works on Chrome, Firefox, Waterfox, and the latest version of Safari but doesn’t work on older versions of Safari.

I guess it’s for security reasons but it’s a shame to exclude shoppers who are using older technology who can’t or don’t want to update/pay for a new computer.

Do you know if there’s a list somewhere of the browsers the plugin does / doesn’t support? I may add a note to the credit card box to inform shoppers who may be puzzled why they can’t enter their card details that they’re using an old browser.

Hi Thomas,

It was a leap of Woocommerce versions but I tested it on another non-public installation and it worked great.

All the plugins are updated apart from one which I’m in the process of trying to purchase via the Woocommerce site BUT I’m seeing the same issue on the Woocommerce checkout page where there’s a narrow white box that I can’t click into to enter credit card information to purchase it.

Uploaded screenshot to https://286blue.com/woocommercecheckoutpage.jpg

Ignore me! Have figured it out

I’m getting the same error – is this plugin no longer supported/working?

From what I’ve seen in various support threads, it’s something to do with the way jetpack processes blog posts and serves them in subscribers emails.

It’s either an SSL http vs https issue (as none of the non-secure http images show up in iPhone emails whereas the https secure images of gravatar’s logos & photos do)

or

it’s the way jetpack is serving up new code calling upon variously-sized “srcset” images that may not exist on the original blog – hopefully @jeherve and the team at Jetpack will have this fixed before the subscribers emails go out tomorrow morning! ??

Hi @jeherve, any update? Still the same issue – haven’t heard anything from my email.

Hi @jeherve, any update? Still the same issue – haven’t heard anything from my email.

Thanks @jeherve, I’ve forwarded the email and hope it will help to fix the issue on images not displaying on iPhone (which had the same problem on this morning’s email to subscribers).

Hi Jeremy, it will probably be easier and more useful to forward you the actual email with images that aren’t displaying on iPhone – that way you can look at it on your (or an) iPhone to check the code. Is there some way you could privately message me your email so you don’t have to publish it publicly here? Perhaps follow then DM me on twitter @286blue

I have seen this issue also with jetpack subscriptions over the previous couple of days. Images don’t show up on iPhone Apple Mail emails but they do on desktop Apple Mail.

any fix soon?

I have seen this issue also with jetpack subscriptions over the previous couple of days. Images don’t show up on iPhone Apple Mail emails but they do on desktop Apple Mail.

Is this an https/SSL issue? I spotted that only images served via https are displayed, images that are http aren’t showing up on iPhone.

Perhaps jetpack has tweaked something over the past couple of days which has blocked non-secure images displaying?