Leaderboard

While I understand that bugs are part of any Release Candidate cycle, it's concerning that we are still discussing basic optimization issues like proper OPcache support. And let's not even get started on the fact that we still don't have 100% native Nginx support. This becomes particularly ironic with the introduction of the new WHMCS Cloud Solution. With cloud hosting, the resource costs are on their side, so you'd think they'd be rushing to support Nginx to reduce their own infrastructure expenses. It's like being sold a high-performance engine but being told you have to power it with hamster wheels. Maybe once their bills start rolling in, Nginx support will suddenly become a priority. This all points to the bigger issue: the development velocity. Core development feels like it's just about "keeping the lights on" (PHP/ionCube updates) rather than actual innovation. This stagnation has allowed third-party developers like ModulesGarden to build entire businesses by selling us functionality that should have been in the core a decade ago. When you look at the "Total Cost of Ownership" license fees + necessary third-party modules, the value proposition is slipping. Newer platforms like Upmind are entering the market with an API-first architecture and modern features built-in from day one. If WHMCS continues to outsource innovation to the community while raising prices for maintenance updates, that competitive threat is going to become an exodus very quickly. We need core features that match the modern hosting landscape, not just compatibility patches.

I never imagined that a simple update could introduce so many problems — and even worse, apparently without proper testing. It is absolutely ridiculous for a financial management system to have its own financial logic broken. In the last 24 hours, I finally received a response on the open support ticket, along with a so-called “patch” (attached). In practice, this patch only fixes the reports by hiding the incorrect ledger entries. However, in several other areas of the system, the incorrect postings are still happening. For example, the “Transactions” tab inside the client profile continues to show wrong values and misleading entries. So, in short, this patch does not actually fix the root problem — it only masks it in specific reports. For now, apply it if you want to slightly reduce the visible impact, but be aware that the financial logic is still broken in multiple parts of the system. At this point, we are seriously considering rolling back to a previous version — or even migrating away from WHMCS entirely. Year after year, the pricing increases exponentially, while the quality of support continues to decline and critical issues like this keep happening. The current level of instability and support simply does not justify the price they are charging anymore. whmcs_v9.0.0-supporthotfix.1_750a0b77ff.321_WHMCS-24949.zip

Hi WHMCS ecosystem developers! I am excited to share an early heads-up about the upcoming WHMCS 9.0 release by the end of 2025 - a major update that brings important changes to the platform’s technical requirements. As part of this release, several core dependencies will be updated, and minimum system requirements will be increased. These changes are designed to improve performance, security, and compatibility with modern PHP standards. Key Updates in WHMCS 9.0: Minimum PHP version: 8.2 Recommended PHP version: 8.3 Minimum ionCube Loader version: 13.0.2 or higher Recommended ionCube Loader version: 14.4.0 or higher Updated dependencies: A number of underlying libraries and components have been upgraded. Some notable changes include: Smarty v3.1.48 —> v4.3.4 Legacy Smarty Tags are being deprecated and will no longer function in 9.0. Smarty Template Objects (including their use in plugins) will no longer be supported. guzzlehttp v7.4 —> v7.4.5 illuminate v7.x —> v9.0 I have attached a provisional list of dependency changes to this post. Please also use this thread to provide your feedback and ask questions of the Development Team regarding these requirement and dependency changes. These changes will require action from module developers to ensure continued compatibility. We recommend reviewing your module code and preparing for updates ahead of the release. We’ll be sharing more details, including a release window, definitive changelog and developer guidance, between now and the end of 2025 to help you get ready. Thank you for being a valued part of the WHMCS ecosystem. We appreciate your continued support and look forward to working together to make WHMCS 9.0 a successful release. whmcsv90_composerlock_provisional.txt

Okay, maybe I was too quick about credit notes. It seems a lot of the features are "coming soon™️". This is not a Release Candidate lol. This is not even alpha. This is internal development. Nothing can convince me that this release didn't just happen because WHMCS promised us a release in December.

add this line to your configuration.php it will go back to normal behavior $allow_adminarea_invoice_mutation = true;

Yes, I agree they should be an option

This is what one WHMCS Staff tell me You have the option to make the change to your WHMCS configuration.php file and add the line $allow_adminarea_invoice_mutation = true;, but it is your decision whether to do so. When this line is present in your configuration.php file, the system will permit most of the changes to invoices that existed before WHMCS version 9.0, notably: Line items can be changed for invoices in any status (when in the "Manage" mode and with the correct admin user permissions set). All attributes are available in the Options tab regardless of the invoice status (when in the "Manage" mode and with the correct admin user permissions set). Payments can be applied in the Add Payment tab regardless of the invoice status (with correct admin user permissions set). Please note that using this configuration line ($allow_adminarea_invoice_mutation = true;) in your WHMCS configuration.php The file is highly discouraged, as it may permit changes that are not compliant with regional/country business regulations and complicate accounting. To bring awareness of this, a Warning health check will appear in the System Health Check summary when the value is present in your WHMCS configuration.php file. Additionally, all “full administrators” will see an Admin Warning banner (which can be dismissed up to every fortnight). You may want to add it temporarily if you do need to make the changes listed above, which were changed in WHMCS version 9.0 to improve invoice management and ensure tax compliance by keeping invoice records consistent. If you do not see any warnings or have issues with editing invoices or changing their status when this line is added, please let us know. Starting with WHMCS version 9.0, non-Draft invoices are immutable. This means you cannot edit transactions (now listed under the Ledger section on the invoice), add or remove items, or modify descriptions on an invoice once it’s no longer in the "Draft" status. This change is intended to improve invoice management and ensure tax compliance by keeping invoice records consistent. For more information on invoice management in WHMCS version 9.0, please refer to the following documentation: https://docs.whmcs.com/9-0/billing-and-invoicing/invoice-management/

Yeah, except for adding AI to domain search, this release doesn't really provide on any of the other promises. Credit notes doesn't work either. When you cancel an invoice, WHMCS just adds a transaction to the invoice. If the invoice has a total of $100, WHMCS just adds a transaction of $100 and cancels the invoice. There's no credit note or anything.

How WHMCS have set this as a RC instead of a Beta is insane. It's a huge upgrade in terms of it's impact on themes/modules. No beta, no reply from WHMCS, no forums specific to v9.

Your process sounds good apart from WHMCS. I would never recommend trying to import tables to new files. You need to update your existing install as normal. You can update from your version but you may have more luck doing a manual update. Backup everything, upload the new v8.13 files, adjust your hosting/server settings to meet the requirements (e.g you may need to update PHP) then run the installation script.

@BENELUX, Today's the day!! https://blog.whmcs.com/133775/whmcs-90-release-candidate-out-now

This week or next! It sure would be nice to double the size of the engineering team temporarily for one release every few years!

@stormy, I'm glad to hear the e-invoicing feature will be a real value add for you. We are working with expert solution-providers in this space, so we're confident about delivering an easy to use and compliant solution with the broadest coverage. @andp97, Yes, by the end of the year in a pre-release version of WHMCS you will have access to this new feature. This bullet point actually describes two significant features which we're very excited about: 1. A RESTful API which provides access to the product catalogue and shopping cart logic. This will provide a suite of new endpoints to get product catalogue information, add, manipulate and get information about items in the cart (including price breakdowns and totals) and much more, all without touching the cart.php file or PHP session data. This means that power users could create their own highly-bespoke frontends whilst WHMCS handles the maths in the background, before seamlessly passing visitors to the checkout page to complete payment. 2. A brand new thin client powered by the aforementioned new API capabilities, providing a thoroughly modern purchase experience based on Vue.js. I've attached a sneak peak below. The new BuyFlow is a compiled Single-page application, meaning the layout isn't manipulated through templates, but you will be able to customise the colours to match your theme through a custom.css overrides file. The shopping cart as it exists today (cart.php and order form templates) isn't going away and will still be available if you'd like to stay with the familiar experience. Stay tuned to our blog and socials over the coming weeks for more information!

Hi @venkat.j, The current latest version is 8.13. This behaviour suggests the dates were set to 00/00/0000, either by an admin (in which case there should be an entry in the client's Log tab) or by a rogue after-market module (in which case there probably wouldn't). You can edit the date fields to set the actual dates and click Save Changes. The correct dates will be stored.

Hi all, In 8.13 a small improvement was made to the accounting of refunded mass-pay invoices. Prior to this the totals of mass-pay invoices were included in the overall income statistics, but now they are excluded as it's already accounted for by the original invoices.

But you did ask them, and not by just posting here? EDIT: This is a bit old now, but a fast search on this board found:

Hello @ThemeMetro This is a known issue, and we have published a HotFix. For more details, please review the following. Apologies for any inconvenience. Kind regards, Stephen.

Hello, Not at all and it's highly recommended, to change the admin path.

Every WHMCS administrator knows the struggle: adding an announcement, writing a knowledgebase article, or placing an image on a product page often requires more effort than it should. Typically, you have to open an FTP client, navigate through folders, upload the file, and then manually copy the URL. This process is time-consuming and disrupts your workflow. To eliminate this overhead, we have developed a simple yet highly functional solution: Media Manager. Zero-Installation Architecture The greatest advantage of this tool is that it requires no module installation or complex configuration. Consisting of a single PHP file (media-manager.php), you simply upload it to your WHMCS admin directory, and it is ready to go. Native WHMCS Security Instead of building a separate security layer, we integrated the tool directly with the WHMCS admin authentication system. This means that no one can access this file without an active administrator session. It doesn't act as a standalone, vulnerable media manager; it functions as a secure part of your existing panel. What Can You Do? The tool provides all the essential features needed for daily management tasks: Maintain organization by creating and deleting folders. Perform fast file uploads and deletions. Rename files on the fly. Copy the direct URL of any uploaded file with a single click. For administrators who frequently add images to knowledgebase articles, the "Login to FTP, find directory, upload file, copy path" cycle is now a thing of the past. How to Get Started There is only one minor adjustment required before use: open the media-manager.php file and replace the "websiteniz.com" placeholder with your own domain name. Once this edit is made, your system is fully prepared. Our goal wasn't to build a massive, complex media library. Instead, we aimed to provide a fast, secure, and practical file management tool within the WHMCS environment. Born out of necessity and tested in the field, this tool is now available for everyone. Github project: Whmcs Media Manager Website: www.megabre.com

Thank you for your reply. I can't attach a screenshot because I don't have permission to edit the topic :) I'll leave it here, you can download and take a look.

Yeah this is a nightmare

I have updated to WHMCS 9 In vendor files the folders was updated, but the folders not required anymore was not removed by the automatic update tool as when I compare WHMCS 8,13 and 9 they are removed. So remember to remove these manually people true sonata-project Facebook container-interop My questions why does the update process not clean and remove everything that is "old". What happend with the quality of the WHMCS releases .. .

I think you guys may be dramatically underestimating what AI is capable of, but I suppose we shall see. As for the post being suitable or not, Webpros has done everything in their power to alienate their client base - this type of post is the inevitable consequence of that.

Hey, after upgrading from 8.x to 9.x, I'm getting a strange issue: if I go to the configuration >> Sign-in option, Activate any social login, add the app ID and secure key, and save it, I get a strange issue. It shows the integration is activated; in the console, it returns success. But when I refresh the page, the integration reverts to the inactive state. I also don't see any active buttons on the Login and Sign-in pages, nor do I get any log or error message.

You may want to check in softaculous you may have the auto update turned on. Go into Softaculous find your install click on edit details auto upgrade select do not auto upgrade. With regards to 9.0 their will still be a lot of developers slightly behind. WHMCS didn't exactly give developers alot of notice with regards to the changes.

Whmcs doesn’t autoupdate - someone is initiating the update. You’re using addons that are not compatible- yet. Logos is not compatible Roll back and stay there till all your addons declare compatibility with v9.

Thanks a lot for the kind words! Based on our testing so far, the bigger challenges in WHMCS 9.0 aren't so much about the new checkout UI, but about changes deeper in the core. WHMCS updated core libraries and parts of their API, which means existing integrations often need to be adjusted. There are also changes in how late fees and credit payments work, and those can affect billing, including recurring charges. These are some of the areas where modules, both off the shelf and custom ones, may not behave as expected if not updated. We shared a more practical take on this here, based on our ongoing work with WHMCS 9.0. If you're running custom functionality and want to be sure everything works the way it should, feel free to contact our team. We'll gladly talk it through and help you understand what, if anything, needs adjusting.

Already opened up a bug (ticket DVZ-331740), just creating this here as well I have a couple of really, really old WHMCS versions (some at 7.1.x), deliberately, to do testing and whatnot for clients. Since they're dev installs and locked down to me only, I'm not terribly worried about threats there. Tried to upgrade one of the 7.1.x versions to 9 and couldn't do so. 'Cannot read configuration file' the system said Rolled back backup, upgraded to 8.13, then to 9, worked like a charm Just a heads up for those that may be in the same position. Looks like some earlier versions aren't available for a direct upgrade

What I find somehow strange after being using WHMCS for 20 years.. when there was only 2-3 people in the company... bugs was fixed quickly often the same day. Now that I have a list of bugs reported many of them with 1 min solutions to implement, and they still doesnt get implement in X versions of whmcs 8x and still not fixed in WHMCS 9. So I dont know if being a large owned company is always a good thing. Just in December alone me and other people I work with found 3 new bugs of things that has been working since whmcs 5 and suddenly not working and per documentation should work.. I am actually concerned that the developing department / team doesnt have good working structure as they introduce bugs that should not be there that has been working for years. This make us need to use more time on testing before each upgrade and time testing is also a huge cost.. whmcs. should going forward be better in quality and also fixe the backlogs of bugs.

Hi @kon, I'm pleased to hear you like the direction we're going with Nexus cart! We're going to continue with this work in 9.1 and bring this same design language to the rest of the purchase flow. The RDAP implementation has been rescheduled to v9.2. This is because we have prioritised security and financial compliance features in releasing 9.0 and will continue this focus in the subsequent 9.1 (eg. credit notes, e-invoicing, improved VAT compliance).

I must have something set up incorrectly because the Login to DirectAdmin button doesn't work if the passwords don't match. If the client changes their password on DirectAdmin then the button only directs them to the login screen on the DirectAdmin server.

... and contact WHMCS support to have the development licensed reissued. ... and then rename the directory back to make your development installation match your production installation as close as possible, once this issue is fixed, and then contact WHMCS support to have the license reissued again. @WHMCS John WHMCS really goofed this RC. It's released just before the holidays and will hit stable very shortly after everyone gets back to work. I hope you understand why developers are frustrated with this.

WeWe is a project-focused WHMCS service provider supporting hosting companies and digital businesses with structured, reliable WHMCS implementations. Our team has multi-year hands-on experience with WHMCS, backed by solid technical resources through our sister company, WebNIC, which has been operating in this industry for over a decade. This allows us to deliver not only development, but also proper project coordination, quality control, and long-term maintainability. Our WHMCS Services: • WHMCS Custom Module & Addon Development • WHMCS System Setup, Migration, and Optimization • Payment Gateway & Third-Party Integrations • Domain Registrar & API Integrations • Server Integrations (cPanel, Plesk, DirectAdmin) • Custom Hooks & Workflow Automation • WHMCS Upgrade, Refactoring, and Performance Improvement • Client Area & Template Customization • Ongoing WHMCS Maintenance & Support Why Work With WeWe: • Strong focus on project management and delivery quality • Practical WHMCS experience across real production systems • Reliable resources with long-term industry background • Clear communication and structured execution • Suitable for both one-off projects and ongoing support If you are planning a WHMCS upgrade, custom integration, or need a reliable partner to manage your WHMCS project end-to-end, feel free to reach out to us at muhammad.m@wewe.cc.

It's at https://whmcs.test/admin/index.php?rp=/admin/billing/billingnote/credit/1 Also, the view invoice page in the client area is completely broken. Trying to load stuff that doesn't exist. (This is a fresh install btw)

Announcing WHMCS 9.0 Release CandidateWe're excited to announce the availability of the WHMCS 9.0 Release Candidate. This release marks the completion of feature development for WHMCS 9.0 and the final step before it becomes generally available. WHMCS 9.0 is a compliance-focused release, introducing a range of updates and enhancements designed to help businesses stay aligned with evolving regulatory requirements while continuing to deliver a seamless experience. WHMCS 9.0 includes the...View the full blog post

We may be able to help if you still require it.

I'd suggest that your average user that grabs a script like this will not change anything in it, especially since they're not (apparently) being told to. I've seen users not change a "CHANGE_THIS" in scripts, then ask why it's not working. I've also seen them ignore the "remove this file after use", so relying on that might not be advisable either. Best practice is not to spoon feed, keep this outside the publicly accessible directories, and instead of that simple URL parameter you reveal, make it a "secret key" that is defined within the script, with a note to change it (or better still they make their own that must be x long and have this or that in it; if empty, fail with "key needed"). Safety first.

Feel free to contact us for support: https://radwebhosting.com/support

Il Ballot SC-081v3 è una proposta dello CA/Browser Forum che riduce la durata massima dei certificati SSL/TLS, passando da un periodo di validità fino a 3 anni a un massimo di 12 mesi. Gradualmente verranno introdotti periodi di validità più brevi. Questo cambiamento impatta direttamente la gestione dei certificati e la sicurezza dei siti web. Perché il cambiamento? Migliore protezione da compromissioni Aggiornamenti crittografici più veloci Allineamento agli standard del settore Prima vs Dopo SC-081v3: Validità certificato: da fino a 3 anni → 12 mesi Sicurezza: buona → maggiore Rinnovi: meno frequenti → annuali obbligatori Gestione: semplice → automatizzata consigliata Roadmap rapida: 1️⃣ Q4 2025: emissione certificati 12 mesi 2️⃣ Q1 2026: aggiornamento software gestione SSL 3️⃣ Q2 2026: tutti i nuovi certificati conformi WHMCS già gestisce riemissione e distribuzione automatica dei certificati SSL a fine ciclo, normalmente ogni 12 mesi, supportando certificati fino a 3 anni. Grazie alla collaborazione con Digicert, il team introdurrà le modifiche necessarie per rispettare i periodi di validità più brevi ben prima che diventino obbligatori. 💡 MarketConnect continua a offrire totale automatismo e facilità di gestione, aggiornandosi proattivamente agli standard industriali e garantendo ai clienti sicurezza e tranquillità senza interruzioni.

can you maybe release an update to 8.13 to add a tool similar to the PHP compatibility tool that shows what files use these old components and won't be compatible? it'll help hosts like us that rely in multiple vendors plugins understand who we need to reach out too to ensure they're getting WHMCS v9 ready.

This is caused by misconfigured WHOIS servers. You need to ensure the correct string for "available". When dealing with this error, you can navigate to the WHOIS interface in WHMCS admin and check some WHOIS responses for domain that status is known For example, you can use "thisdomainisn0tregistered.org" as a test for getting the appropriate response of WHOIS for a domain that is available for registration. Then, you need to incorporate your findings in the whois.json file. Configuring the appropriate values in this manner will ensure that your clients are given the opportunity to register the domain which is "available" and configured for sale in your WHMCS. Example { "extensions": ".org", "uri": "socket://whois.publicinterestregistry.net", "available": "Domain not found." }

Hello folks, I'm developing a custom payment gateway module and need to trigger a hook after the admin clicks "Save Changes" on the gateway configuration page (configgateways.php). I can see the POST request with the correct credentials (like App ID and Token) in my browser's dev tools. However, my hook isn't being triggered at all. ChatGPT suggested a GatewayConfigSave hook might exist, but I couldn't find any official documentation about it. I also tried AdminAreaPage and similar hooks, but none are reliably triggered with the config save event or POST data. Has anyone else run into this issue? Is there a recommended or undocumented hook to use when saving a gateway's settings?

You should write your own. AI is not to be trusted.

You can remove the Edit with Sitejet Builder link from the left sidebar menu under the Actions sidebar when logged in as a client and looking at the Product Details page using this hook code: <?php use WHMCS\View\Menu\Item as MenuItem; add_hook('ClientAreaPrimarySidebar', 1, function (MenuItem $primarySidebar) { $actionsMenu = $primarySidebar->getChild('Service Details Actions'); if ($actionsMenu instanceof MenuItem) { foreach ($actionsMenu->getChildren() as $child) { if (strpos($child->getLabel(), 'Sitejet') !== false) { $actionsMenu->removeChild($child->getName()); } } } }); See the attached screenshots showing this custom hook file in place in the /includes/hooks/ directory. The screenshots show that this link is no longer there after this hook code is added. You would create a file named "remove_sitjet_link.php" and add the above code into it, and upload it to your /includes/hooks/ directory. I tested this with WHMCS version 8.13.1. I hope that this helps someone.

Great list of modules. Thanks for sharing it with us.

Hello Jackson, I have used QuickBooks Payment Gateway Module for my WHMCS store. This module is very easy to use and supports credit and debit card payments across different countries United States, Canada, United Kingdom, Australia, and New Zealand. The best thing is, you will get 7 days free trial before buying the premium version here. Get it from here - https://members.modulesstack.com/index.php?m=product_page&pid=18&name=quickbooks-payment-gateway-for-whmcs Let me know if you need any assistance. Thanks

I haven't noticed any difference, enom support still sucks just as much as it always has.

Technically the other way round - opensrs bought enom and that’s when enom fell apart

Here's the fix! https://whmcs.community/files/file/204-gocardless-eur-payments/

Hello @Blasgo Thanks for your post, if you have registered the domain with your registrar then you will need to follow the "Manual Domain Entry Only" process To add a domain on its own without a product, follow the steps below: If you haven't already, create the client by navigating to Go to Clients > Add New Client. On the client summary page, click the "Add New Order" link in the Actions panel The client will be preselected, so you should fill out the rest of the form - begin by choosing the payment gateway you want the client to pay with Leave the Product/Service dropdown menu set at None Leave the Billing Cycle dropdown menu set at Monthly Enter the domain in the Domain text field and select Register as the Domain Registration Option (even though you aren't intending to register it today) Choose the number of years you next want the client to be invoiced for at the time of renewal and tick any addons the user has for their domain Ensure both tick boxes for sending an order confirmation and generating an invoice are unchecked so the user is not emailed about the order you are adding Finally, set the Order Status dropdown to Active and then click the submit button to add the order to WHMCS You will now be shown the order screen summarising the details of the order you just added Now as the final step, you must go to the domain's information page to enter the correct next due and expiry dates as well as selecting the registrar the domain is registered with if using one of the built-in registrars. To do this, from the order screen, click on the link in the Item column of the items ordered - this will take you straight to the details screen.