Leaderboard

Storing plain text passwords anywhere on the server; that's the bad practice. Though I understand it for what's being done there, it's in a format that someone with server access (though leaked password, elevated access exploit, coding error, server misconfiguration and so on) could read and use to gain access there. It helps reduce security.

Feature requests don't get taken seriously now even if they do pick up interest, it is at the point that the entire feature request thing has lost the interest of the majority of your client base. Some are 7+ years old with a LOT of up votes (considering the very small pool of people active on the requests site) that have not even been acknowledged by WHMCS in any meaningful way. The obvious solution to this problem is NOT to get in to the habit of keeping a copy of the six theme as any important changes will then likely be missed as that bad habit forms, the proper solution as implemented in the majority of serious projects is the ability to either point at a custom css file via the web ui so theme: six Custom css: template/custom/mycustom.css I might put in a feature request to abolish the feature requests section and start it again with a fresh clean slate and invite the entire customer base to participate again with the promise that WHMCS will acknowledge and make final decisions within 3 months of XX threshold being reached, then I will check back on this request in 2025 🙂

Always the same tune, John. You tell members/users to go find the requests, which is far removed from the flow of conversation and sees little participation as a result. It's where ideas go to die ™️. To have that be useful, it should at least be clearly linked to here in the community, and share the community login. It would be helpful if it was simpler to navigate and find what you need and so on. Before you say it, I know, I should start a request in the requests system, to update the requests system. 😉

Bear in mind that will store his remote user/pass in plain text within that file. I get why it's being handled that way, but it's not terrible good practice overall. 😉

<?php # Primary Sidebar cPanel Login Form # Written by brian! use WHMCS\View\Menu\Item as MenuItem; add_hook('ClientAreaPrimarySidebar', 1, function(MenuItem $primarySidebar) { $client = Menu::context('client'); $clientid = 4; if ($client->id == $clientid) { $service = Menu::context('service'); $servertype = $service->product->servertype; if ($servertype != ""){ return; } $username = 'username'; $password = 'password'; $cpanelhref = 'https://www.domain.com:2083/login/'; $webmailhref = 'https://www.domain.com:2096/login/'; $bodyhtml = '<form method="post" action="'.$cpanelhref.'" target="_blank"> <input type="hidden" name="user" value ="'.$username.'"/> <input type="hidden" name="pass" value ="'.$password.'"/> <input class="btn btn-success btn-sm btn-block" type="submit" value="'.Lang::trans('cpanellogin').'"/> <input class="btn btn-primary btn-sm btn-block" type="submit" formaction="'.$webmailhref.'" value="'.Lang::trans('cpanelwebmaillogin').'"/> </form>'; if (!is_null($primarySidebar->getChild('Service Details Actions'))) { $primarySidebar->getChild('Service Details Actions') ->removeChild('Login to cPanel') ->removeChild('Login to Webmail'); } $primarySidebar->addChild('cPanel Login', array( 'label' => 'cPanel Logins', 'icon' => 'fa-server', 'order' => 20, 'footerHtml' => $bodyhtml, )); } }); there are a handful of variables that you will have to update... $clientid -> this is the client's ID value - you can get it from their client summary in the admin area. username & password -> obviously change these to those given by your client. cpanelhref & webmailhref -> replace domain.com with the url of your client. if you don't want to show the webmail link, then just remove the last <input> line from the hook. for the given user, assuming you get the username, password and URL correct, it should log them directly into cPanel without asking for login details.

Pretty simple to treat it like a typical config file in a lot of software. custom.css.txt (with a note to rename it)