Callum MacGregor

Thank you for the clarification.

Yeah, until they scrap pages too 😄

I got it working now. Thanks @Adriano Faria for offering to help. I had to create a dummy extension in admincp, then the extensions.json was created correctly. This is exactly why I am so reluctant to upgrade Invision to newer versions.

I don't have an extensions.json file, its an old application. I'll try and create it myself.

Its my own application. For a bit more information, in the admincp the extension does show up as expected: However, I logged what ItemsIterator collects from \IPS\Application::allExtensions call, and my extension is no longer listed there:

I have an application that creates a custom commerce package, extending \IPS\nexus\Invoice\Item\Charge. Up until the latest update it worked fine, but since the latest update the ItemsIterator expects all extensions to be in the 'nexus' application, and therefore cannot load the class of my package object. How it works now, I don't think its possible any more to create custom chargable items, but I desperately need this functionality.

You're right, its working as intended. I would say that opting to store billing details wouldn't necessarily count as giving consent for continuous billing; but that's a separate issue. But back to the main topic: please could I officially request the ability to disable automatic billing for account credit? Or if its not possible to do it on a granular level, to disable automatic billing entirely for all payment methods.

There is no such setting for account credit, so payment is taken for users automatically who have enough account credit to cover it. EDIT: Sorry I forgot to clearly clarify in the original post that this affected account credit only.

In the automated task generateRenewalInvoices.php, Commerce will try to automatically take payment when a renewal invoice is generated (and a billing address is stored). While I don't think this is wrong necessarily, its not behaviour I desire, and my customers definitely do not want this. The offending line of code is: /* Try to take payment automatically, but *only* if we have a billing address (i.e. the customer has a primary billing address set) otherwise we don't know how we're taxing this and the customer will need to manually come and pay it - we can skip this if tax has not been configured */ if ( $invoice->billaddress OR \count( $availableTaxes ) === 0 ) I would request to have an option to disable this, as right now I have to comment this code out manually to prevent my users from being charged automatically (even if it is to account credit). Kind Regards.

Thanks for reporting it as a bug. I'll await the fix as it does appear to still be an issue even in the latest update.

User ID: 105995 The user is banned now, for obvious reasons, but wasn't at the time. EDIT: I actually think I might know why. Maybe Maxmind changed their API results format, because in the code within Rule.php, the expected syntax is 'riskScore'. But in the maxmind API response, its 'risk_score'. Rule.php: /* Score */ if ( $this->maxmind ) { if ( !$this->_checkCondition( $maxMind->riskScore !== NULL ? $maxMind->riskScore : round( $maxMind->score * 10 ), $this->maxmind, $this->maxmind_unit ) ) { return FALSE; } } Maxmind API response for this particular transaction (redacted): risk_score : 99

No, the user is not a reseller.

Hello I think commerce fraud rules are broken. I had a transaction that came back with a 99% risk score from maxmind, but was approved anyway, despite the second rule in my anti-fraud rule set being to refuse any transaction with a score greater than 55%.

Email ticket support is not primarily how it works. Its an optional component to the ticket system that without, it can continue to function perfectly fine.

Why bother paying your developers when your customers will do it for you for free, right? Same attitude that EA takes with "LiVe SupPorT" aka using paying customers to test their unfinished games for them with no cost.