Al Brookbanks

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.

So the stock level is a red herring. Do you have Elasticsearch enabled? We need solid steps to reproduce this. What intrigues me is that the vast majority of stores are not prone to this. So what's different? Could there be a common setting between each store with the issue or possibly an common 3rd party extension or skin.

Thanks I don't need to see the request log. I've worked with another merchant who has had this issue on rare occasions. I've spent uncountable hours trying to work out what in earth is happening. This is a scenario that I haven't tried!! Easy to reproduce so I'll do this early next week. Sorry about this. Terribly frustrating but if you are right then it should be something I can resolve (hopefully without too much difficulty).

Is the store and extension up to date? Do we know what steps we need to take to reproduce this? Can the customer provide any feedback as to what may have happened? Can you contact PayPal to recover the fees for a double payment?

As fas as I am aware this was an uncommon issue that hasn't raised it's head since recent versions that addressed it. In particular there was a JavaScript redirect that could fail. We added a "if this page doesn't redirect click here" message to help move it along. There have been other enhancements but I can't recall what was done. This shouldn't happen with the latest version but if it does we can't fix it without steps to reproduce the issue.

It's impossible to say.

I mean I'd need to debug this via support. I'm not sure what's gone wrong.

Oh dear sorry you have problems. I'm not sure what's going on here I'm afraid without a deeper look. All good here. Hope you are well and business is good.

Did you clear the cache? The big orange button in the back end?

This is quite a good explanation https://www.adobe.com/creativecloud/file-types/image/raster/webp-file.html