Vendor Name is not Updated in Messages After Vendor Name Change

Thanks for your message — our team will reply shortly.

In the meantime, you can also get instant help from our AI Assistant, familiar with all the docs and solutions we’ve shared over the years.

Hi @coralreefweb,

By default, WordPress usernames cannot be changed — this is a core WordPress limitation, as usernames are the only unique identifier assigned to a user account.

However, HivePress provides a solution through Display Names. Instead of relying on usernames, you can:

  • Go to HivePress > Settings > Users > Display Name
  • Select a display format that suits your needs (e.g., Full Name, First Name, etc.)
  • Have users re-save their profiles in WordPress (WP Dashboard > Users)
  • Once you change the Display Name setting and users re-save their profiles, the new display name will be used throughout the site, including in messages.

In regards to the question in the topic title; yes, custom code can be added to the functions.php file (using a Child Theme) - However, most users find a plugin like Code Snippets easier to navigate and manage custom code. Depending on what kind of changes you’re looking to make using a Child Theme may be useful.

Changing usernames is possible by using a workaround plugin like this.

I hope this helps!

Cheers,
Chris :victory_hand:

Hi,

Thanks for the report, the issue is confirmed. It occurs because it’s actually a WordPress-level behavior, since messages are implemented as hidden comments, and WordPress stores the author name separately for each comment.

We’ll address this by changing the logic so the displayed name is taken directly from the user account instead of the message/comment data.

I am already using child theme so Is there any automated system regarding this, Because manually it will take time and effort, I have done custom already in my site regarding in other option, it is possible you can give me any code for this where system become automated rather than manually changing name.

Thanks for the details.

There is no simple solution for this at the moment, but as mentioned previously, we plan to improve this behavior on the HivePress level by overriding the current WordPress logic.