Paul, Thank you for your reply The query error on, or we didint never open that page after some update in the past modules/addons/BillingExtension/core/BillingExtension_Admin/Clients.php is present also in old module version I think that is a column missing in database Anyway: - the page that generate the error made this query: SELECT t1.id, CONCAT(t1.firstname, " ", t1.lastname) AS clientname, t1.companyname, t1.email, t1.address1, t1.address2, t1.city, t1.state, t1.postcode, t1.country, t1.phonenumber, t1.credit, t1.taxexempt, t1.datecreated, t1.groupid, t1.lastlogin, t1.ip, t1.host, t1.host, t1.status, t1.language, t1.marketing_emails_opt_in AS marketing, t1.email_verified AS emailverified, t2.code AS currency, t3.groupname, t3.groupcolour, t4.billing, t4.reference_person, t4.charge_processing_fees, t4.locktaxexempt, t4.entity , t4.splitpayment , t4.einvoiceitcausale , t4.einvoiceitstatus FROM tblclients AS t1 LEFT JOIN tblcurrencies AS t2 ON t1.currency = t2.id LEFT JOIN tblclientgroups AS t3 ON t1.groupid = t3.id LEFT JOIN bx_clients AS t4 ON t1.id = t4.id ORDER BY t1.id DESC LIMIT 0,200 The table called is this on my db I checked colunms called on query: - t4.billing:OK - t4.reference_person:OK - t4.charge_processing_fees:MISSING - t4.locktaxexempt:OK - t4.entity:OK - t4.splitpayment:OK - t4.einvoiceitcausale:OK - t4.einvoiceitstatus:OK DB TABLE STRUCTURE: CREATE TABLE `bx_clients` ( `id` int(11) NOT NULL, `billing` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `locktaxexempt` int(1) DEFAULT NULL, `entity` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `splitpayment` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `einvoiceitcausale` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `einvoiceitstatus` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `credit_notify` int(11) DEFAULT NULL, `smtp_host` text COLLATE utf8_unicode_ci, `smtp_port` text COLLATE utf8_unicode_ci, `smtp_user` text COLLATE utf8_unicode_ci, `smtp_pass` text COLLATE utf8_unicode_ci, `smtp_ssl` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `smtp_name` text COLLATE utf8_unicode_ci, `smtp_email` text COLLATE utf8_unicode_ci, `smtp_bcc` text COLLATE utf8_unicode_ci, `smtp_logo` text COLLATE utf8_unicode_ci, `smtp_signature` text COLLATE utf8_unicode_ci, `smtp_css` text COLLATE utf8_unicode_ci, `smtp_header` text COLLATE utf8_unicode_ci, `smtp_footer` text COLLATE utf8_unicode_ci, `reference_person` int(11) DEFAULT NULL, PRIMARY KEY (`id`), KEY `billing` (`billing`), KEY `entity` (`entity`), KEY `splitpayment` (`splitpayment`), KEY `einvoiceitcausale` (`einvoiceitcausale`), KEY `einvoiceitstatus` (`einvoiceitstatus`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

Ciao, purtroppo non sono passato a tale ultima versione, pertanto non ho modo di aiutarti al momento o testare. Da quello che hai affermato tuttavia in precedenza >Sono ritornato alla version: 2.2.196 (con un riprirstino della snapshot del disco della macchina linux) >Ma questo errore continua ad apparire. Vuol dire che anche con restore di versione antecedente il problema persiste? Sarebbe paradossale, vorrebbe dire che qualcosa a livello di restore non ha funzionato, e soprattutto ci possa essere un problema lato database con non situazione "pulita" a livello di tabelle e colonne? Presumo ci sia stato una mia incomprensione in merito tuttavia. Su quale versione di whmcs e PHP sei ? Hai potuto verificare se altri moduli in utilizzo nel tuo whmcs possano portare a tale errore/problema ? Per spiegazione dell'errore 500...la query SQL cerca di accedere alla taella alias t4 e colonna chage_processing_fees che non risulta essere esistente nel database associato appunto. Se ho novità per te utili in merito ti aggiornerò. Considerando lo stato dell'arte con tale modulo e suo sviluppatore, se almeno effettivamente ci fosse riscontro tra gli utilizzatori...si potrebbe fare qualcosa. ---- Hi, Unfortunately, I haven’t upgraded to the latest version, so I’m currently unable to help or test this myself. However, based on what you mentioned earlier: I reverted to version 2.2.196 (by restoring a snapshot of the Linux machine's disk) But this error still keeps appearing. Does this mean the issue persists even after restoring to a previous version? That would be quite paradoxical—it would suggest that something went wrong during the restore process, and more importantly, that there might be a database issue where the table and column structure isn’t in a “clean” state. However, I assume there might have been a misunderstanding on my part. Which version of WHMCS and PHP are you using? Have you been able to verify whether any other modules currently in use in your WHMCS installation might be causing this error/problem? As for the 500 error explanation: the SQL query is trying to access the table alias t4 and the column charge_processing_fees, which doesn’t appear to exist in the associated database. If I come across anything helpful for you, I’ll let you know. Considering the current state of this module and its developer, if there were at least some feedback from other users, perhaps something could be done.

nessun altro ha questo problema? è una questione di versioni di PHP? non capiamo perché nessuno risponde, non riusciamo ad aggiornare il nuovo modulo

Ho notato un altro errore nel modulo tentando di accedere alla lista . Sono ritornato alla version: 2.2.196 (con un riprirstino della snapshot del disco della macchina linux) Ma questo errore continua ad apparire.

Venerdì ho eseguito l'aggiornamento di Billing Extension Da: // Product: WHMCS-Bi11ingExtension // Version: 2.2.196 // Identifier: Katamaze // Date: 2024-05-09 Bundle 7.4 & 8.1 A: // Product: WHMCS-BillingExtension // Version: 2.2.204 // Identifier: Katamaze // Date: 2025-04-04 16:49:52 Bundle 7.4 & 8.2 Seguito tutte le istruzioni presenti nel documento https://katamaze.com/docs/billing-extension/26/installing-billing-extension il sistema si è aggiornato ma adesso alcuni url di alcune parti non funzionano e danno un errore 500 ad esempio: cliccando l'url relativo /dl.php?type=i&id=2754&viewpdf=1 funziona mentre il /dl.php?type=i&id=2754 no. Qualche idea su cosa possa fare per risolvere la criticità? Rilevata la versione ionCube Loader®: 12.0.5 nel file di log di php non ho nessun report di errore e nei log del vhost solo dei 500 generici.

We previously used the module unit WHMCS updated to 8.1. We then contacted Katamaze without success as we seems to be ignored. We stopped using the module. Since then they seem to have "updated" the module to "work" with WHMCS PHP 8.1 but still same issues. Each time we purchase the module again but still broken and no support or response. Seems all they are doing is taking money without fixing the issues customers are experiencing. There is also no open source module that we can purchase to try and fix these issue. Maybe someone here can assist in getting the below error resolved as it seems Katamaze is not interested in customer support.... Oops! Something went wrong and we couldn't process your request. Please go back to the previous page and try again. For additional assistance, please reference the WHMCS TroubleShooting Guide » Error: Attempt to modify property "status" on null in /html/modules/addons/CommissionManager/core/CommissionManager_Admin/Commissions.php:122 Stack trace: #0 /html/modules/addons/CommissionManager/core/CommissionManager_Admin/Commissions.php(25): CommissionManager\CommissionManager_Admin\Commissions->AdditionalData() #1 /html/modules/addons/CommissionManager/CommissionManager.php(128): CommissionManager\CommissionManager_Admin\Commissions->__construct() #2 /html/clickstaff/addonmodules.php(0): CommissionManager_output(Array) #3 {main}

Hi there. That script is very useful! Thanks. I've added a little modification. This script will not show a notification for the invoices that are due the same day, but not expired yet. All the best <?php /** * Admin Stats for WHMCS v8 * * @package WHMCS * @copyright Katamaze * @link https://katamaze.com * @author Davide Mantenuto <info@katamaze.com> */ use WHMCS\Database\Capsule; add_hook('AdminAreaHeaderOutput', 1, function($vars) { $v8 = Capsule::select(Capsule::raw('SELECT value FROM tblconfiguration WHERE setting = "Version" LIMIT 1'))[0]->value; if (explode('.', $v8)[0] != '8'): return; endif; $showZero = true; $ordersTotal = Capsule::select(Capsule::raw('SELECT COUNT(t1.id) AS total FROM tblorders AS t1 LEFT JOIN tblorderstatuses AS t2 ON t1.status = t2.title WHERE t2.showpending = "1"'))[0]->total; $invoicesTotal = Capsule::select(Capsule::raw(' SELECT COUNT(id) AS total FROM tblinvoices WHERE status = "Unpaid" AND duedate < CURDATE() '))[0]->total; $ticketsTotal = Capsule::select(Capsule::raw('SELECT COUNT(t1.id) AS total FROM tbltickets AS t1 LEFT JOIN tblticketstatuses AS t2 ON t1.status = t2.title WHERE t2.showawaiting = "1" AND merged_ticket_id = "0"'))[0]->total; if (!$ordersTotal AND !$invoicesTotal AND !$ticketsTotal): return; endif; $notificationsLabel = AdminLang::trans('setup.notifications'); $orderText = AdminLang::trans('stats.pendingorders'); $invoiceText = AdminLang::trans('stats.overdueinvoices'); $ticketText = AdminLang::trans('stats.ticketsawaitingreply'); if ($ordersTotal OR $showZero) { $pendingOrdersJS = <<<HTML $('#v8fallback').next('ul').append('<li><a href="orders.php?status=Pending" data-toggle="tooltip" data-placement="bottom" title="{$orderText}" data-original-title="{$orderText}" style="word-wrap:break-word"><small><span class="ico-container"><i class="fad fa-shopping-cart"></i></span><span class="v8fallback">{$ordersTotal}</span> {$orderText}</small></a></li>'); HTML; } if ($invoicesTotal OR $showZero) { $overdueInvoicesJS = <<<HTML $('#v8fallback').next('ul').append('<li><a href="invoices.php?status=Overdue" data-toggle="tooltip" data-placement="bottom" title="{$invoiceText}" data-original-title="{$invoiceText}" style="word-wrap:break-word"><small><span class="ico-container"><i class="fad fa-sack-dollar"></i></span><span class="v8fallback">{$invoicesTotal}</span> {$invoiceText}</small></a></li>'); HTML; } if ($ticketsTotal OR $showZero) { $awaitingTicketsJS = <<<HTML $('#v8fallback').next('ul').append('<li><a href="supporttickets.php" data-toggle="tooltip" data-placement="bottom" title="{$ticketText}" data-original-title="{$ticketText}" style="word-wrap:break-word"><small><span class="ico-container"><i class="fad fa-question-circle"></i></span><span class="v8fallback">{$ticketsTotal}</span> {$ticketText}</small></a></li>'); HTML; } return <<<HTML <script type="text/javascript"> $(document).on('ready', function() { $('ul.right-nav').first('li').prepend('<li class="bt has-dropdown"><a id="v8fallback" href="#"><div class="badge-container"><i class="fas fa-exclamation-triangle always"></i><span class="badge"><span class="fas fa-times"></span></span></div><span class="visible-sidebar">&nbsp;{$notificationsLabel}</span></a><ul class="drop-icons"></ul></li>'); $("*[id=\'v8fallback\']").on("click", function(e) { e.preventDefault(); $(e.currentTarget).parent("li").toggleClass("expanded"); }); {$pendingOrdersJS} {$overdueInvoicesJS} {$awaitingTicketsJS} $('#v8fallback').next('ul').css({"width": "340px", "left": "-134px"}); $('span.v8fallback').css({"font-weight": "700"}); }); </script> HTML; });

I switched from a Serverplan dedicated server to a Siteground Hosting plan. The server provider Sitgroung replied to me: "We provide Managed Hosting services and I am afraid that it will not be possible to change the MySQL configuration on request. Here at SiteGround, we strive to provide the best possible security and services. All our servers are protected by an elaborate multi-layered security system. We have a Security team that is constantly looking for changes that need to be made to our security system and they have deemed that MySQL on our servers should use Strict Mode ." the MySQL version is 8.0 While for the Billing Extension module it is at version 2.2.200 WHMCS version is 8.11.2

Hello, Essentially, strict mode needs to be disabled to ensure WHMCS functions properly. Here's the documentation on this topic: https://docs.whmcs.com/system/database-and-storage/database-and-storage-tutorials/disable-mysql-strict-mode/ Have you switched providers and moved to a dedicated solution (VPS/dedicated server)? What version of MySQL are you using? Also, which WHMCS version and Billing Extension version do you have? It would be great to see a comeback from Kian, a brilliant developer with excellent modules of his own.

I have the Katamaze add-on for electronic invoicing. Previously I used a dedicated server on serverplan, now I have moved everything to Siteground. Since then I have a problem "PDOException: SQLSTATE[HY000]: General error: 1525 Incorrect DATE value: '0000-00-00'" I contacted my server and they said: "The error you are getting is due to SQL Server operating in strict mode, which does not allow '0000-00-00' to be used as a valid date. Instead of disabling strict mode, which is generally not recommended to maintain database integrity, you can resolve this issue by addressing the root cause in your code or database schema." I should therefore insert instead of '0000-00-00', the value NULL or a valid default date. I wrote to support but they do not respond. What can I do?

I don't have any experience with this particular module, but the error is common when upgrading from PHP 7.x to PHP 8.x and typically is a difference in syntax or that you are incorrectly mixing string and array functions.

Hi, We work with Katamaze Billing Extention for a while, since few days and without changing version we get a validation error on every created invoice. Invoices are still created although. We changed invoice number variable and increment with same issue TypeError: Cannot access offset of type string on string in /var/www/WHMCS/html/modules/addons/BillingExtension/core/BillingExtension_Admin/Hook.php:3893 Stack trace: #0 /var/www/WHMCS/html/modules/addons/BillingExtension/core/BillingExtension_Admin/Hook.php(4523): BillingExtension\BillingExtension_Admin\Hook->Warnings() #1 /var/www/WHMCS/html/modules/addons/BillingExtension/hooks.php(647): BillingExtension\BillingExtension_Admin\Hook->SequentialNumbering() #2 [internal function]: BillingExtension_InvoiceCreation() #3 /var/www/WHMCS/html/vendor/whmcs/whmcs-foundation/lib/Hook/Manager.php(0): call_user_func() #4 /var/www/WHMCS/html/vendor/illuminate/support/Facades/Facade.php(261): WHMCS\Hook\Manager->run() #5 /var/www/WHMCS/html/vendor/whmcs/whmcs-foundation/lib/Billing/Invoice.php(0): Illuminate\Support\Facades\Facade::__callStatic() #6 /var/www/WHMCS/html/includes/quotefunctions.php(0): WHMCS\Billing\Invoice->runCreationHooks() #7 /var/www/WHMCS/html/iitadmin/quotes.php(0): convertQuotetoInvoice() #8 {main} Does that ring a bell to someone? Thanks Mastly

And it's down again... It annoying that if Katamaze goes down all sites using the modules goes down to, especially when its so hard to get into contact with them.

System was back in business. I hope there will be updates, informations, tweets, or other communications in case there are any planned or unplanned maintenance activities on Katamaze systems. Thanks

Yes, I remember that moment well. Everything should have been at a standstill since about 00:50 today, the inability to have communication, news, a simple tweet about the situation at hand is a huge problem.

I remember the very same issue happened years ago, during a system maintenance (Katamaze changed/updated its server, it should have been just a matter of an hour or so, but something went wrong and everything was down for 12 hours or so...)

Hello, it is a huge problem, I confirm that we also obviously have the problem being down katamaze.com as a whmcs system. Help

... and, since it is down, also our whmcs site (which uses katamaze's billingextension) is down with a hard-to-understand-and-investigate SQL error... I guess we are not the only ones experiencing this issue...

Hi, Yes I have the same problem. BX doesn't work with php 8.1 even though they promise it in the product description. You must use php 7.4. BX support is terrible and they haven't been able to fix the problem in years.

I have the same problem. Support is ignoring me.

Ciao, per il cron ho risolto tornando ad utilizzare la versione 7.4 di php Però continuo a non riuscire a vedere la versione come correttamente aggiornata ed allo stesso tempo non riesco ad inviare la fattura dall'area amministratore usando il modello "Invoice Creation" dalla pagina della fattura. Invece dal cron le email delle nuove fatture partono regolarmente...mistero

Avete avuto modo di risolvere per caso?

Same issue here, but with a different version: Anyone have solved?

Qualcuno riscontra il medesimo problema? Nella documentazione non è indicato come inserire uno stato in EU. Lo stesso problema è presente con le Isole Canarie che sono ES ma considerate come EXTRA EU

Having the same issue, did you figure out what is causing it?