Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


DennisHermannsen last won the day on September 2

DennisHermannsen had the most liked content!

Community Reputation

58 Excellent

1 Follower

About DennisHermannsen

  • Rank
    Level 2 Member

Recent Profile Visitors

2275 profile views
  1. Yeah, WHMCS should do their job. They use their own software - but I hardly doubt they would ever use the beta themselves. Heck, they don't even use v8 yet! They don't even have enough faith in their own software to use the latest version 😅
  2. There's UnblockIP from ServerPing: https://www.serverping.net/clients/cart.php?gid=3
  3. WHMCS v9 - Admin Area refreshed (3 blank spaces removed)!
  4. People have been asking that question for years, yet WHMCS never answers it. All WHMCS do is mention the feature request - but those feature requests are many years old and have hundreds of votes without ever being implemented. - https://requests.whmcs.com/topic/cancel-x-days-overdue-invoices Pssst.. You wanna hear a secret? That topic was also set as "Investigating" two years ago. It's not going to be implemented. https://web.archive.org/web/20180408220313/https://requests.whmcs.com/topic/cancel-x-days-overdue-invoices WHMCS tries to make it seem like the request system is really great and that everyone has a chance of getting their suggestions added - it only requires enough votes. Well, not only enough votes... They also need someone who actually cares enough to implement one of the most requested features for years.
  5. I'll have to stop you right there, John. The same thing goes for regular clients. In theory, you could just change their details. It's just a hell lot easier to delete everything than to have hundreds of inactive users (all with unique email addresses). ... And so can a client. But - if the client wants their account deleted, we should (and must) delete it. If a user (not a client) actually decides to contact us and asks us to have their account removed, why shouldn't we be able to delete it? Sorry, but I just can't wrap my head around why a 'Delete User' button and/or API function has been made. Reasoning? We're forced to delete data about a client if the client requests it. Not doing so is punishable with huge fines. In 2018, WHMCS made a lot of steps to make it look like they cared about GDPR - and then they basically ruined it with a single update and can't understand why we feel something is wrong. Please, please, please, please (!!!!!) let us know why it has now taken 3 releases (I reported it before GA) and there's still no solution to this. It's really just a matter of deleting the user the same way that a client is deleted. Sorry about my tone in this reply, my it really frustrates me. You can't make a release that is so GDPR focused back in 2018 and then ruin it two years later saying: "You know, you can just manually edit out the personal information for each user" - WE COULD VERY WELL DO THAT WITH CLIENTS AS WELL BEFORE 2018, It's just a lot easier NOT having to do that.
  6. Of course you shouldn't just go on a rampage and delete random users... You should only delete users that ask for it. Example: I am the owner of an account. 4 other are invited to access my account. I contact the company and ask to have my user account deleted. They delete only my user account - the 4 other users will still have their account, but won't be able to access my account as it no longer exists.
  7. I don't think I asked to be misunderstood, but I guess people can't see beyond the tip of their own nose... Let me rephrase in bullet points: It's very annoying that this hasn't been fixed This issue should have gotten more focus WHMCS should have given a statement about this issue instead of handling everything through tickets however: You can't just magically fix an issue without knowing why it happens I tried comparing our cases, and there's no common thread for the issue
  8. You should be able to delete different users. It shouldn't delete every user connected to a client - it should just delete the user that you select. That ain't hard.
  9. That's just not good enough. The account should be completely deleted. If a customer asks us to delete their account, we cannot keep any information about them. Everything has to go. It's very weird how WHMCS didn't even consider that keeping the email address and name would be an issue.
  10. But that doesn't mean that they know why the bug happens. They can't just fix something if they don't know why it happens.
  11. It's not shocking that it's not fixed. It can be quite difficult to fix something that you don't have a lot of information about (like why it happens, how often it happens, for who it happens etc). I've been trying to compare our cases of this bug, and I have absolutely no idea why it happens - there's no common thread - and when I finally think I have found the common thread, there's a case that disproves my theory. What actually is shocking is that, despite this thread being very active, WHMCS hasn't dropped by to say anything for a long while. Bugs can be difficult to fix. Giving a written update about a specific bug isn't that difficult. Instead of gathering information through multiple tickets, maybe WHMCS should use this thread (or create a new thread) to gather all the info they could. Other users could then voice their own experiences.
  12. You cannot downgrade unless you took a backup just before upgrading. If that's the case, just load a backup.
  13. Thanks for that, @WHMCS Peter - it almost works perfectly. I've found one issue, though. use WHMCS\Authentication\CurrentUser; use WHMCS\User\Relations\UserClient; add_hook('ClientAreaSecondaryNavbar', 1, function (MenuItem $primaryNavbar) { $user = CurrentUser::user(); if ($user && $user->isOwner(CurrentUser::client())) { //do stuff } }); I've created a hook for my module. This module adds a link to the secondary navbar. If you log in as a user and have access to multiple accounts, the following error will be thrown right after you log in: TypeError: Argument 1 passed to WHMCS\User\User::isOwner() must be an instance of WHMCS\User\Client, null given, called in /home/user/dev.example.com/client/modules/addons/gdpr/hooks.php on line 12 and defined in /home/user/dev.example.com/client/vendor/whmcs/whmcs-foundation/lib/User/User.php:0 Any idea what that could be caused by?
  14. @WHMCS Peter that just seem to show if anyone is logged in. In my case, I need a way to differentiate users and clients 🙂 How would that be done best?
  15. Nice! https://classdocs.whmcs.com/8.0/WHMCS/User/User.html It seems like we should use isOwner() to check if it's a user or a client.
  • 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