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.

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.

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.

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

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.

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)

So your point is, whmcs should prioritize modern, clear and consistent development instead of just raising prices all the time?

It's quite bold to release an RC without any beta for a major new version. Sure not lacking confidence.

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.

Nexus is gonna disappoint you. It's just a reskinned Twenty One template (for the system template) and a reskinned Standard Cart template (for the cart template). It's only during checkout that it's different.

@WHMCS John Good news. Thanks. Are there any screenshots of the new client UI/Nexus/Search/Ordering etc.

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

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

The problem is, I *do* want clients to have access to it in Plesk in case they want to use it, but I do *not* want SiteJet to take over everything for them in WHMCS as it's far more confusing to have it there than in Plesk. The problem is, what if a customer uses WordPress and doesn't know it - they're going to be super confused as to what this is and think, oh great I can edit my site right from here! And then potentially wipe out the entirety of their WordPress website when they go to publish it, or be super confused about why their site content isn't there when they open SiteJet. You *really* need to have this option only appear *if* the primary domain is already using SiteJet or has no website at all yet. Not just blanket for every hosting plan. How do I access the hosting plan / services list on the Client Area dashboard with this? Is it considered a sidebar? Yes, I understood this from the documentation. And this is great for people who don't want SiteJet anywhere, ever. But why should it be all or nothing? If you truly want people to start using SiteJet, then don't only provide the option to force it everywhere or have it nowhere at all - allow us to choose where we want it to be displayed. And given that WHMCS doesn't have awareness of addon domains or subdomains within a hosting plan, having these options in WHMCS is kinda useless for anyone but the customer with a single domain, and a single website, who only wants a site builder and not other solutions like WordPress or Magento. Meanwhile having the SiteJet option in Plesk makes perfect sense because then the customer can choose on which domains or subdomains they wish to use it. Yet you're saying that to hide it in WHMCS I have to disable it in Plesk too, so customers can't use it at all...

Also,

I don't know, I gave up. WHMCS shipped the v9.0 RC with hardcoded links to /var/www/html/whmcs in the Nexus cart assets. It attempts to load Node modules but these were not part of the version they shipped. The cart doesn't work. The Nexus template's all.css file has this, so I assume it's Bootstrap 4. /** * bootstrap-switch - Turn checkboxes and radio buttons into toggle switches. * * @version v4.0.0-alpha.1 * @homepage http://www.bootstrap-switch.org * @author Mattia Larentis <mattia@larentis.eu> (http://larentis.eu) * @license Apache-2.0 */ I think WHMCS just rushed this release because they promised a release in December. This release is so botched. They've technically delivered on their promise, but yeah...

Still using bootstrap 4.x ?

The Nexus theme have this bootstrap file: /whmcs/templates/nexus/sass stat ../../../node_modules/bootstrap-four/scss/bootstrap stat: ../../../node_modules/bootstrap-four/scss/bootstrap: stat: No such file or directory /*! * WHMCS Twenty-One Theme * Global Stylesheet * Copyright (c) 2020 WHMCS Limited * https://www.whmcs.com/license/ */ @import "../../../node_modules/bootstrap-four/scss/bootstrap"; @import "global"; @import "forms";