Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


DennisHermannsen last won the day on September 2 2020

DennisHermannsen had the most liked content!

Community Reputation

71 Excellent

1 Follower

About DennisHermannsen

  • Rank
    Level 2 Member

Recent Profile Visitors

3057 profile views
  1. Aren't information protected in the whois database by default now for most registrars (without needing to pay a fee) because of GDPR? I don't recall that we have had to pay Hexonet for it.
  2. @bear mine was just a comment to clarify this: Sorry if that was not clear 🙂
  3. PHP 8 is not supported. Not officially, at least.
  4. We had a similar issue once. A hook for one of our modules wouldn't work on one WHMCS installation but worked fine on the rest of our installations. It was a problem for weeks. At the end, I just left it. It wasn't something critical. While we had the issues, I started developing another module which also used hooks. For some weird reason, this solved our issues with the first module's hooks - despite no changes being made to that module. The two modules didn't even use the same hook events. I still don't know what went wrong. Make sure that the addon is enabled (try disabling and enabling again). Try disabling most of your code in that hook except something line "logActivity('test');".
  5. Make sure that the amount is sent as a zero-decimal currency. If you need to charge 100€, you need to charge 10000. Check the gateway log to see what's being charged.
  6. As far as I know, they don't state "Lifetime" anywhere, but that's besides the point. You still have every right to use the version of WHMCS that your license covers, you just can't upgrade it. I don't see why it's misleading - but it sucks.
  7. There's not being done anything illegal. You're still able to use your owned license. If you aren't going to convert your license, you're going to be stuck with the owned license - just like you would if WHMCS ceased existing.
  8. UnblockIP works fine on our installation of WHMCS v8.1.
  9. I'm fairly certain they're out of ideas already. In a month or so, there's going to be a new post to this thread with a message looking like this: I can then see that the request get 1 or 2 upvotes because nobody uses that system unless they're referred to it... 😆 I don't get why everything has to be a feature request. Fixing something that's clearly broken shouldn't have to be requested. But someone at WHMCS will obviously argue that it's by design 🤯
  10. We did end up disabling it through .htaccess - but my main concern is that WHMCS doesn't use the maintanance warning instead, and that they basically scream "HEY, THIS WEBSITE IS INSECURE!!! TRY GOING TO /INSTALL TO SEE FOR YOURSELF"... That could be handled a lot more nice. Imagine if WHMCS also put up a public warning for each website that used en EOL version of PHP... 😅
  11. I'm currently upgrading our last WHMCS installation to WHMCS 8.1.3. It's taking quite some time because of the changes to the tblemail table. During all of the time (a period of 30+ minutes), everyone accessing our website is met with this message: Since I've enabled maintanance before starting the upgrade, I surely wouldn't expect WHMCS to show anything but the maintanance message. Also, why is WHMCS even broadcasting to every visitor that there's a /install folder present on the website? Everyone can access it by default (it requires no login) and thus everyone could mess everything up.
  12. A flag, setting, parameter. Call it what you want. You're able to disable it. Removing it from templates doesn't require edits "all over". It's two files. In case you're not using a default WHMCS template, this change would have to be made once. That's weird. On our 3 installations, it's only checking active services, as it should. It wouldn't make any sense checking inactive/cancelled services. No, it wasn't. You said nothing useful was added in any of the updates. Security updates are included with the latest versions of WHMCS. You can't expect WHMCS to solve issues for the few percentage of users of EOL'ed versions that don't want to upgrade to later versions. Wouldn't you think that I was out of my mind if I was still on version 1.3 and expected them to release security fixes for that version, just because I didn't want to upgrade (whatever the reason was)? It's not described in the documenation. WHMCS advises you to make customization to the menu by hooks - and it's great for modules. If a module needs to add a menu item, the module can do so by hooks. Everything is basically HTML and can be changed. See this: There's plenty of alternatives to WHMCS, and you're free to use whatever you like. I get why you're frustrated, but I don't get why you're blaming WHMCS.
  13. You can still just edit it as HTML... In your header.tpl, you have this: <section id="main-menu"> <nav id="nav" class="navbar navbar-default navbar-main" role="navigation"> <div class="container"> <!-- Brand and toggle get grouped for better mobile display --> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#primary-nav"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> </div> <!-- Collect the nav links, forms, and other content for toggling --> <div class="collapse navbar-collapse" id="primary-nav"> <ul class="nav navbar-nav"> {include file="$template/includes/navbar.tpl" navbar=$primaryNavbar} </ul> <ul class="nav navbar-nav navbar-right"> {include file="$template/includes/navbar.tpl" navbar=$secondaryNavbar} </ul> </div><!-- /.navbar-collapse --> </div> </nav> </section> Remove the includes - you'll have no menu and can insert whatever you'd like. It has been possible to do it like that since they introduced editing the menu using hooks. Ok, so every feature you don't need should be disabled by default? Why complain about it when there's literally a setting that disables the functionality that you don't want? If you want a software that's tailored to your needs, you should have one developed. Yes, it's difficult fixing bugs for a feature that isn't implemented yet. It's very rare that a feature that has been in WHMCS forever suddenly stops working. No one is telling you to update to WHMCS 8. You could easily do with an update to 7.7. When that's said, version 8 is stable. We're using it on 3 seperate installations with no issues. The only issues we've had was with the new user implementation, but they have been fixed. You can disable that feature, by the way - like most other features they introduce. My point was not that they supported it after EOL. My point was that you can't get mad at a company for not supporting something they clearly stated they won't be supporting.
  14. Well, if you don't find the security updates or bug fixes useful, you don't have a reason to upgrade then. There has been a lot of bug fixes for WHMCS since 7.6. My argument is still valid - if I was on v5.3 (or even 1.3), I could say the same thing as you. That I don't want to be forced to upgrade because v5.3 has everything I need. You can't expect WHMCS to support versions that have been EOL'ed a long time ago. You don't see Microsoft patching security holes in Windows XP, even though that version is the golden version af Windows to a lot of users. You don't need to use hooks to change the menu. You can change it as HTML if you want to. SSL checks can be disabled. If you were a software developer, would you really want to support every version of the software that you developed? Your code base will most likely have changed between major versions, which means fixing security issues is not the same for each version.
  • 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