Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


DennisHermannsen last won the day on March 4

DennisHermannsen had the most liked content!

Community Reputation

109 Excellent


About DennisHermannsen

  • Rank
    Level 2 Member

Recent Profile Visitors

5008 profile views
  1. The easiest way would be to set a new due date for the services (like tomorrow) and then generate due invoices for the client on their summary tab.
  2. That's because you're not looping through it. There's a similar request in this thread:
  3. You need to loop through $service_config_options. They are the configurable options for the service.
  4. Did you remove the module from within WHMCS > Settings > Addon Modules?
  5. The customfields needs to be an array of base64 encoded serialized array. For PHP, you would do it like this: 'customfields' => array(base64_encode(serialize(array("1" => "Google"))), base64_encode(serialize(array("1" => "Google")))),
  6. Updates won't make changes to anything but the WHMCS stuff. Everything that's in between the following lines could be changed: ### BEGIN - WHMCS managed rules - DO NOT EDIT BETWEEN WHMCS MARKERS ### ... ### END - WHMCS managed rules - DO NOT EDIT BETWEEN WHMCS MARKERS ### Everything outside of that block won't be changed by updates to WHMCS.
  7. Increase the value for memory_limit in your PHP configuration. You've currently only configured the limit to 32MB. Set it to 128MB.
  8. You don't put .tpl in the $ca->setTemplate() function.
  9. You can modify the hook or ask the module developer to modify it to not return data if the TLD is one that doesn't allow changes to the contact details. Otherwise, you can create a hook that uses JavaScript to remove the Contact Infromation tab.
  10. It's your registrar module that allows the client to access the Contact Information page. The module should not return anything in the _GetContactDetails and _SaveContactDetails for those TLDs.
  11. That's what these fields are for If they weren't meant to provide the user a way to set their name servers once the transfer completed, then what's the point of even having those fields? Which is why it makes sense to set the name servers on a successful transfer. I don't have a problem with this btw. Hexonet did a great job of cleaning up the process and it gave me the idea of implementing the same feature for our own registrar modules. I did, however, have a problem with it a few years back. WHMCS support could not give me any explanation as to why those fields existed and I also didn't get a clear response as to whether the name servers were supposed to be updated automatically or not. It feels like a legacy thing that was never removed. Nobody knows why it's there or what it does. You're also only able to set the name servers once per order which also doesn't make any sense. But hey, if you ask WHMCS today why those fields are on the order formular, they're most likely going to tell you that it's so registrars has the ability to update the name servers after a successful transfer.
  12. You'd think it was supposed to happen automatically but it isn't. I have no idea why WHMCS even allows the customer to enter the name servers when ordering a domain transfer. Hexonet has modified their Ispapi module to allow for a name server change once the domain has been transferred.
  13. I can't believe this has to be said so often but @brian! is no longer active on the forums. You can search for a developer to do the work for you: https://whmcs.community/community/137-service-offers-requests/ - it's most likely going to cost you a few bucks.
  14. I'm know, but that was not my point. There's nothing you or anyone of us can do about it though. It's been a problem for more than a year and WHMCS staff are well aware of it at this point.
  15. It's ModSecurity, There's nothing you can do about it. Except upload the code to a third party service such as Pastebin.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated