Leaderboard

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

Request WHMCS to make it a confugurable option instead of removing it?

The one question I have is "why"? Clearly there's a need and demand for it, why is it not even considered being made optional, with warnings about not doing it or what have you. Why is it simply removed, with no options and so on.

Are there still issues after the 9.0.3 release?

A system should be designed to be functional for its paying customers, rather than being dictated by external regulations that may or may not be applicable to all users. Implementing such a feature without a proper disable option is impractical and appears to be an oversight. The current suggested workarounds are ineffective for the majority of standard web design and hosting businesses. Remember, most projects start off with two 50% (published) invoices (deposit and final) from the quote when converted and the final invoice typically gets tweaked for various reasons. This change would prevent that quick 10 second update to it. WHMCS should focus on developing efficient software that delivers value to its users, allowing us to manage legal compliance independently, rather than introducing features that hinder usability.

Yes, I agree they should be an option

Does anyone now how to remove "Search for a domain with AI-powered suggestions"? Thanks

@Justin ROCKET LAUNCHER Your WHMCS already looks quite close to your main website. I'd probably just rework things like the sidebar panels and hero section, but honestly, it's not as bad as you might think. That said, there's more than one way to approach this. WHMCS doesn't have to be 100% identical to your main website. Keeping the same branding (colors, tone, general feel) is important, but at the end of the day it's still a separate system with a different structure. Trying to make it feel completely seamless usually hits a limit. In our case, we ended up taking a slightly different approach, keeping most of the experience on the main site and only relying on WHMCS where it makes sense. I'm inviting you to see how we made ours looks like for both guests and logged-in clients.

This is fully achievable. You can either redesign WHMCS to match your website, or go fully API-driven and handle everything directly on your main site without exposing WHMCS. We’ve implemented similar solutions before that are still in production today, including domain registration, support centers, and custom domain search integrations. The main issue is likely the developers you’re hiring. Lower-end developers usually lack the experience required for this level of integration. What you are asking is NOT a simple “WHMCS tweak” It is: → a custom frontend application → with WHMCS acting as a backend API Most developers fail because: - They only know WHMCS templating - They don’t understand UX flow - They don’t build proper API orchestration A proper implementation would typically cost: $5.000 – $20,000+ for full api-driven (true seamless experience)

Glad to see more customers speaking up about this… it’s a simple, fixable issue. All they need to do is keep allowing the switch: Add ($allow_adminarea_invoice_mutation = true;) in your WHMCS configuration.php . WHMCS choosing a one-size-fits-all strict model is what’s really causing the pain… let us decide if we need to deal with regional compliance and added accounting complexity, not force it on everyone.

Not everyone wants SAAS solutions, or keeping data with a third party due to concerns about client data. I'm one of those businesses.

It totally broke the adding late fees option. I have invoices that are many days old and none of the late fees have been added like they were supposed to be. This is a real mess.

Yes, I'm hoping they're making an option

If I had to guess, it's not an arbitrary decision, but based on some legal requirement they must follow or get into trouble. I'd have hoped a "change this at your own risk" choice would suffice, but maybe they don't want to chance someone claiming they missed it. Just a guess.

Thanks for the confirmation @WHMCS Ricardo. I really hope WHMcs team reconsiders this, hopefully making it optional.

I would say this issue qualifies needing a last resort technique since they are removing it. What else can I do?

Whats stupid is as a developer this is as simple as adding a checkbox to the config to allow us to choose ourselves. I've never in my life understood why software companies lock you in, instead of giving you the option. You keep increasing prices year after year and you want us to stay with you, but if you keep doing this crap most of your base is not gonna find value in your ever increasing prices.

Welcome to the common sense reasons why were frustrated about WHMCS enforcement of preventing us from editing our OWN invoices we created in the first place. Credit / debit is useless in real world standard practice. If they want to provide a switch to disable editing published invoices or changing status fine, but dont force it on the customer base. That's dumb.

Check the domain at NEO, as @RadWebHosting suggests the payment of the invoice will trigger a renewal with the registry. If NEO support domain syncing then the expiry update will be updated in due course. I can't find the article but the way to do this without getting a renewal processed is to edit the invoice. Then on a new line copy and paste the details of the domain and dates, add the price and then delete the original line. WHMCS links the line item to the action of renewal. By deleting the original line the renewal action is not done.

While invoice editing can currently be re-enabled via $allow_adminarea_invoice_mutation = true; in configuration.php, this option is reportedly being removed in a future release. This raises a practical concern: how are administrators expected to handle routine tasks such as removing late fees or splitting system-generated invoices that are linked to products and services?

Hello everyone, I wanted to share a simple but effective security approach I implemented in WHMCS to reduce spam registrations and fake account abuse. The idea is straightforward: users must verify their email before they can access any part of the client area or place orders. Overview If a user has not verified their email address, they are completely restricted from using the client area. This includes blocking access to: $blockedPages = [ "clientarea", "services", "invoices", "domains", "tickets", "productdetails", "upgrade", "addons", "downloads", "supporttickets", "serverstatus" ]; Access control behavior When a user is not verified: They cannot access the dashboard They cannot view services They cannot access billing or invoices They cannot open or view support tickets They cannot use upgrades or addons The only allowed access is the email verification flow. Allowed page for unverified users Unverified users are only allowed to access: /user/profile From this page they can: Resend the verification email Update their email address if needed Complete the verification process User flow User registers an account Verification email is sent automatically User logs in System checks verification status If not verified, all client area access is blocked User is redirected to the profile page After verification, full access is restored automatically Purpose The main goal of this system is to reduce spam accounts, fake registrations, and abuse of hosting resources. It ensures that only verified users can interact with services, which significantly improves account quality and reduces unwanted usage. Result This approach helps: Reduce bot registrations Prevent disposable email abuse Improve security of client accounts Keep hosting resources clean Ensure only real users access services EXAMPLE BELOW THIS IS HOW IT LOOKS, If anyone is interested, I can share the hook code for this implementation.

Nice. Thanks for sharing!

AI wont kill WHMCS right now and any near future. The logic behind a system like WHMCS its too huge to replicate easily, domain renewals is one thing, but making it all work together with invoices, dns, hosting, etc etc etc. You need to spend alooooooot of tokens for doing that. So no, right now AI wont kill WHMCS, but give it 2-3 years surely yes WHMCS will be replaced by other systems.

Try this: @media (max-width: 768px) { .sidebar { display: none; } }

I did find that I can manually change the status to Draft in the database and then I can edit the invoice and then publish it again.

Since editing invoices will be removed in the future I cannot do any more updates.

can you try something like, put this in a file includes/hooks/hide_cart_sidebar.php <?php if (!defined("WHMCS")) { die("This file cannot be accessed directly"); } /** * Remove Categories, Actions, and Currency panels from the cart sidebar. */ add_hook("ClientAreaSecondarySidebar", 1, function ($vars) { $filename = \App::getCurrentFilename(); if ($filename !== "cart") { return; } $sidebar = \Menu::secondarySidebar(); $sidebar->removeChild("Categories"); $sidebar->removeChild("Actions"); $sidebar->removeChild("Choose Currency"); });

Thank you for the reply @WHMCS John and for getting back to me about the credit note issue. Just a bit of feedback, for me personally ( our accounts dept are happy to do the add payment) if would be a lot easier if you could tick a set of invoices and mark them paid - it would then show them paid with the method stated on them (eg bank, cheque etc) rather than having to go into say 80 invoices individually to add a payment to each one

This also doesn't work for us. In our country (Thailand) you are only not allowed to change/edit paid invoices. Any other type is no problem. We use the "Edit invoice" option a lot. It would be better if there is a configuration option where we can choose which types of invoice could be edited. Or just make some check boxes in the "admin role" page, so that we can choose which type of invoices can be edited.

Hi, Thanks for reaching out. AI-powered domain suggestions are part of the WHMCS Namespinning lookup providers functionality now: https://docs.whmcs.com/releases/9-0/9-0-release-highlights/ You can switch to another lookup provider if you don't wish to leverage the functionality of the WHMCS Namespinning lookup provider. Please see: https://docs.whmcs.com/8-13/domains/lookup-providers/

Yeah this is a nightmare

@WHMCS John @WHMCS @WHMCS Aimee @WHMCS Alex @WHMCS Andrew @WHMCS Anwar @WHMCS Areeb @WHMCS Arty @WHMCS Carlos @WHMCS Chance Are you guys listening, or is it time for us to migrate to another billing software? Is this how it’s going to be going forward? Please review all the complaints, it’s becoming too complicated to manage our business with WHMCS now. Are you reconsordring restore the previous features.

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/

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.

"Luck" isn't really a component here. If you haven't played around with agentic coding I can see why this would seem like a stretch for you, but it's quite trivial to get a fairly simple billing system up and running quite rapidly. And like I said this is with current-level tools, in a year or two, replicating the entirety of WHMCS would likely be very doable.

Also using custom.css for the theme's variables defeats the purpose of custom.css, it's now going to be replaced for every update. v9 screams minimal effort, rushed with no regard for users. If they don't care why should we?

We're pleased to advise that the issue has now been resolved:

I was reading the documentation about the "Order Days Grace" that is located under General Settings > Ordering with the description "The number of days to allow for payment of an order before being overdue." I was wondering if this could be used to, in effect, create Net 30 or Net 15 billing, where the due date is set 30 or 15 days after the order is placed. Based on the documentation, I believe this achieves that. And it appears that the domain grace and redemption period is managed separately under General Settings > Domains. I would like to confirm that: The "Order Days Grace" only applies to product and service invoices, and not domains. That domain grace / redemption periods are managed separately from this setting. All future invoices for renewals also have the same grace period. Also, is there any way to do the following? Only allow approved customers to have a grace period on invoices. My goal is to allow approved vetted customers Net 30 billing for products and services (but NOT domains), while everyone else must pay in advance. Is there any way to set it up like this?

Please please do not use IP as a way to detect language, 1. it is not very reliable and 2. is actually quite offencive for people who don't speak the native language of the place they live. (e.g. I am English but happen to live in Italy but don't speak good Italian and I hate it if I am redirected to the italian site even though my browser language setting is english.) Much better and much simpler is to just use the browser language setting. Here is the PHP script we use to redirect customers to our specific language pages. <?php if(isset($_SERVER["HTTP_ACCEPT_LANGUAGE"])){ $langarray=explode(",", $_SERVER["HTTP_ACCEPT_LANGUAGE"]); $lang = strtolower($langarray[0]); //echo $lang . " / " . $_COOKIE["Lang"] . " / "; $stop=0; //change this to 1 to disable redirect if ($_GET["stop"]!=1&&$stop!=1){ if (isset($_COOKIE["Lang"])){ if ($_COOKIE["Lang"]=="italian"){ header("Location: " . $_SERVER["HOST"] . "it/"); } else { header("Location: " . $_SERVER["HOST"] . "en/"); } } else { switch ($lang){ case "en-au": case "en-bz": case "en-ca": case "en-029": case "en-gb": case "en-in": case "en-ie": case "en-jm": case "en-my": case "en-nz": case "en-ph": case "en-sg": case "en-za": case "en-tt": case "en-us": case "en-zw": case "en": case "gd": case "ga": case "ga-ie": case "cy-gb": case "cy": header("Location: " . $_SERVER["HOST"] . "en/"); break; case "it": case "it-ch": case "it-it": header("Location: " . $_SERVER["HOST"] . "it/"); break; case "es": case "es-es": case "es-ar": case "es-ve": case "es-bo": case "es-cl": case "es-co": case "es-cr": case "es-do": case "es-ec": case "es-sv": case "es-gt": case "es-hn": case "es-mx": case "es-ni": case "es-pa": case "es-py": case "es-pe": case "es-pr": case "es-us": case "es-uy": header("Location: " . $_SERVER["HOST"] . "es/"); break; } } } } ?> As you can see it checks to see if a "Lang" cookie is set and uses that as the clients language if it is, thus allowing the visitor to override the script on future visits if your site sets this cookie from a language choice in the site. Otherwise it looks at the browser language choice to picks the preferred language and defaults to english if it can't find a match.

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 have already done that. I'm not an idiot.

My screenshot and your first screen shot both state that 8.13.2 are the latest and recommended. Stop trying to boost your post count. You are not adding any value to this topic.