It'd be super convenient if a total was shown for the various Products/Services, Domains, and other products!
I have a client with a TON of domains. Active, Expired, Transferred, etc... It'd be a real time saver, if those counts could be also be included within the appropriate section. I realize that there's a total count up top, in the Products/Services box, but some of these pages and up becoming *super* long to scroll back and forth in.
Welcome to the October 2018 Community Wrap-up a look back at some of the highlights from the community over the last month. WHMCS.Community is here to help you so please do send your feedback thru!
WHMCS.Community October 2018 Statistics at a glance:
307 new members joined WHMCS.Community
338 new topics where created
1,110 replies were crafted by WHMCS.Community Members
Continuing his reign as the most reacted to community member is@brian! on 49 points! In second place on 14 points is @Kian with @hanstavo finishing out the leaderboard on third place with 11 points
Reactions on the community are a key way we surface great content on WHMCS.Community. Every reaction to a post might see you or a thread you've contributed to added to the Top Picks & Leaderboard and soon, your reaction points will count towards your status on the community
Getting help from WHMCS.Community Team
It's been a while since we last reminded people about the ways to contact the Moderation team when you need assistance such as changing your username, finding the right place to post or just asking a general community-related question. The place to do that is the WHMCS.Community Assistance board this ensures that any one of the Community Team members can assist you as quickly as possible.
That's a wrap for October!
And that wraps up the October 2018 wrapup, as always please provide any community-related feedback in the General or WHMCS.Community Assistance Board
Man, I must have overlooked. Thank you! 🙂
Apparently you should always use one "?" in that kind of URLs. Stupid from me.
Have a very nice Christmas and the best wishes for 2019 in advance.
So I was sending an upcoming scheduled maintenance email to our clients and due to a server-side process limitation, the email sending process was terminated too early.
It has sent the email to some clients, but not all.
Is it possible somehow to re-send the email to the clients that didn't receive the email the first time around without getting too manual?
Thanks WHMCS community 😎
Create a file named for example StrongPasswordGenerator.php in includes/hooks directory. Here's the content:
$password = substr(str_shuffle('abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!@#$%^&*()-=+?'), 0, $length = '10');
Capsule::table('tblhosting')->where('id', $vars['params']['serviceid'])->update(['password' => Encrypt($password)]);
add_hook('PreModuleCreate', 1, 'hook_StrongPasswordGenerator');
Before WHMCS generates the service, this script will override the default password with a stronger one. Of course I suggest you to change the function that generates the password because the one I used is not that great. I posted the script just to provide an example.
Will using the DirectoryIndex directive in .htaccess affect WHMCS in any way? All the calls WHMCS tries to make seem to be directed to index.php, so there does not appear to be a problem.
Is this the best way to change the default home page or is there a better way?
Guys I need some help translating the text "Join our mailing list" customer sees during the purchase process into spanish language. This is a screenshot: http://captura.servidoresseguros.info/134b662b1c0a
I already use an overrides file, but I was not able to find that text.
I've searched and noticed this topic has been discussed before but I'm sorry to say the new solution in WHMCS 7.5+ is still not good enough.
In today's world, we need to have proper Strong Passwords to maximize the security of hosting accounts, FTP, DB, Mailboxes etc.
For example in Plesk and cPanel these password security matters have been taken seriously but in WHMCS still not yet.
In Plesk, there are 5 levels of password strength:
1. Very Weak: These passwords are typically short and use only one type of characters (lower or upper-case characters or digits). Example: password. This security level prevents simplest password-guessing attacks.
2. Weak: These passwords are typically short and mostly use one type of characters (lower or upper-case characters or digits) with a couple of characters of a different type. Example: password12. These passwords provide basic protection from password guessing.
3. Medium: These passwords are typically short and contain characters of at least two types (lower or upper-case characters, digits, or special characters). Example: Password12. Such passwords provide reliable protection from attacks that capture passwords.
4. Strong: These passwords are at least 8 characters long and have at least one occurrence of upper and lower-case characters, digits, and special characters. Example: P@ssw0rd12. Such passwords provide strong protection from brute-force attacks.
5. Very strong: These passwords are at least 16 characters long and include multiple occurrences of upper and lower-case characters, digits, and special characters. Example: ~!my_P@$$w0rD123. Such passwords provide the best possible protection, though they are rather hard to remember.
If you use Plesk (set to Strong passwords) with WHMCS (passwords, letters, numbers, special characters) you simply cannot get an account automatically created in Plesk because the WHMCS passwords are too weak.
I did a test with WHMCS on my system, it creates long 14 character passwords but the mixture of upper, lower, numbers and characters is very simple and weak - no use of # or some other characters noticed.
The only way o get this to work is to set Plesk to Medium passwords, and this leaves the server open to lower strength passwords which can have major consequences because we all know users are "lazy" and choose simple passwords that are easily hacked.
Please please please WHMCS, improve your Auto Generated Passwords, or add a section where we can define the passwords to be used in more detail.