aegisdesign

Seems to be coming back up. The status page says everything is operational but that's not the case. There's multiple reports of outages still and I can't do anything in the ENOM control panel as it's showing an error about an invalid client IP. The IP belongs to ENOM/Tucows!

WHMCS 8.3 requires PHP v7.2 or later so check you have that too.

They're actually using WHMCSSmarter's WHMCS install to mass mail everyone in the clients table. The data is what you get from {$...} merge data fields.

Had the same here. I downloaded one of their free modules in 2017 before they stopped doing them and switched to selling IPTV products. Presumably their WHMCS install has been hacked and the hacker is just trying to get customers from their database to pressure them into paying. Disappointing that the owners haven't shut the site down / blocked email going out as I've now had two emails from their WHMCS install. The likelihood of them paying the ransom would seem tiny if they don't have control of their own server. From my pov, the data they have is either public already or obsolete so not worried about it at all.

You need to add them in your firewall config so they aren't blocked. It's not a WHMCS specific issue as these need to be whitelisted for any site on your server(s) that accept PayPal. It's so PayPal can send notifications to your server to tell you you've had a successful payment (or not). If the firewall blocks PayPal you'll never know a bill has been paid.

index.php is literally just something that inits WHMCS and fires requests at the frontend dispatcher before passing the response to a Zend Framework (or Laminas in v8+) SAPI emitter. 4 or 5 lines of code + some error handling? But why? WHMCS's UI is not pretty and historically has been out of step with modern web development (eg. it's only just gone to Bootstrap v4). It's not really great for the marketing part of a business.

Just to add to this. If you wanted to retain the ability to click on the table row but make it more obvious by changing the background colour on hover like normal Bootstrap behaviour add this to your custom.css .table-list > tbody > tr { background-color: #fff; } .table-list > tbody > tr:nth-child(even) { background-color: #f8fcfd; } .table-list > tbody > tr:hover { background-color: #f5f5f5; } .table-list > tbody > tr > td { background-color: inherit; } .table-list > tbody > tr:nth-child(even) > td { background-color: inherit; } For some reason WHMCS's themes set the background colour on the TD cells and not on the TR row so even though the underlying row has had its background changed on hover, the TD colour overrides it to be white or blue. This change will work across all list tables (products, domains, tickets, invoices etc) which also really should have action buttons too but that's another fight to get WHMCS to change this awful design pattern.

ionCube24 might give you some better error reporting than standard IonCube. Also of course check if you've an error_log as that might give you a clue as to why PHP_FPM is disappearing.

I personally don't mind the Twenty-One theme. It's too basic for an out-of-the-box install perhaps but that's good. It's easier to customise than Six. Child theming, is going to be a massive time saver. Glad to see the back of Six and BS3. But yes, how many times have we asked for a roadmap.

Which version of PHP? Also check which version of Ioncube loader you're running. I've had similar errors with other software where the ioncube loader hadn't been upgraded but the user had moved to PHP 7.4. It worked fine on earlier versions of PHP or when they upgraded ioncube.

They *HAVE* learnt from Wordpress. The new child theming system is lifted almost identically from how Wordpress does it. You have a main theme and your custom mods are done in the child theme. It's what we asked for 7 years ago. https://requests.whmcs.com/topic/whmcs-child-themes-in-wordpress-style-to-make-upgrades-less-work

Be still my beating heart. WHMCS 8.1 beta just arrived with Bootstrap 4 support and child theme support. Downloading now.

That gives them a day for discussing implementation with customers & developers, alpha builds etc. I'm intrigued at how they're going to implement it without breaking compatibility with existing themes and modules.

We'll see. I'm trying to be optimistic. It's difficult in these times of pandemics, brexit and opaque WHMCS development. Hopefully it'll arrive alongisde Blesta adding Bootstrap 4 support (it's in their v5.0 beta sprints) so I don't have to get my head around using two different versions of Bootstrap finally..

Update: Bootstrap 4 support coming in WHMCS 8.1. https://requests.whmcs.com/topic/bootstrap-4-support#comment-20785