lkitching

To allow for the pages of the client area to seamlessly integrate with our main website (we have WHMCS in a sub-directory). Previously when moving from V3 to V4 (before you supported it) we had to write a ton of custom CSS to "fix" the style of the older bootstrap elements (navbar, container widths etc). An upgrade to BS5 will be very useful for many of us.

You can use the API to build a script to do this, cycling through each domain and auto-recalculating the price. https://developers.whmcs.com/api-reference/updateclientdomain/

I have just spoken to WHMCS Support regarding this as we are seeing the same on our templates. They have opened a bug report but I forgot to note down the case number before closing the chat, if they email it to me I'll update here.

Someone might come up with a better way to do it, but I found adding the following to my custom.css helps in my case .dataTables_wrapper table.table-list { display: block; width: 100%; overflow-x: auto; -webkit-overflow-scrolling: touch; } It's basically pinching the code from Bootstrap's default "table-responsive" class and applying it to the existing wrapper (to avoid a ton of template changes). I have no idea why that is not being used already on all tables in WHMCS to be honest...

While a 3rd release isn't the "norm" it's still very new and will require testing on your own development environment. We're not in a hurry to upgrade - perhaps next month for us, unless there's a pressing issue in the meantime which means that needs moving forward.

+1 for this idea too, does it need raising on the feature request boards or is this something you have noted already @WHMCS John ?

Hello John, We closed the ticket as I needed to create a new ticket to upgrade to Priority Support as your lack of response was appalling. Once we upgraded, the response time was literally minutes. The issue was resolved by installing a hotfix provided by your support team, which I noticed (only afterwards) that it's available for download here too.

We are seeing this error too - do you have any timeline for an update on this?

We have just updated to the latest version of WHMCS (7.8.3) and are now seeing and issue whereby our overnight Cron Job is no longer capturing payments using the WorldPay FuturePay gateway. There are no errors when running the Cron Job manually via the command line with the verbose output and display_errors enabled. We are able to capture payments manually using the same details, however it takes two attempts to do this (the first attempt results in the payment being declined). There are no results being posted to the 'Gateway Log' regarding the payments when the Cron Job runs; however under 'Automation Status' we are seeing multiple "failed" captures (all payments are showing as failed, except the one capture we did manually). There are no "failed" capture attempts in the Gateway Log. We believe this is a bug in the system as we are able to produce the same results on 3 separate installations which all use the WorldPay FuturePay module. Has anybody else had the same issue? I noticed there was a hotfix for other gateways, but this does not appear to cover WorldPay FuturePay. I have opened a ticket with WHMCS approx 2 hours ago regarding this and am yet to receive a response: Ticket #VXY-048403

@WHMCS John if you need help getting it past the proof of concept stage; along with other things (such as Bootstrap 4 etc) I am sure that the community; including myself - would be willing to help.

That's great, how far away is this going to be from a release? Are we talking within the next 6 months or will it be beyond that?

This would be an awesome feature, but I think it's highly unlikely anything like this will be added anytime soon.

I'd vote for it :-)

Yeah - realised that it might not work now it's changed, cheers for that Brian!

My understanding of this is that while it's not shown in the "everyday" WHOIS database; there is still a case for ID protect to prevent details being shown in the "searchable WHOIS" (to those who have access). It may still be required for some customers; although they are probably shady ones at that.