Al Brookbanks

Great!!

Did it work?

It looks like there is a 3rd party patch: https://github.com/noelboss/featherlight/pull/412/commits/ddd0b99569072ce4dc5654f70cb634cfe902d919 We can try this via support if you need help.

This is the only issue I've seen concerning WEBP so far. If you wanted to open a support ticket I'm sure I can fix this for you. Sorry the update has caused problems for you. WEBP was only ever tested on the default skin.

I see. It's definitely failing to load in the image.

What exactly happens? I can't see why it wouldn't be compatible.

Lightbox shouldn't mind about the file format. Which skin is this?

Can you login to the extension configuration screen and click the disconnect button. Once done please connect again. Then save the config and clear the cache.

authenticationReason: ERROR is the clue. This means your customer has failed the security challenge set by their bank (not PayPal) and your PayPal Commerce settings are set to reject this scenario. Check your 3D Secure Scenarios in the module extension config page. In particular "Buyer may have failed the challenge or the device was not verified."

Elasticsearch is free.

Get Elasticsearch installed and you are all set. The default search isn't great for short key word searches.

Do you have a custom skin and does the pay now button disable when it's clicked?

I'll have another look at this in the new year. The new version disables the pay now button on click. It fixed the issue from my testing. Are there different steps to reproduce this? Pressing pay twice in PayPal makes no sense. Also there is no pay button in PayPal but only a continue button.

Well that's incredibly disappointing. Is the Pay Now button disabling when it's clicked and you are sure you are on the latest version?

You should be good based on that. It's quite easy to reproduce on an iPad. Pay with the shortcut yellow button. If you hit the pay now button twice it then goes to a new payment screen instead of going to the processing page. This disables the button so it can only be clicked once.

After all these months I've finally reproduced it and solved it. It was the "Pay Now" button being tapped or clicked more than once. The new release 1.9.3 should fix this but only if the following criteria is met; The checkout form has the id checkout_form The Pay Now button has the id checkout_proceed

It it worth asking the customer if they remember what happened?

Thanks. I'll dust off the iPad and do some tests...

Any pattern or steps to reproduce?

I use Kibana to manage this. Create a user and pass. Assign a role to this user for all privileges on a specific index name. I've not done it for a while so I might create the role first then the account and password.

Add these fields to the includes/global.inc.php file with correct values. Please note that your skin may need changes if you are not using the default Foundation theme. $glob['es_h'] = ''; // Elasticsearch host e.g. https://localhost:9200 $glob['es_u'] = ''; // Elasticserch username $glob['es_p'] = ''; // Elasticsearch password $glob['es_i'] = ''; // Elasticsearch index name $glob['es_v'] = ''; // Elasticsearch vertificate validation enum('1','0') $glob['es_c'] = ''; // Elasticsearch certificate path The last two fields can probably remain empty.

Try setting the values in the includes/global.inc.php file (in most cases the last two can be ignored): $glob['es_h'] = ''; // Elasticsearch host e.g. https://localhost:9200 $glob['es_u'] = ''; // Elasticserch username $glob['es_p'] = ''; // Elasticsearch password $glob['es_i'] = ''; // Elasticsearch index name $glob['es_v'] = ''; // Elasticsearch vertificate validation enum('1','0') $glob['es_c'] = ''; // Elasticsearch certificate path

Stripe.

Tell me about it. CubeCart has had it's fair share of chargebacks too. I hope you don't get more.

Did this transaction pass 3D secure? If so I believe it should be protected and you shouldn't be liable to chargeback fees. Our PayPal integration has much more granular settings. If you want to you can choose to only accept payments that pass 3D secure. With that setting enabled you are never liable to chargeback fees. The square extension could have this feature added.