Leaderboard

I’ve added: $allow_adminarea_invoice_mutation = true; Honestly, this change is a nightmare for our daily workflow. We need to edit invoices every day, and with this new restriction, what used to be a simple operation has become an everyday problem. In my opinion, this was a very bad decision from a usability point of view, especially for companies that manage billing operations daily and need flexibility when handling invoices.

Glad to see more customers speaking up about this… it’s a simple, fixable issue. All they need to do is keep allowing the switch: Add ($allow_adminarea_invoice_mutation = true;) in your WHMCS configuration.php . WHMCS choosing a one-size-fits-all strict model is what’s really causing the pain… let us decide if we need to deal with regional compliance and added accounting complexity, not force it on everyone.

You should reinstall the vendor directory for the WHMCS version you are running

I’m trying to install ModulesStack from https://modulesstack.com/installation/ I followed the steps, but I’m not sure if I’m doing it correctly. The installer runs, but the modules don’t appear in my admin panel. Has anyone successfully installed it? What am I missing?

Hello people, I had this exact problem as well, it was caused by Resellerclub mods but I found the fix. You need to update the module/registrars folder as well as /modules/addons/resellerclubmods_core These files are available here: https://www.resellerclub-mods.com/whmcs/login From here download logicboxes_registrars_3.19.0_PHP_7.4_8.4.zip and resellerclubmods_core_1.9.0_PHP_7.4_8.4.zip Then upload it to your installation of WHMCS and you should be good to go! Thanks Dave Geoghegan https://www.webworld.host

Very creative.

Not everyone wants SAAS solutions, or keeping data with a third party due to concerns about client data. I'm one of those businesses.

If you’re going to market a platform as a professional billing system, then act like one. That means involving certified accountants, validating against real-world accounting standards, and subjecting every financial change to rigorous testing before it ever reaches production. Anything less isn’t just an oversight — it’s negligence. Rolling out changes with this level of impact, only to expose fundamental bugs, is completely unacceptable. Billing systems are not feature playgrounds. They are the financial backbone of businesses that rely on accuracy, stability, and trust. What’s most concerning is not just the presence of these issues — it’s that they made it through your release process at all. That speaks to a breakdown in quality control, testing discipline, and respect for your user base. We’ve deliberately held off upgrading to 9.x while waiting for critical modules to catch up. Based on what we’re seeing now, that decision looks more justified than ever — and we’ll be waiting considerably longer. If you want to be taken seriously in this space, raise the bar. Because right now, this isn’t it.

All the more reason to have had a beta, John.

It's possible to do . A query like this will do it: $productid = "INSERT PRODUCT ID HERE"; foreach (Capsule::table('tblhosting')->WHERE('packageid', '=', $productid)-> WHERE('domainstatus', '=', 'Active')->get() as $orderlist) { $userid = $orderlist->userid; $server = $orderlist->server; $domain = $orderlist->domain; $paymentmethod = $orderlist->paymentmethod; $billingcycle = $orderlist->billingcycle; $nextinvoicedate = $orderlist->nextinvoicedate; $amount = $orderlist->amount; print ("$userid: $server : $domain: $paymentmethod: $billingcycle: $nextinvoice: $amount<br />"); } Implementation is going to be on you, but this will get you started