WHMCS bug fixing is hourly help with one specific fault: an error page, a hook that misfires, a payment that never marks its invoice paid, a module command that fails every time. You pay $65 per hour for the time spent finding and fixing it, and the call where we decide whether the problem suits hourly work is free. Some problems have fixed-price pages of their own: a stopped cron goes to cron fixing, mail that never arrives to email deliverability, and signs of a break-in to hacked WHMCS cleanup.
Faults people bring us
- A blank page or a generic error screen after a PHP change or a WHMCS update
- "Cannot be decoded by this version of the ionCube Loader" errors from an encoded module
- Gateway callbacks logged as Invalid or Error in Billing > Gateway Log while the invoice stays unpaid
- Create, suspend or terminate commands that fail and pile up in Utilities > Module Queue
- Two hooks fighting over the same hook point, or a hook cancelling email at EmailPreSend
- Smarty errors in a custom theme or order form after an update
- Prices, configurable options or promotions calculating wrongly in the cart
- API calls from your website or app that started returning errors
- An admin dashboard that loads blank, often a database collation mismatch
How an hourly fix runs
- You describe the fault. What happens, since when, what changed around that date (an update, a new module, a PHP switch), and how to make it happen again. Exact error text and screenshots save the most time.
- We estimate. After the call or a first look, you get a range of hours. If the fault turns out bigger than the range, we stop and ask before going further.
- We reproduce it. On a staging copy where possible, otherwise on live with care. Diagnostics go on only for as long as they are needed: Log Errors, SQL Debug Mode and Hooks Debug Mode (all under General Settings, Other), Module Logging in Configuration > System Logs, and Display Errors only for a short window, since it shows error details to customers too.
- We read the logs. The Activity Log, Gateway Log and Module Log, plus the web server's error log for anything that fails before WHMCS can record it.
- We make the smallest fix that holds. Changes go into your own hook files, theme copy or module copy, not into core files or default templates that the next update would overwrite.
- We tidy up and report. Debug settings are switched back off, because WHMCS warns they swell the database. You get a short note with the cause, the change, the files touched and the time spent.
Rates and blocks
| Option | Price | Suits |
|---|---|---|
| Hourly | $65/hour | A single fault |
| Weekly block | $650 for 10 hours a week | A run of related fixes, such as after a messy update |
| Monthly block | $1,650 for 30 hours a month | A steady stream of issues on a heavily customized install |
| Fixed price | A written quote within a business day | A fault that turns into a defined project |
Hours can be paid through Stripe (cards, Apple Pay, Google Pay), through PayPal, or in crypto using NOWPayments.
What we need
- An admin login with full permissions, or a role that can see logs and settings
- SFTP, SSH or control panel access to the WHMCS files
- Any staging or test install you already run; without one, we will say whether this fault is worth building one for
- Permission to switch debug settings on for a short time
- License details for any third-party module involved
Where hourly work stops
- Encoded modules. We cannot change ionCube-encoded code. We collect the evidence the vendor needs, or quote a replacement through legacy module rescue when the vendor is gone.
- WHMCS core bugs. We write up the reproduction steps for WHMCS Technical Support and, where one exists, add a hook-based workaround until their fix ships.
- New features. Wanting WHMCS to do something new is development work, which starts with hooks development or a module quote.
Both supported branches are covered. Installs older than 8.13 can still be diagnosed, though the real fix may turn out to be an update.
The quickest first hour begins with the exact error message and the time it appeared, so paste both into your first message.