Community Builder 2.4.7 Released!

Community Builder 2.4.7 can be freely downloaded by all registered members

 

We just released Community Builder 2.4.7 with 9 new features and 14 bug fixes!

The main new features (full CB 2.4.7 changelog) include:

  • Name format options with First Name Only, Last Name Only, First Name and Last Initial, First Initial and Last Name, First and Last Initial settings.
  • Randomly generated usernames for fallback option will generate Joomla required username
  • Password unmasking feature has been added - this way you no longer need extra verify password field
  • New profile edit tab vertical layout has been implemented
  • Updated Bootstrap to version 4.5.2
  • Support for latest MySQL 8.0.17+

Community Builder 2.4.7 is a recommended upgrade for all CB sites.

Our demo website has already been updated to Community Builder 2.4.7, so you can see it in action along will all our Joomlapolis add-ons.

As always, you should first test on a cloned environment before upgrading your production site.

Looking ahead to Community Builder 2.5!

With the future CB 2.5 release, simultaneous support for Joomla 4.0 and Joomla 3.9 will be achieved using updated CB libraries. This will make future upgrades from Joomla 3 to Joomla 4 easy. In order to achieve this and be able to use modern PHP language techniques and future PHP 8 compatibility, we are issuing now an advance notice of end of PHP 5 support starting with the upcoming CB 2.5 release. Going forward, the new minimum PHP version will be same as that of Joomla 4, namely PHP 7.2.5.
 



krileon's Avatar
krileon replied the topic: #321561 3 days 1 hour ago

That is: why just one password field?

Verify input behavior has been around long enough for the UX of it to be studied and the results are basically that it's a pointless field. Statistically the vast majority of people actually get their password correct the first time and actually typo it the second time in the verify input field. This creates doubt and the end result is users have to clear both fields and type their password yet again if you don't end up just losing the user entirely. This is all avoided by simply toggling visibility of the password to verify its value and if they did manage to type it wrong they can recover with forgot login, but statistically the chance of that happening is little to none since again people get their passwords right the first time basically 99% of the time. Given we're in a world of modern password managers as well people often aren't typing their passwords either.

Suppose you accidentally make a typo in your password. A second password field would detect this, before saving.

They can unmask the password to check it if unsure. Worst case they use forgot login to reset it.

With all that said the verify input field is not going away and by all means continue to use it if you want to. The unmasking feature is also entirely optional, but is default enabled so simply disable it if you do not want it.
stimpy's Avatar
stimpy replied the topic: #321559 3 days 1 hour ago
I don't understand the password unmasking feature. That is: why just one password field? Suppose you accidentally make a typo in your password. A second password field would detect this, before saving.
krileon's Avatar
krileon replied the topic: #321471 1 week 5 days ago

crealiagroup wrote: Hello, what about a planning of CB for Wordpress?

That won't be for awhile, but ideally yes we'd like to support Wordpress and Standalone solutions. It's so far off though I can't really give any specifics. We need to implement Symfony components and effectively rewrite all of CB first, which is the primary goal of next years development.
crealiagroup's Avatar
crealiagroup replied the topic: #321462 1 week 6 days ago
Hello, what about a planning of CB for Wordpress?

Facebook Twitter LinkedIn