bear

We moved from them to Stripe, for the very same reasons. Stripe is far more reasonable. Take note, when cancelling with CDG, make very sure you receive confirmation it's been canceled. We missed they hadn't confirmed, and a recent audit showed they were still pulling the monthly fee from our connected account. Fighting to claw that back currently.

Illuminate is just creating the DB connection. WHMCS is trying to say it's not finding the table being asked for. I've seen hooks and addons calling Illuminate, so it's conceivable some reporting module or template you're using was supposed to have created it? I notice: /modules/addons/ticketsd/hooks.php in that quote of yours. That's where I'd start looking, since it's likely what's triggering this.

Should anyone come across this thread after seeing this error, this fell over on mine because the client didn't have an active subscription with Stripe yet. They were subbed with the previous merchant provider we were using, and I hadn't noticed the changeover date or it might have been clearer. It would have been good had WHMCS simply said no card/profile found or something of that nature instead of heading off to the merchant without checking and the gateway log being the only hint. Too much to ask of a billing system, maybe. 😉

Tried to capture a Stripe payment and it failed with this: "You passed an empty string for 'customer'." While I wait for my ticket and the inevitable "upgrade (on 7.6.1) or give us full access to look" response, I was wondering if anyone knows why it's doing that and if there's a fix. I tried searching, but quoted it finds nothing, unquoted finds all instances of any word with "you" in it. Anyone have an idea on this?

How about only allowing registration if they buy something? Generally it's pointless to allow that without an order of some kind.

If it's broken, this begs the question as to why these "hotfixes" don't get rolled into updates, if it's not in the latest download/autoupdate.

And still the same disappointing Android one as before...

Maybe disallow changing user details in WHMCS for clients? Even if just temporary, it will stop that cold.

That doesn't help determine what went wrong. Perhaps you should temporarily (just long enough to get the result) enable error reporting and load the page?

Did you enable the use of PHP tags (which is not generally a good idea) in the settings of WHMCS?

If you have someone that's late (some clients we give extra leeway to) and want to renew before payment, another method is to move the domain line item on the invoice (along with price) to a new line, save, then delete the original line it was copied from. That way you don't need to remember to put that check mark back (which affects *all* domains). That's the method we use, since it keeps the invoice due and won't renew the domain again if it's paid later. The following renewal/invoice is back to normal. https://docs.whmcs.com/Domains_Management#Manually_Registering.2FRenewing_a_Domain

I have nothing meaningful to add except the "LOL zone" if friggin' hilarious in that. :agree:

You said you were diving, so I was waiting. :) Simplest way is to load the page, and look for the CSS calls. Looking at "/ph-web-hosting.php", there is no head content at all, including CSS calls, which means it's missing the header include. Seeing as it's outside the WHMCS directory structure, that may be the reason? Without seeing what it is you're specifically doing, it's hard to guess accurately. Did you follow this at all, making sure paths were defined properly? https://developers.whmcs.com/advanced/creating-pages/ Or did you want these to be fully external to the WHMCS structure and only call information from WHMCS?

All one can hope is one day soon you search for a difficult issue you're having, and come across a thread that has someone with the exact same issue as you have, and you think "oh boy, I can finally fix my problem". You open the thread, and it states "fixed it", and nothing more. Only then will you feel the frustration that posts like that cause. Glad you fixed it.

Perhaps you could share so others might benefit from the solution?