Over the course of the next few weeks we would like to not only introduce you to the new features we've been working hard on for the next version of XenForo, but also introduce you to some new members of the XenForo team! We'll introduce those new team members in the upcoming HYS threads.
New minimum requirementsYou might remember that we started requiring PHP 5.6 starting with the release of XenForo 2.1. We base decisions like this on the "anonymous usage statistics" many of you kindly send to us periodically.
At the time we started the first HYS thread for XenForo 2.1 a whopping 44.7% of our customers were still using PHP 5.x. However, some time has passed and there has been a reasonable surge of usage in PHP 7.0 and above:
There is now only 14.4% of you running PHP 5.x (still too many!) and a whopping 86.6% of you are now comfortably enjoying PHP 7.x.
With this in mind, the time has finally come - we must leave behind PHP 5 and move onwards and upwards to PHP 7 and therefore XenForo 2.2 will require a minimum of PHP 7.0. But, don't worry, if you're worried that is too "bleeding-edge", just consider that PHP 7.0 was released nearly 5 years ago so, in actual fact, we'd strongly recommend you plan your upgrades to go as far as PHP 7.4 if you can.
But you don't care about that, right? What is actually new?!
User profile banners
Ah the old, familiar user profile header. So... blue... so... familiar. This won't do. If a user wants to make their profile look at least 86.6% better than before, as long as they have permission, they just need to click the "Edit profile banner" button to be presented with an overlay which allows them to browse for and upload an image from their device.
After uploading the image is now displayed in the user profile header. Still so... blue... so... much fancier.
Of course, there may be more interesting parts of the image to display, so you can change the focal point of the banner by clicking "Edit profile banner". All you need to do is click/touch and drag to reposition it to a different part of the image.
Still so blue... still so fancy...
Of course it's only fair that we apply the same pizazz to the member tooltip too:
From a forum admin's point of view there is, as mentioned earlier, a permission to control the ability to upload a profile banner or not:
And just like avatars, from the user edit page in your admin control panel you can view a user's current banner, delete it, or replace it with another.
And moderators who have permission to "Edit basic user profiles" can also view and delete the existing profile banner:
And that's it...! For this feature, at least... 👇
Username change managementWhile not particularly significant, we get around 50 requests per year from people wanting to change their username.
It's not a particularly arduous process but the user has to contact a staff member first, we then attempt to verify there aren't nefarious reasons for the request, then we check when they last changed their username as we don't like people changing their names too frequently, then we have to log in to the admin control panel to check the name isn't already in use before finally making the change, (sometimes) updating their custom user title and telling the customer that we've done it.
Wait... actually... that is arduous. So we made it simpler. And, while it is now simpler, there are quite a number of options to tune the system to your requirements.
First and foremost we've added a permission to control the ability to change your username. If you prefer not to allow users to change their own usernames then you can change this permission to "No" for the "Registered" group, otherwise you can keep it as "Yes" (its default) to enable the functionality.
Next, we've added an option so that you can control how frequently a user can change their usernames. By default we have set this to 30 days but it can be set to a much higher value, if desired, or set to a lower value or even 0 so users can change their usernames as frequently as they like. This is also the amount of time that needs to pass after a new user registers before they're able to change their username for the first time.
To change their username, a user simply needs to visit their Account details page and click the "Change" button that appears next to their current username. This will appear as long as they have the aforementioned permission and their last username change wasn't applied too recently.
The change username form looks how you might expect. We attempt to make it clear in this overlay that if there is a time limit on username changes then they will be prevented from changing the username again until that amount of time passes.
Once submitted the username is changed.
We also felt that it was important for there to be an approval process so that moderators or admins would be able to approve or reject username changes, if desired. This would allow some level of scrutiny of the name to make sure it isn't inappropriate or otherwise against your forum's rules.
Our solution for this is that username changes by default will go to the "Approval queue" before taking effect. It is made clear to the user that their username change is pending:
And moderators (who have the "Approve / reject username change" permission) will expect to find the username change amongst the approval queue:
The user will receive an alert / push notification once the change has been approved or rejected.
You may decide that having an approval process is unnecessary. In which case, you can allow users with permission to change their usernames without approval:
There is still quite a lot more to show you, including a couple more options. One such option allows you to control whether users are allowed to choose usernames that were recently in use by another user. It is disabled by default, but it is there if you need it:
One of our use cases for XenForo community is that we often like username changes to be public. We currently do this manually, as I mentioned before, by changing the custom user title. Going forward username changes are logged and displayed publicly automatically via a menu that appears on the user's profile (and member tooltip):
In all cases we will show a maximum of five of the most recent username changes in this menu. The "See more" link will display if you are viewing your own profile, or if a moderator (with the "Bypass user privacy" permission) is viewing your profile. This enables the user to see all username changes:
This brings us nicely onto the final option which relates to what we consider to be a "recent" username change.
By default the "Previous usernames" menu and overlay will only be available if a user has username changes within the last 30 days. The option allows you to set that to a higher amount or lower amount as required. Setting the value to 0 will disable displaying username changes publicly.
In some cases, a user may have a valid reason to change their username without it being displayed publicly. For example, they may be concerned about privacy so they would prefer the change to be kept private. The user would likely contact a member of staff privately to request the change. There is a new checkbox that appears below the username field when an admin is editing a user:
Username changes done in this fashion are not displayed publicly, but will still display in the "Previous usernames" menu and overlay for the aforementioned moderators with the bypass privacy permission and the user themselves.
Note that while editing a user we also display the date of their last username change, and the date of their next allowed username change.
While username changes have traditionally (and will continue to be) logged in the "User change log", this new username change feature actually maintains its own dedicated log called the "Username change log".
The toggle you see here allows you to set whether a particular username change is displayed publicly or not.
When you upgrade to XF 2.2 we will attempt to populate this log with existing values from the user change log.
In some cases there will only be a limited amount of data populated as we haven't always kept username change logs in the main user change log indefinitely. Username changes that we import from the user change log will not be displayed publicly.
Speaking of usernames, we do have another small feature that is relevant to both users registering and username changes.
Username validation and generic input validationWhile this feature is very small and currently only used to validate username input, for developers it provides a small framework to provide generic input validation in other places. But we'll mostly focus on its application to username validation, for now.
Quite simply when a user is registering or attempting to change their username, we verify what they have written so far is a valid username and display an appropriate error. The following video should demonstrate how it works:
For developers, the implementation is as simple as adding a
validation-urlattribute to the input. That URL is responsible for performing the logic required to validate the username (running it through the username validator in this case) and returning some JSON params to indicate if there are errors and what the errors specifically are.
Speaking of developers, we will have a special HYS thread for you to get your teeth into at some point in the next few weeks so keep watching!
Security locking user accountsThere are a few situations where you might wish to protect a user's account. You might suspect unauthorized access on a specific account or have a general concern that some breach has occurred.
We attempt to cater for both of these situations by allowing you to "Security lock" user accounts. Primarily this is done when editing a user in the admin control panel:
We'll outline in more detail the behaviour of each option below.
User must change passwordIf you suspect a more general breach and you want a user to change their password when they next log in to their account then this is the option to choose.
A user who has their account locked by this method will be met with the following screen when they use this account:
After confirming their existing password and entering a new password, the user is redirected to the URL they tried to access originally.
User must reset passwordIf you suspect a more targeted attack against a specific user, or you detect unauthorized access to a specific account then requiring a password reset is a better approach.
The difference with this approach is that a password reset email is sent to the user's registered email address. In other words, the user has to demonstrate they have access to the email address on their account before being able to change their password and log in.
A user who has their account locked by this method will be met with the following screen when they use this account:
Shortly afterwards, an email should arrive to the email address on their account which will look like the following:
The "Reset password" button will take them to a form where they will be able to choose a new password:
And in this particular case it must be a new password. We prevent the user from picking the same password they already have.
Again, once the password has been changed, the user can continue to use the site as normal.
But, what if you have concerns about multiple users...? 👇
New "Batch update users" actionsDue to the nature of some security breaches, you may wish to security lock most, or even all, user accounts on your forum. To enable you to do that we added the ability to set the security lock via "Batch update users":
As well as setting either of the security lock types in this way, you can also remove existing security locks too via the same action by setting it to "None".
Note that to prevent awkward situations, security locking administrator accounts in this way isn't possible.
While not related to security locking, we have also added the ability to set user states via "Batch update users" too:
And as the well-known saying goes: "All good 'Have you seen...?' threads must come to an end" but, don't worry, we'll be back later this week to introduce you to a new face and more new features.