HostingMe

Thank you @brian! changing the opening IF statement works perfectly.

Hi All, I'm using a module that adds integration to a VPS supplier and their module adds controls for a VM in the product details primary sidebar. I'm looking at renaming the labels on these controls and add a font awesome icon. Using the hook below everything works as expected on a VPS product details page however if you try and navigate to a different product type, like shared hosting for example, you're presented with the following error: Error: Call to a member function setLabel() on null in /home/domain/dev.domain.com/includes/hooks/client-sidebar-vps-rename.php:40 This is the code I've used for the hook: <?php use WHMCS\View\Menu\Item as MenuItem; add_hook('ClientAreaPrimarySidebar', 1, function (MenuItem $primarySidebar) { if (!is_null($primarySidebar->getChild('Service Details Actions'))) { $primarySidebar->getChild('Service Details Actions') ->getChild('Custom Module Button Start VM') ->setLabel('Power On') ->setIcon('far fa-play-circle'); } });

Thanks Brian, worked perfectly.

Hi all, I'm currently using 'Natterly' as my live chat provider which supports adding visitor details direct to the chat widget. Currently I'm using {$clientsdetails.firstname} and {$clientsdetails.email} to pass the information to the widget but what I'm finding is if user 1 is managing users 2 account the chat widget shows users 2 details. What I'd like is the chat widget to show users 1 details which I'm not sure on how to do. This is the full integration code which I'm currently using: var chatbox = new NatterlyChatbox("[Your Site Token Here]") chatbox.visitor.name = '{$clientsdetails.firstname}'; chatbox.visitor.emailAddress = '{$clientsdetails.email}';
 chatbox.render(); I've also added a screenshot below which hopefully helps explain what I mean. Any help on this would be appreciated. Thanks in advance. Steve

I saw a very similar issues with web hooks failing a while back during beta testing. I found the issue was related to Stripe having the wrong metadata information for some customers. To resolve the issue I logged into Stripe > Customers > Selected the customer > Scrolled down to the Metadata section and checked the information there matched WHMCS. If not update to match WHMCS. As an example if the Customer ID within WHMCS is 10 and Stipe has the metadata ID as 15 the web hook would fail. Changing the metadata ID to 10 in Stripe would fix the issue.