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;

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.

Thanks to @Mytihost, I found an elegant solution for this issue. The following hook: add_hook('ClientAreaPage', 1, function($vars) { if (!empty($vars['clientsdetails']['customfields'])) { $customfieldsAssoc = []; foreach ($vars['clientsdetails']['customfields'] as $field) { $customfieldsAssoc[$field['id']] = $field['value']; } return ['customfieldsAssoc' => $customfieldsAssoc]; } }); makes available the value of any client custom field in a template, using i.e. the form {$customfieldsAssoc.17} (where "17" is the id field in the tbl customfields)

Hello, Not at all and it's highly recommended, to change the admin path.

Hi Still waiting on the answer, also. I guess I need to open a ticket then

Una buona notizia e' che il nostro team di sviluppatori sta attivamente lavorando per aggiungere la gestione di fatture elettroniche in una delle prossime release di WHMCS. In attesa di avere piu' dettagli nei prossimi mesi, non si hanno ancora tempistiche o specifiche. Certo e' che si potranno emettere fatture elettroniche in diversi formati, incluso Fattura PA. Per rimanere aggiornati potete sottoscrivere alla feature request corrispondente: https://requests.whmcs.com/idea/add-electronic-invoicing

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

Personally I wouldn't recommend using it for production. There's a few reports of issues since upgrading which is common with new versions. Better to wait a few weeks for any bugs to get fixed.

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.

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.

So what did you mean when you said: You said it works and then said it doesn't work. Then you said it doesn't work. I am not trying to back you into a corner. I am simply trying to understand.

... and contact WHMCS support to have the development licensed reissued. ... and then rename the directory back to make your development installation match your production installation as close as possible, once this issue is fixed, and then contact WHMCS support to have the license reissued again. @WHMCS John WHMCS really goofed this RC. It's released just before the holidays and will hit stable very shortly after everyone gets back to work. I hope you understand why developers are frustrated with this.

WeWe is a project-focused WHMCS service provider supporting hosting companies and digital businesses with structured, reliable WHMCS implementations. Our team has multi-year hands-on experience with WHMCS, backed by solid technical resources through our sister company, WebNIC, which has been operating in this industry for over a decade. This allows us to deliver not only development, but also proper project coordination, quality control, and long-term maintainability. Our WHMCS Services: • WHMCS Custom Module & Addon Development • WHMCS System Setup, Migration, and Optimization • Payment Gateway & Third-Party Integrations • Domain Registrar & API Integrations • Server Integrations (cPanel, Plesk, DirectAdmin) • Custom Hooks & Workflow Automation • WHMCS Upgrade, Refactoring, and Performance Improvement • Client Area & Template Customization • Ongoing WHMCS Maintenance & Support Why Work With WeWe: • Strong focus on project management and delivery quality • Practical WHMCS experience across real production systems • Reliable resources with long-term industry background • Clear communication and structured execution • Suitable for both one-off projects and ongoing support If you are planning a WHMCS upgrade, custom integration, or need a reliable partner to manage your WHMCS project end-to-end, feel free to reach out to us at muhammad.m@wewe.cc.

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

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

Hello WHMCS Community! I'm thrilled to announce the release of Update 3 for the Stripe Checkout module for WHMCS, developed under RackNode! This update brings even more powerful features, making it easier than ever for businesses to cater to a global audience with a seamless and secure payment process. What’s New in Update 3? Expanded Payment Gateway Support The Stripe Checkout module already supports widely-used payment methods, including: PayPal Alipay Cash App Google Pay Apple Pay Link Card In addition to these trusted options, Update 3 introduces support for a wide range of new payment gateways to help you reach customers around the globe: WeChat Pay iDEAL Bancontact Giropay Sofort SEPA Debit EPS Przelewy24 (P24) OXXO Boleto FPX GrabPay Multibanco MobilePay Revolut Pay Amazon Pay (Beta) US Bank Account (ACH) TWINT Enhance checkout conversion rates by offering localized and regional payment methods your customers trust. Selectable Payment Gateways Now, you can choose a single payment gateway to display at checkout, offering a streamlined payment experience tailored to your business needs. Key Features (As Always): Multiple Payment Method Support: Accept payments via cards, Alipay, Cash App, and more. Adaptive Pricing: Automatically convert prices into local currencies, increasing global accessibility and conversion rates. Error Handling & Secure Webhook Integration: Ensuring secure, real-time payment confirmations with robust logging and signature verification. Seamless WHMCS Integration: Easy setup with just your Stripe credentials, making it a perfect solution for hosting providers and online businesses. Why Choose Stripe Checkout Module? Global-Ready: Accessibility for customers worldwide with local currencies and payment methods. Secure & Reliable: Built with security at its core, ensuring peace of mind for you and your customers. Pricing: $49 Per Year WHMCS Marketplace Documentation: For detailed setup instructions, visit our documentation: Documentation Questions or Customization Requests? Feel free to reply here or reach out directly to info@racknode.net for any inquiries or custom development needs.

I'd suggest that your average user that grabs a script like this will not change anything in it, especially since they're not (apparently) being told to. I've seen users not change a "CHANGE_THIS" in scripts, then ask why it's not working. I've also seen them ignore the "remove this file after use", so relying on that might not be advisable either. Best practice is not to spoon feed, keep this outside the publicly accessible directories, and instead of that simple URL parameter you reveal, make it a "secret key" that is defined within the script, with a note to change it (or better still they make their own that must be x long and have this or that in it; if empty, fail with "key needed"). Safety first.

New here? That's not now, nor has it ever been the way of it. More profit is met with "what is the next thing to make even more".

I have used the above code for my WHMCS 8.13.1 for automation & server selection. It's working fine. This files saves my headache as i was looking for this since 2 months. Great work and hats off to Mytihost Team. Thank You.

@EnricoloDi niente! Occhi puntati su quando verra' rilasciato WHMCS 9.0 😀

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

Will need to take your word for it, since there's no way for us to substantiate that. I've personally never heard anyone state they'd like to hand over control of billing in WHMCS, but my circle is smaller. A further note, up 63% is a relative term. If no one wanted it, but x number of users now do, the vague starting point allows for some "fudge room" in gauging increase of interest.

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.

This is caused by misconfigured WHOIS servers. You need to ensure the correct string for "available". When dealing with this error, you can navigate to the WHOIS interface in WHMCS admin and check some WHOIS responses for domain that status is known For example, you can use "thisdomainisn0tregistered.org" as a test for getting the appropriate response of WHOIS for a domain that is available for registration. Then, you need to incorporate your findings in the whois.json file. Configuring the appropriate values in this manner will ensure that your clients are given the opportunity to register the domain which is "available" and configured for sale in your WHMCS. Example { "extensions": ".org", "uri": "socket://whois.publicinterestregistry.net", "available": "Domain not found." }

Hi @rcartists, You must first set product pricing in your default currency. Then you can have the system calculate the pricing in additional currencies: https://docs.whmcs.com/payments/currencies/#update-product-prices The system can also be configured to update the pricing of additional currencies automatically once per day: https://docs.whmcs.com/payments/currency-tutorials/automatically-update-prices/

You should write your own. AI is not to be trusted.

Hi @Sudipto Mahmud, Yes the auto-updater will update files with a customised admin and crons directories. For more information see: https://docs.whmcs.com/getting-started/configuring-whmcs/enhancing-security/#5-rename-the-whmcs-admin-area-directory

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 understand your frustration, and we’re sorry to hear about your experience. To clarify, the lifetime license you purchased grants you indefinite use of the theme, but as stated on our product page, ongoing updates and support require an active subscription. This is a common practice in the industry, as maintaining compatibility with WHMCS updates involves continuous development work, which incurs costs for us as well. We’d be happy to assist you further if you choose to renew your support & Updates plan. Alternatively, you’re welcome to continue using the existing version of the theme without updates. If you have any questions about your options, feel free to reach out. Thank you for your understanding.

You're most welcome! Be sure to stop by our marketplace regularly - it's the best way to stay up to speed with all the latest updates and fresh releases.

I'd recommend making a backup of any files you are planning to delete. Better yet, try moving the folder outside of WHMCS document root path. I would keep the files at minimum until you've either confirmed this solution has solved your issue or not. This way you can quickly restore your WHMCS back to its previous state in case of any unforeseen errors.

Custom fields are a pain to deal with in WHMCS. Other than placing a {break} if the field is found, there's not really more optimization that can be done - unless you can access it by $customfields.17.value, which I assume you can't.

You can post at https://whmcs.community/community/137-service-offers-requests/ and one of the developers can do this work for you.

We know a number of people like to use Google Suite, we also know that sometimes you may have problems configuring it correctly. The following is a known good configuration: mail method --> SMTP PORT 465 host: smtp.gmail.com Type: SSL Thanks to @garybarr for also letting us know G Suite App Passwords can be used when you run into Authentication issues, the full steps for creating an app password are located on the G Suite Support Site.

YOU CAN USE MY EMAIL DESIGN FOR YOUR COMPANY, THANKS TO THIS COMMUNITY I HAVE FOUND A LOT OF COMMUNITY CONTENT, SO I GIVE YOU MY PERMISSION TO USE IT. Post Update: After a long time working on the code, I have managed to get it to look correct. There were many problems that I am going to name now, which I fixed to make it display correctly; Global Email CSS Styling: Some generic tags will not work, for example 'body', instead of adding it to Global Email CSS Styling, I added it directly to the HTML code to make it work. Error ❌ body{font-size: 17px; line-height: 25px; color: #f1f1f1; font-family: 'Open Sans', sans-serif; font-weight: 400; margin: 0px; background-color: #070B41;} Solution ✅ <body style="font-size: 17px; line-height: 25px; color: #f1f1f1; font-family: 'Open Sans', sans-serif; font-weight: 400; margin: 0px; background-color: #070B41;"> Sometimes you have to add an '!important' to the CSS code, because another tag is replacing it. For example, I wanted to put links with a different color and no style; Error ❌ a{text-decoration: none; color: #1094F0;} Solution ✅ a{text-decoration: none!important; color: #1094F0!important;} Some images on some providers do not load correctly because it can detect that the domain is not secure. For example; Error ❌ https://universalgg.com/assets/img/mails/logo.svg Solution ✅ https://i.imgur.com/7nQbkxQ.png It has taken me a long time to investigate, since on localhost it was working correctly. I have tried various SMTP providers and it was working fine too. Conclusion: The error is from WHMCS and not from my design, but it can be solved. All code: <!DOCTYPE html> <html> <head> <title></title> <link rel="preconnect" href="https://fonts.googleapis.com"> <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> <link href="https://fonts.googleapis.com/css2?family=Open+Sans:wght@300;400;500;600;700&display=swap" rel="stylesheet"> <style> .main-table{background-color: rgb(3 5 33 / 87%); border-radius: 20px; overflow: hidden; margin-top: 20px;} .content-table{padding: 50px 40px 50px 65px;} .h1-table{padding-bottom: 25px; font-size: 22px; font-weight: 700; color: #fff;} .btmspace-table{padding-bottom: 30px;}.top-line{padding-top: 30px;} .grey-line{border-top: 1px solid #707070;} .welcome-img{width: 50%; background-image: url('https://universalgg.com/assets/img/mails/img.webp'); background-position: left; background-size: cover; background-repeat: no-repeat;} .welcome-copyright{color: #DDDDDD; font-size: 12px; text-align: center;} a{text-decoration: none!important; color: #1094F0!important;} </style> </head> <body style="font-size: 17px; line-height: 25px; color: #f1f1f1; font-family: 'Open Sans', sans-serif; font-weight: 400; margin: 0px; background-color: #070B41;"> <table width="1140" border="0" align="center" cellpadding="0" cellspacing="0" class="main-table"> <tr> <td> <table width="100%" border="0" align="center" cellpadding="0" cellspacing="0" class="content-table"> <tbody> <tr> <td colspan="2" style="padding-bottom: 35px;"> <img src="https://universalgg.com/assets/img/mails/logo.svg" style="max-width: 430px;" width="100%" height="auto" alt="logo"> </td> </tr> <tr> <td colspan="2" class="h1-table"> ¡Bienvenido! </td> </tr> <tr> <td colspan="2" class="btmspace-table"> Hola {$user_first_name}, revisa este correo electrónico en su totalidad, ya que contiene información importante. </td> </tr> <tr> <td colspan="2" class="btmspace-table"> Has registrado tu cuenta el día {$user_signup_date}. Necesitarás tu dirección de correo electrónico y la contraseña que elegiste durante el registro, para iniciar sesión.</br> Si creó la cuenta como parte de la realización de un nuevo pedido con nosotros, en breve recibirás un correo electrónico de confirmación del pedido. </td> </tr> <tr> <td colspan="2"> Por favor, no responda a este mail, es un mensaje automático. Le enviamos un cordial saludo, gracias por confiar en nosotros. </td> </tr> </tbody> </table> <table width="100%" border="0" align="center" cellpadding="0" cellspacing="0" class="top-line"> <tbody> <tr> <td class="grey-line"></td> </tr> </tbody> </table> <table width="100%" border="0" align="center" cellpadding="0" cellspacing="0" style="padding: 30px 40px 30px 65px;"> <tbody> <tr style="vertical-align: middle;"> <td style="padding-bottom: 20px; font-size: 15px; font-weight: 500; color: #1094F0;"> <a href="https://universalgg.com">Sitio web</a>&nbsp; | &nbsp; <a href="{$whmcs_url}">Área de clientes</a>&nbsp; | &nbsp; <a href="mailto:info@universalgg.com">Contactar</a> </td> <td style="padding-bottom: 13px; text-align: right;"> <a href="https://twitter.com/UniversalGamg"><img src="https://universalgg.com/assets/img/mails/s_twitter.svg" style="display: inline-block; margin-right: 15px;" alt="icon"></a> <a href="https://www.instagram.com/universal_gg/"><img src="https://universalgg.com/assets/img/mails/s_instagram.svg" style="display: inline-block; margin-right: 15px;" alt="icon"></a> <a href="https://discord.gg/nMxTQ5UZpM"><img src="https://universalgg.com/assets/img/mails/s_discord.svg" style="display: inline-block; margin-bottom: -1.5px;" alt="icon"></a> </td> </tr> <tr> <td colspan="2" class="welcome-copyright"> 2018-2023 &#169; {$company_name} </td> </tr> </tbody> </table> </td> <td class="welcome-img"></td> </tr> </table> </body> </html>

it doesn't use an email template and that email is hard-coded internally to WHMCS... two thoughts.. if you are using PHP Mail for your email settings, I think it will show the client's IP in the header - specifically in the X-PHP-Script setting output... I can't recall if the same applies when using SMTP to send. perhaps you could add just jQuery/JS to the form to add the client's IP value to the message string before it sends to WHMCS ? all that said, there's nothing to stop a user hiding their IP by any number of methods - so there's no guarantee that any value you receive for their IP address, by any method, would be accurate.

which is the definition of a lookup provider. all i'm saying is that WHMCS 7 is designed to either use whois, or a lookup provider, for ALL TLDs - you can't mix and match, e.g this module for .ge, but whois for .com - you have to put all your eggs in one basket.