WHMCS.Community

IMPORTANT REMINDER: Open Source and License Upgrades - 30% OFF! Our special offer on Open Source purchases and License Upgrades is slowly drawing to a close. If you enjoy the idea of having a WHMCS module that comes with lifetime validity and unencrypted code, go place your order now, and pay 30% less! Look around our Marketplace and take your picks! 1. WordPress Manager For WHMCS 2.2.0 - 15% OFF! In a couple of days WordPress will turn 21! The timing couldn't be any better for breaking the major news: our WordPress Manager For WHMCS has just been leveled up to version 2.2.0 and welcomed a package of noteworthy additions: The option for importing WordPress instances from a remote server by entering the WordPress login URL, admin username, and password The feature that allows showing WordPress status notifications in the client area whenever the instance undergoes an update The possibility of specifying the "Site Title" when setting up a new WordPress site or importing it from a remote server Let us boost the celebration mood by granting you a joyous 15% promo code on the module, available on our website only for a limited time. View the changelog and learn all about WordPress Manager For WHMCS 2.2.0! 2. More WHMCS modules updated to new versions Aside from our top-tier WordPress Manager, a handful of other modules have recently also undergone refinement so that they now perform even better in the WHMCS V8.10 environment. The list includes: Polish Language Translation For WHMCS 2.9.0 that lets you reach out to your Polish-speaking customers and make the reality of your WHMCS easier for them (covered by the ongoing 30% OFF!) SMS Center For WHMCS 3.16.0 that equips your WHMCS platform with tools for managing SMS messages exchanged with your clients and team members Zimbra Email For WHMCS 2.3.0 that helps you handle your account provisioning and management routines without stepping outside of your WHMCS 3. PanelAlpha v1.0.2 As we all know, PanelAlpha keeps evolving, which has recently been marked by the release of version 1.0.2. Now that WordPress is about to celebrate its 21st anniversary, PanelAlpha has found a special way to mark the occasion. They have published an important business guide that explores key research-backed insights about this top CMS solution. Should you offer WordPress hosting? Could you be missing out if you don’t? Find out if WordPress hosting would benefit your offerings! 4. EasyDCIM v1.11.0 EasyDCIM is making significant progress with the latest 1.11.0 update by saying goodbye to Debian 11 as its base operating system. The official switch to Debian 12 "bookworm" has been accompanied by the following new features: New ASUS driver utilizing the Redfish protocol Automatic sensor detection in ASUS, Dell, and HP servers The ability to establish power usage limits for servers Discover the full scope of novelties in EasyDCIM v1.11.0! Need WHMCS Module Development For Your Business? Get Your Free Quote Now! We can customize our modules to fit your exact needs or even create a completely new one from scratch to give your WHMCS platform an added boost!

Came here as I have the same issue... payments not getting updated in whmcs... 

Hi Thank you. Is there no hook for such a thing?

Scenario: There are 10 clients, each with Credit Cards on file. 8 of them have only 1 credit card on file as default payment method and the other 2 have 3 cards each on file, with 1 set as their default. They are all due on the same date. During the cron job on their due date, their cards are attempted capture and service renewed if their default card is successful. In the case of the 2 who have multiple cards on file, 1 of them, their default card FAILS and does not renew their service. Solution/Question: In the case of the multiple cards on file client who's default card failed during cron, is there a HOOK that can be written/implemented that will automatically attempt capture on their next card on file in the event that the default card FAILS during the daily cron operation? This same solution would also try their 3rd card if the 2nd card fails as well, until all cards on file have been attempted.

Will this be an issue with WHMCS Plesk modules? For anyone who's using the Plesk REST API, please note that starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Since the curl commands send the “Content-Type: application/x-www-form-urlencoded” header by default, you need to add the --header "Content-Type: application/json" option to such commands to keep them working correctly. We strongly recommend that you check your existing integrations that use cURL for compliance with this change and update them if necessary. Failure to do so may result in any such integrations ceasing to work after updating to Plesk Obsidian 18.0.62.

mod_soyoustart_products' doesn't exist /vendor/illuminate/database/Connection.php:331

You can edit your orderform theme files. I'm not sure if it will help, but here's a guide we prepared regarding removing some fields during order process: https://radwebhosting.com/client_area/knowledgebase/396/Customize-WHMCS-Order-Form-Cart-Template.html

It should be opt in, John. Always. Don't add things anywhere like this without direct opting in during installation. Show it to the admin (with no hopes of removal there, like the marketplace), and have it not appear anywhere in customer facing pages unless the admin agrees and chooses to.  Simple.

Anyone?

I'm bewildered that this is even a question. Why would you *forcibly* add this without a option to turn it off? WHMCS is used by thousands of web development companies who want to sell their own development services and not push people to use Sitejet. Your motivations here are very transparent - it's just like the debacle with the SSL warning icons. You guys are just trying to sell your own services. It's been years since that "feature" was added and after years of requests there is still no way to turn it off. The answer is simple - stop adding features without giving clients an option to turn them off. Surely this cannot be that difficult of a concept to grasp?