ERROR: User Display Name Is In Use

Hi @samdobrow,

1. Could you please go to your site’s Dashboard -> Plugins -> Installed Plugins -> and send a full screenshot with everything you have installed related to Profile Builder (make sure the plugin version can be seen)?
2. Could you please go to your site’s Dashboard ->Profile Builder -> Settings -> Advanced Settings -> Fields -> and send a full screenshot from there (please make sure all the settings from that page can be seen)?
3. Could you please send a screenshot with the exact error message you see when you try to edit a user?

You can use a site like https://snipboard.io/ to share the screenshots.

Best regards,

I have the same problem and this problem was not here in the previous versions. You have a bug there. If this field is activated:

Unique Display Name

Unique “Display Name” for users.

By enabling this option, users will not be able to choose a “Display Name” that is already used by another account.

then you control the display name even in the edit in the administration and not JUST when creating the account or not JUST for any other users EXCEPT for the user I am editing.

• This reply was modified 10 months, 3 weeks ago by keengamer.

Hey guys,

Thank you for reporing this, I’ve created a task and forwarded it to our development team, where they will get it fixed in one of our future updates to Profile Builder (we release a new update every two weeks, so the fix will come in one of these future updates).

Note: At the moment (until the issue is fixed) you can either downgrade the Profile Builder plugin to the previous version (3.10.7), this version can be downloaded from here (at the bottom of the page you can choose the version), or you can disable the “Unique Display Name” setting (Profile Builder -> Settings -> Advanced Settings -> Fields). With either one of these options, you will be able to successfully update the user without changing their Display Name.

Best regards,

Hi @alexandrubodea

I have the same issue, I was using version 3.10.9

I have downgraded to version 3.10.7

This has solved the issue for now, do you know if this next release will have the fix in place?

Many Thanks,

Andy

Hi @ahillmortons,

The fix for this issue will come in one of our next 2 updates to Profile Builder (most likely the next one). These updates will be released somewhere in the first half of February.

Best regards,

Hi @alexandrubodea

Thanks for your reply, now I have rolled back to 3.10.7 I’m getting the below security notice, I’m wondering if there’s anything I can do to get the latest version work so I’m not getting security notices?

Or is there something I can avoid using on 3.10.7 to negate any security flaws?

Many Thanks,

Andy

WP Toolkit has detected new vulnerabilities on WordPress sites under your care. It is strongly recommended to update or disable vulnerable assets on these sites. You can also configure WP Toolkit to perform automatic actions when vulnerabilities are detected.

Vulnerability
The following vulnerabilities were found in deactivated assets and have to be addressed manually:

WordPress Profile Builder plugin <= 3.10.7 – Insecure Direct Object Reference to Sensitive Information Exposure via user_meta Shortcode vulnerability

WordPress User Profile Builder plugin <= 3.10.8 – Missing Authorization to Plugin Settings Change Vulnerability

Hi?@ahillmortons,

In this situation, maybe the best will be to update the Profile Builder plugin to the latest version (3.10.9) and then disable the “Unique Display Name” setting (Profile Builder -> Settings -> Advanced Settings -> Fields). This way you will be able to successfully update the users without changing their Display Name (without encountering this issue).

Note: I’ve also spoken with the development team and they confirmed that this issue will be fixed in our next update to Profile Builder (which will be released in approximately 2 weeks).

Best regards,

thanks! This has been doing my head in!! Spent too much time trying to figure it out, so THANK YOU to the poster of this issue. I’ve turned off the offending display unique.. field and now its all working fine.