Override registrar's DNS management
Please make sure the hook is working:
The file name must be: custom_hooks.php
and this file must be placed in the /modules/addons/solutedns directory
Make sure the arrray is returned by the function.
You could simply check if the function works by adding die(); to it and see if the client area stops working.
You must change the priority value accordingly.
The file name must be: custom_hooks.php
and this file must be placed in the /modules/addons/solutedns directory
Code: Select all
function SDNS_hook_ClientAreaMenuPriority() {
return array(
'ClientAreaPrimarySidebar' => 2,
'ClientAreaPrimaryNavbar' => 1
);
}
You could simply check if the function works by adding die(); to it and see if the client area stops working.
You must change the priority value accordingly.
This is the entry of my custom_hooks.php
Does it need both lines? Since I only need the PrimarySidebar
Code: Select all
[sinihost@server1 ~]$ cd public_html/store/modules/addons/solutedns/
[sinihost@server1 solutedns]$ cat custom_hooks.php
function SDNS_hook_ClientAreaMenuPriority() {
return array(
'ClientAreaPrimarySidebar' => 1
);
}
[sinihost@server1 solutedns]$
Does it need both lines? Since I only need the PrimarySidebar
I'm sorry to hear it still doesn’t work. As far SoluteDNS goes, changing the priority of the WHMCS menu system really is the limit of menu organisation without hardcoding it. As it seems the SoluteDNS value gets overwritten after all you may want to look at the other module in which way it’s overwriting it.
As long you can reach the WHMCS DNS Management page for registrar modules SoluteDNS can pick this up and redirect it to the SoluteDNS DNS Management page. So you might want to take measures to revert the changes made by the module to the WHMCS default value.
As long you can reach the WHMCS DNS Management page for registrar modules SoluteDNS can pick this up and redirect it to the SoluteDNS DNS Management page. So you might want to take measures to revert the changes made by the module to the WHMCS default value.
It's okay, I totally understood that this is not something relatively easy to overcome, since hooks priority is hardcoded on hooks.php itself, and every developer can use the same function, which we could never know which priority they use
SoluteDNS itself actually is usable in my system, but the reason I'm questioning about this, is so that customer don't have to go through different menu, for different DNS management module
SoluteDNS itself actually is usable in my system, but the reason I'm questioning about this, is so that customer don't have to go through different menu, for different DNS management module