Display Name
When is this simple, highly requested addition going to be added? Itโs been on the road map for over a year.
What's the difference between name and display name?
Yes for privacy I'd like a way to have a username only so that people don't have to give out their full names
+1
+1
Marekย the difference is between user/login name VS display name. A display name makes it so your login name isn't exposed and subject to attacks like brute force. Also, it can preserve privacy, especially if your user name is also an email address.
Verity Cantareย simply you can say display name is as NickName
+1
Not only that, same for a DOB, ideally synced with FluentCRM.
Also give the ability to have users for businesses. Untapped potential depending on your community use case Shahjahan Jewelย #littlethingsmakebigthings
I have a number of businesses signed up and itโs not practical telling the user to change their First & Last Name to their business name.
Hello David Freeman, talked it over with the team.
Our team suggested that, for now, the simplest workaround is just to use theย First Name field for businesses/brand names. The Last Name field is optional, so you can simply set your First Name to your business or brand name and leave Last Name blank. That's what will show across the community (posts, comments, member cards, etc.).
Under the hood, the display name is just First + Last concatenated โ so "Alias" in First Name with no Last Name shows exactly as "Alias" everywhere.
(Attaching a screenshot of the profile edit page for reference.)
If this is something more users are looking for, do let me know โ I'll bring it back to the team. I always want to help the community.
Hope that helps for now.
Thanks for checking with the team, I appreciate it.
However, using the First Name as the business name and leaving Last Name blank changes the userโs core WordPress data across the entire site, not just FluentCommunity. We need to retain first and last name for contact/admin purposes and other integrations.
Customers purchasing through WooCommerce are also typically required to provide a last name for billing and order details. This also applies to other commerce plugins like FluentCart, which rely on first and last name for customer records.
The expected approach, consistent with WordPress and most community platforms, is to use display name for the public/business name rather than repurposing core identity fields.
Otherwise, this is likely to cause issues over time, especially in a marketplace environment.
David Freeman, If User Sync is enabled, leaving Last Name blank in FluentCommunity would write that back to WordPress core and could affect WooCommerce billing, FluentCRM, and other integrations โ so your concern is valid.
However, if User Sync is disabled, FluentCommunity and WordPress operate completely independently. In that case, leaving Last Name blank only affects your community profile and won't touch any core WordPress data. You can give it a look.
Again, I will talk about your concerns with this comment to the team. Thank you.
Iโve created a small MU plugin that automatically syncs the WordPress display name with FluentCommunity when itโs updated, so the correct public/business name shows consistently across posts, comments, and profiles without affecting first and last name fields.
If anyone would like a copy just let me know ๐ค
David Freeman, Great! Is it production-ready? Do share, please.