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

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"); });

I have reported the following on 19th Feb 2026 : == Affected Version == WHMCS 9.0.1 == Description == When a client attempts to upgrade an existing yearly/recurring service to a one-time (lifetime) service, WHMCS throws a fatal DivisionByZeroError in includes/upgradefunctions.php inside SumUpPackageUpgradeOrder(). This happens on the latest WHMCS version running on PHP 8.3 and occurs even with all custom hooks/modules disabled, indicating a core issue. This was working fine with PHP 7.4 ex : Error: DivisionByZeroError: Division by zero in public_html/includes/upgradefunctions.php:0 Stack trace: #0 public_html/upgrade.php(0): SumUpPackageUpgradeOrder('9043', 10, 'monthly', '') #1 {main} == Steps to Reproduce == Use the latest WHMCS version on PHP 8.3. Create a recurring product (e.g., yearly billing cycle). Create a second product with pay type “One Time”. Set up an upgrade path from the yearly product to the one-time product. Log in as a client with the yearly service. Go to Client Area ? Upgrade/Downgrade and attempt to upgrade to the one-time product. The upgrade page fails with a fatal error. == Expected Result == The upgrade page should load normally == PHP Version == 8.3 == Severity == High This was confirmed to be a bug [ case WHMCS-25204 ]. Since then, two minor versions (WHMCS v9.0.2 & v9.0.3) were released, and this is not fixed yet!

Rad web hosting announces release of client-facing whmcs whois addon module! Rad Web Hosting is pleased to announce the release of client-facing WHMCS WHOIS addon module. Rad Web Hosting Announces Release of Client-Facing WHMCS WHOIS Addon Module Rad Web Hosting is pleased to announce the release of its new client-facing WHMCS WHOIS Addon Module, a powerful and flexible extension designed to provide a secure, public-facing WHOIS lookup interface for WHMCS installations. This module enables hosting providers, domain registrars, and infrastructure operators to offer fast and reliable domain WHOIS queries directly from their WHMCS platform. The module was developed to address a common need among hosting providers: offering a public WHOIS lookup tool that integrates seamlessly with WHMCS while maintaining performance, security, and administrative control. With built-in caching, CAPTCHA protection, customizable WHOIS servers, and strict domain validation, the WHMCS WHOIS Addon Module delivers a modern and abuse-resistant solution for domain lookup services. A Modern WHOIS Lookup Tool for WHMCS The new addon introduces a clean and efficient WHOIS lookup interface that can be accessed by both clients and public visitors. Hosting providers can easily add a WHOIS lookup page to their WHMCS deployment, allowing users to query domain registration information without requiring login access. Visitors can simply enter a domain in the standard format: example.com The module then performs a WHOIS query and returns the registry response directly within the WHMCS interface. The public lookup page is accessible via: https://yourdomain.com/index.php?m=client_whois This makes it easy for providers to link the tool from their homepage, domain search pages, knowledge base, or marketing landing pages. Designed for Security and Abuse Prevention Public WHOIS services can easily become targets for automated abuse. To prevent this, the Rad Web Hosting WHOIS Addon Module includes several built-in safeguards. Anonymous users are required to complete a CAPTCHA verification using WHMCS’s built-in CAPTCHA framework before performing a lookup. This allows the module to automatically support whichever CAPTCHA provider is configured within WHMCS, including: Google reCAPTCHA hCaptcha Cloudflare Turnstile WHMCS built-in CAPTCHA Logged-in clients are exempt from CAPTCHA, allowing for a smooth user experience while maintaining protection against automated queries. In addition, the module enforces strict domain validation rules, ensuring that only properly formatted domain names can be submitted. Intelligent WHOIS Server Resolution Different domain extensions use different WHOIS servers, and managing these differences can be complex. The Rad Web Hosting module solves this by implementing a flexible multi-layer WHOIS resolution system. When a lookup is performed, the module resolves the correct WHOIS server using the following priority: Administrator-defined WHOIS server overrides Built-in WHOIS server mappings Automatic IANA referral lookup This approach ensures compatibility across a wide range of domain registries while allowing administrators to customize WHOIS servers for specific TLDs when necessary. Through the module’s admin interface, operators can easily add, edit, or disable WHOIS servers for individual domain extensions. Built-In WHOIS Caching for Performance To ensure fast response times and reduce unnecessary network requests, the module includes a built-in filesystem caching system. When a WHOIS query is performed, the response is stored locally and reused for subsequent requests during the configured cache lifetime. This significantly reduces outbound WHOIS traffic while improving lookup speeds for frequently queried domains. Typical performance improvements include: Scenario Response Time Cached lookup Under 10 milliseconds Fresh WHOIS query 200–900 milliseconds By caching responses, the module also helps protect upstream WHOIS servers from excessive requests. Flexible TLD Validation The addon allows administrators to define which domain extensions are accepted by the lookup tool. This configuration is maintained in a separate file, making it easy to update without modifying the core module code. Administrators can also choose to allow any TLD if they prefer not to enforce a strict validation list. This flexibility makes the module suitable for environments ranging from small hosting providers to large-scale domain marketplaces. Seamless WHMCS Integration One of the key goals of the project was to ensure that the module integrates naturally with WHMCS. The addon follows WHMCS development best practices and relies on native platform functionality wherever possible. See also How to Install WHMCS Domain Reseller API Registrar Module Key integration features include: Native WHMCS CAPTCHA support WHMCS addon module architecture WHMCS database integration for server management Smarty-based client area templates Compatibility with WHMCS security and configuration settings This ensures that the module behaves like a natural extension of the WHMCS platform rather than a standalone add-on. Easy Installation and Deployment Deploying the module takes only a few minutes. Administrators simply upload the module directory to the WHMCS addons folder and activate it through the WHMCS admin panel. Once activated, the module automatically creates its required database tables and becomes immediately available. The lookup page can then be accessed through the WHMCS routing system and linked anywhere on the provider’s website. Ideal for Hosting Providers and Domain Services The WHMCS WHOIS Addon Module is especially useful for: Web hosting providers Domain registrars Domain marketplaces Infrastructure platforms SaaS providers managing domain portfolios By offering a built-in WHOIS lookup tool, providers can give visitors quick access to domain registration data while keeping the entire experience within their own platform. Continuing Innovation from Rad Web Hosting The release of the WHMCS WHOIS Addon Module reflects Rad Web Hosting’s ongoing commitment to building practical tools for the hosting and infrastructure community. Rad Web Hosting has long focused on delivering solutions that combine performance, security, and operational simplicity, and this module continues that tradition by providing a production-ready WHOIS lookup system designed specifically for WHMCS environments. Future enhancements may include additional performance improvements, advanced caching options, and expanded domain intelligence features. Availability The Rad Web Hosting client-facing WHMCS WHOIS Addon Module is available now. Github: https://github.com/Rad-Web-Hosting/client_whois WHMCS Marketplace: https://marketplace.whmcs.com/product/8495-client-whois-lookup For more information about Rad Web Hosting services and tools, visit: https://radwebhosting.com Find us on whmcs marketplace

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

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?