Hi Jerome,
Thank you for your patience.

I am sorry, that is a bug. Please remove the code I supplied earlier(It was a mistake, I supplied code from profile data control and not moderator).

The problem is happening because BuddyPress ignores the xprofile data and uses WordPress user meta data for these ignoring some of our actions. This happens when you use a mapped WordPress field(Biography, first name, last name).

I am working on a solution, please expect a plugin update by 21st.

Thank you
Brajesh

Hi Jerome,
Thank you for your patience.

I have investigated the issue thoroughly and the only solution is to avoid using wp-bigraphy/similar mapping and use the BuddyPress Xprofile field(create one named Bio).

The problem is with BuddyPress and It will have impact on your search as well.

When a user saves a field which is mapped to WordPress fields, BuddyPress does not have it in the xprofile field data.

If you had a field in xprofile and you mapped, the old data will remain there and will never be updated. In case of mapped fields, It updates user meta.

The problem with this approach is it is neither consistent, causes data redundancy/inconsistent state and issues with Profile Data search. It seems, when this feature was introduced(It has been in recent years), It did not go through thorough testing.

I will suggest avoid using this field mapping as there are no visible benefit of mapping the field.

Regards
Brajesh