How to disable the TERMINATE module command operation for some or all admin users?

[itomic]

Hi All,

 

We've had a couple of occasions where hosting accounts have been accidentally terminated using the terminate module command in WHMCS, and I want to stop this.

 

I can see that it's possible to enable/disable *all* modules commands ("Perform Module Command Operations") per admin role, but I want to see if I can disable *only* the terminate command.

 

WHMCS documentation doesn't appear to be coughing up the answer.

 

Thanks for your help,

 

Ross

[SeanP]

I don't think you can get that granular with the permissions. I think it is all module commands or none. You might want to request this as a feature:

 

https://requests.whmcs.com

[itomic]

Thx.

 

https://requests.whmcs.com/responses/more-granularity-for-permissions-for-module-command-operations

[sentq]

it can be done using hook actions, you can specify list of admin ids allowed to terminate products, if anyone else tried to use the termination command it will aborted

[SeanP]

sentq has a good idea here. You can do this using the PreModuleTerminate hook. The "Terminate" button will still show, but you can have it abort, if the admin is not allowed to run it.

 

Create a new hook file under your includes/hooks folder called something like "termperm.php". Within that file, use the following code:

<?php

if (!defined("WHMCS"))
   die("This file cannot be accessed directly");

function terminate_permission($params) {

 // Admin IDs who are allowed to use the Terminate function
 $termallow = array('1','2','3');

 if ($_SESSION['adminid'] && !in_array($_SESSION['adminid'], $termallow)) {
   $return = array("abortcmd"=>true);
   return $return;
 }

}

add_hook("PreModuleTerminate",1,"terminate_permission");

?>

 

Be sure to edit the "$termallow" array, with a list of admin ids that are allowed to use the Terminate function.

 

I tested this on my dev server, and it worked well for me.

Edited April 9, 2015 by SeanP

[AT_]

Is there by chance a message that can be printed explaining why it is aborted? Aborting without displaying a reason isn't ideal. Has anyone needed to do this?

Something like:

return [
    'abortcmd' => true,
    'abortmsg' => 'Your reason message here.',
];