Leaderboard

@WHMCS Carlos I try very hard to say professional in these threads (and I don't reply a lot), but I really have to wonder what world the WHMCS management/development team lives in. The next LTS release needs to be out (for a while, so it's fully vetted, BEFORE the previous LTS is retired. LTS has no real meaning if you can't stay on a LTS release. This is pretty much exactly the opposite of what we want/need. WHMCS at it's heart is ordering/billing software. We want a very slow/stable with minimal changes (especially within the LTS track). To be honest, I can't really think of a single new feature in the last 3 - 5 years that WHMCS has put out that we have implemented. There is no way we would implement automated updates until it's been fully vetted (read that as in production for several years). The risks simply don't make sense. Simply put, we can't. From my understanding/community threads, 9.1 forces us to sign up with the WHMCS marketplace. We have compliance requirements and we need to know exactly what data is shared between our WHMCS install and the marketplace. We also need to know how this will work since we keep a development and production environment. We've had ticket RLB-418773 open since 1-Nov-2026 and have received any useful answers. This is also going to force us to do two major upgrades in a relatively short timeframe. This is a lot of work for our staff (testing, training etc.) as well as potentially frustrating to customers. WHMCS really needs to reconsider supporting 8.13 until there is a stable/vetted path to the next LTS version. WHMCS's sister company cPanel manages to support multiple versions at the same time and I have to believe their codebase is much more complex than WHMCS. My 2 cents

I migrated from modernbill 🙂

We've deliberately remained on WHMCS 8.13 due to the numerous issues with version 9. We've been closely monitoring the WHMCS End of Life (EOL) schedule, where the end-of-support date for version 8.13 has been listed as "TBD" for a long time. When I checked the page today, I was genuinely shocked to discover that the status had changed: support for WHMCS 8.13 is now scheduled to end on December 1, 2026 - roughly one month from now. I checked the page earlier this month, and the date was still listed as TBD. Furthermore, the latest available snapshot on the Internet Archive, dated September 30, 2026, confirms that the status was still TBD at that point. Announcing the end of support for a major software version with only around one month's notice is completely unreasonable. This is particularly concerning given the significant issues that still remain with WHMCS 9, which are precisely why we've continued to run version 8.13 in the first place. Customers need adequate notice to plan, test, and execute a major upgrade - especially when the proposed upgrade path involves a version that continues to present substantial problems. Changing the EOL status from "TBD" to a firm date so close to the deadline, without meaningful advance notice, is simply unacceptable.

@WHMCS Carlos I never saw this email. Did anyone else? Personally, I have no intention of getting trapped on 9.1 right now. Just a quick glance around this community tells me it still has too many bugs. Your beta period was what, 2 weeks at best? Before I could even download and install it, the GA was available.

@DennisHermannsen Unattended Automatic Updates only apply updates for the version you are on that we have marked as safe to apply automatically: security fixes, bug fixes and small improvements, with nothing that requires changes to your hooks, themes or customisations. Anything that needs manual steps is not applied automatically, and moving to a new version (9.1 to 9.2) is always a manual update. Before each update, WHMCS backs up the files it is about to replace and restores them if the update fails. @Damo fair enough, it's your call. You can keep automatic updates off, or set your own schedule, under Utilities > Update WHMCS > Configure Update Settings.

@WHMCS Carlos I'm sorry, but this is a bit insane. how were we possibly to know that we should ask for more time on 8.13.x? We did like others on this thread did and kept checking the EOL page. The sudden appearance of Dec-1 and now Dec-31 is just not really acceptable. We may be 1% of WHMCS users, but we have year end closing processes etc. and my CFO would kill us if we updated WHMCS during that. WHMCS has also not given us a clear path to stay on LTS. They way the EOL page stands now we'd have to go to 9.0 (bad idea) and then that would be EOL in either 30 days or EOL at the exact same time as 8.13 goes EOL. Contrary to WHMC's belief, updating WHMCS is not as easy as clicking a button. We have 3rd party modules, custom written reports, hooks, provisioning and payment gateways. That requires us to maintain a development system and fully regression test every patch, upgrade etc. WHMCS also has a habit of breaking API calls between release/patches and then we have to code around that (please see case SIQ-586041 as an example). As far as I know that's still broken and it's been 7 months. Please keep support for 8.13.x at least through the end of Jan-2027 so we can get through year end. Once more month is not going to kill WHMCS. Thanks

I don't think that's the entire reason. Version 9.0 was forced into GA way quicker than any version and it was full of bugs. I appreciated WHMCS decision to extend support for version 8.13 indefintely. We tried running v9.0 on a dev installation but even without any customization, we had a lot of issues. Stuff that were outright illegal and stuff that broke invoicing for EU business. We don't appreciate being given only 1 month of warning - and I'm generous when I say we were given a warning. The only reason I know support for v8.13 ends in ~1 month is because I check the docs regularly. There is no way we can make sure we're running v9 in 1 month. Usually, we're pretty quick to upgrade, but the fact that v9 was originally shipped with so many issues is concerning - so we need a lot of time making sure everything is working correctly; not just customizations, but also invoicing.

@WHMCS Carlos I appreciate the extension to keep 8.13.x going because IMO it's the most stable of the actively supported versions. Being given 1 month to upgrade DURING the start of the busy Holiday season and End of Year is not easy at all. Aside for no more bug fixes or security updates, what's the downfall to continuing to use v8.13.x ? Where was the email to alert your users? Everyone is different and I can't imagine all of your users constantly check the Documentation or the Forums.

I came here to mention this very same thing. Given the significant number of problematic changes in 9.x AND that 9.1 was only released 10 days ago, this is an unreasonable expectation. If the WHMCS devs had done a better job preparing 9.x such that there weren't endless bugs reported for months after, I can see this being more reasonable. However that's not how things panned out. I also would like to request that WHMCS 8.13 remain actively supported until at minimum your planned release date for WHMCS 9.2 so that your customers can feel more comfortable with the 9.x upgrade prior to ending support for 8.x. I would estimate that this would be June 2027.

I’m honestly not convinced by these repeated price increases, especially when they happen without clear prior notice. I’m a small provider managing around 10–20 clients only, and with the latest increase, the subscription is becoming financially unjustifiable. At this scale, the cost is no longer proportional to the value received and is starting to feel more like a burden than a business tool. I understand that businesses evolve, but constant yearly increases without meaningful added value for small users come across as exploitation rather than progress. If this pricing strategy continues, I’m seriously considering moving away from the entire WebPros ecosystem, including WHM and WHMCS. At the very least, there should be better transparency, advance notifications, and fair pricing options for low-usage customers.

If a hosting plan already has support for it, apparently it just takes over the entire Client Area dashboard advertising it HUGE. Even when the customer already has a site there not using Sitejet... This should have been disabled by default for existing installs, enabled by default for new installs. Yet I don't even see any option to disable it without editing the CSS. #sitejetPromoPanel{ display: none; } Funny thing is, I don't even dislike Sitejet, I just realllly don't want this to confuse customers who already have sites built with something else, and it certainly will do that based on how WHMCS chose to implement it.

With it on - WHMCS wants us all to use it - so I’ve been trying my best to work with it, but it’s proper shite. I found a bug within an hour of using it, confirmed. Not being able to ‘undo’ things to an invoice that may have been done by mistake is a right pain. For example : you cancel an invoice that had been partially paid. (I did this yesterday to an invoice because the customer had made a couple of bank transfer payments but then ghosted us - so I cancelled their account and cancelled the invoice. (Which is what I would normally do in v8) in v9 cancelling the invoice created a credit to the customer - and then applied a credit note to the invoice for the total. It’s a bloody mess that is impossible to fix unless we go and SQL it back to the way it needs to be. Invoice immunatbility has a long way to go before it’s usable or acceptable.