Credit Icons Gray

Hey Fashun,

Yea I just chose a grey icon, there’s no significance to it, I thought it looked better.

You can just replace credits.png in the plugin with the image of your choice, let me know if you find one that looks good, I can set it as the default.

Cheers,

Sean

@seanvoss, I might be missing something in the Stripe docs but I assume that JCB and Discover aren’t accepted in the UK as I get the following error when trying (test).

Payment error:Your card is not supported. Please use a Visa, MasterCard, or American Express card

Consequently I was going to replace the image, removing those icons, but am concerned that when I update plugin it will get overwritten again.

Any suggestions? An option to replace image in the WooCommerce payment options would be awesome ??

Ahh good point, I stole that image from Stripe’s website You’d think they would consider that. ??

I’ll program that in for you, should be a minor change.

Awesome, I couldn’t have wished for a better response. Thanks.

Have a go with 0.23 there is a new setting in the admin woocommerce settings payment gateways striper (where you put your key in) to specify a URL.

Cheers,

Sean

Excellent, thanks. Does the job nicely!

Just a thought, where HTTPS might not be available when developing, locally it would be good if the protocol was dealt with automatically.

Would stripping the http: or https: from the image src would solve this? Then however the page is rendered it would use the ‘current’ protocol.

e.g. https://website.dev/checkout would use http and https://website.com/checkout would use https.

Seriously not a biggy though and thanks very much for the rapid change to the plugin!

Wait…. actually just using the relative url in the setting in the backend should work fine shouldn’t it?

e.g. /wp-content/uploads/2014/01/credits.png rather than https://website.com/wp-content/uploads/2014/01/credits.png

This would automatically use the protocol based on the address of the page. So assuming you have woocommerce configured correctly, ‘Force secure checkout’ when live it wont break in dev and when live.

Yea, I think that might be the way it’s working, I just noticed that the wordpress seemed to be changing my protocol on my production instance that’s why I wrote the note.

Give it a shot and see what it does in your instance.

Yeah seems to work for me…. not pushed my latest changes to the development server yet, which has SSL configured, but I am 99.99% it will work as is with relative urls. Thanks Sean, great work.