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

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.

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.

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 .. .

This new "feature" is terrible and is a fundamental change. This feature does not conform to most businesses and should be an option if there are other regulatory purposes in other countries. It severely limits the flexibility of the system and limits its function. I highly recommend a switch to disable this new "feature".

Stepping back from this specific issue, it does feel like a broader pattern within WHMCS rather than an isolated problem with NexusCart. I do not have insight into WHMCS internal development processes, and this is not intended as criticism of individual contributors, but from a customer and integrator perspective the overall direction can be difficult to follow. Over recent releases, we have seen recurring regressions, incomplete fixes, and features that appear to ship without being fully validated across real world installations. When combined with limited transparency around known issues or roadmaps, it creates the impression of fragmented development and weak internal communication. WHMCS is a mission critical platform for many businesses, so stability, predictable releases, and timely fixes are just as important as new features. At times it feels like significant bugs or long requested improvements are either delayed for extended periods or quietly deprioritized, which makes long term planning and confidence in upgrades challenging.

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.

Growing a business with limited resources is tough, but the right marketing tools can make it much easier. They help you save time, avoid doing the same tasks over and over, and keep everything in one place so you're not constantly jumping between different apps. Think about all the things that go into marketing: setting up a website, posting on social media, sending emails to customers, and keeping track of projects. Doing all of that manually takes a lot of time. But with the right tools,...View the full blog post

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.

ETA: Estimated Time of Arrival. By definition, not exact. 😉

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

Hello, It's very easy to resolve with Hook, just do Create a hook file at: whmcs/includes/hooks/invoice-lineitem-date.php <?php use Illuminate\Database\Capsule\Manager as Capsule; use Carbon\Carbon; add_hook('InvoiceCreationPreEmail', 1, function ($vars) { $invoiceId = (int) $vars['invoiceid']; $inv = Capsule::table('tblinvoices')->where('id', $invoiceId)->first(); if (!$inv) { return; } $dateText = Carbon::parse($inv->date)->format('d-m-Y'); $items = Capsule::table('tblinvoiceitems') ->where('invoiceid', $invoiceId) ->get(); foreach ($items as $item) { $isBillableItem = ($item->type === 'Item'); if (!$isBillableItem) { continue; } $newDescription = $item->description; if (strpos($newDescription, '{DAY}') !== false || strpos($newDescription, '{MONTH}') !== false || strpos($newDescription, '{YEAR}') !== false) { $newDescription = preg_replace( '/\{DAY\}\s*-\s*\{MONTH\}\s*-\s*\{YEAR\}/i', $dateText, $newDescription ); } else { $newDescription .= " ({$dateText})"; } Capsule::table('tblinvoiceitems') ->where('id', $item->id) ->update(['description' => $newDescription]); } });

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

Hello, I have a dedicated Hetzner server, WHMCS cannot connect to the server, it gives this message, but these ports are open on the host, and Hetzner also says that we did not close the port and it is open, but it still does not connect. FAILED: Could not connect to Virtualizor. Please make sure that all Ports from 4081 to 4085 are open on your WHMCS Server or please check the server details entered are as displayed on Admin Panel >> Configuration >> Server Info.

John didn't say that 😉 He said the feature list is under wrap (eg not yet announced).

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.

We won't go cloud. Kayako burned us with that and SupportPal is brilliant. Where's the announcement?

This module works as documented. Password reset and firewall rules are tested and functional. For support, contact support@arkhost.com as stated in the README or via GitHub issues.

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.

Hi @ZeroMB, Thanks for that information. I've logged case #WHMCS-22693 with our developers in order to have this reviewed for future releases. Whilst I cannot provide an estimated time for completion for this, once we resolve cases and push features they are available at our change log, here: https://changelog.whmcs.com/ Thanks again for taking the time to report your findings.

Hi there Negar. WHMCS software will allow the following billing cycles: One Time/Monthly Quarterly Semi-Annually Biennially Triennially Daily billing is not a part of our product, and there are not currently any plans to add this. If you should decide to get started, we recommend that you review our System Requirements - http://docs.whmcs.com/System_Requirements and then you may purchase a license here: whmcs.com/orderhttps://www.whmcs.com/signup Thank you for your interest in WHMCS! Customer Service Team

We're pleased to announce the release of WHMCS 8.13 Release Candidate. This marks the end of feature development for the 8.13 series and is the final stage before version 8.13 is promoted to General Availability status. WHMCS 8.13 includes the following new functionality and enhancements: Manual User Password ResetsOne of our most requested admin features is here. With over 250 community upvotes, WHMCS 8.13 introduces the ability to reset a user's password directly from the Admin Area. This...View the full blog post

Hi @ghmercado, The domain sync batches are limited to 50, so the notices will never exceed that. We're currently tracking a few different ideas for changes to this notification. Check them out and add your vote to your preferred option: https://requests.whmcs.com/idea/ability-to-disable-domain-sync-emails https://requests.whmcs.com/idea/provide-an-option-to-email-on-domain-sync-only-if-a-problem-is-encountered https://requests.whmcs.com/idea/make-domain-sync-cron-work-in-smaller-then-1-hour-increments-or-allow-syncing-more-than-50-domains https://requests.whmcs.com/idea/add-expired-domains-to-the-automation-status-screen

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

I Need to.. any whmcs developer ? Thank you

The automation issue in WHMCS for additional purchases may be due to missing or misconfigured triggers for add-ons. Ensure automation is enabled for all product types and that the payment gateway is properly integrated to trigger actions after transactions. Also, check for any conflicts with other integrations, like Spotify streaming.

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.

yes.