This is what I found out.
The warning did not occur on my staging site. So I switched on/off different parameters.

Then when I changed the username xfield in the backend at “who can edit” from all members to administrator the warning occurs on my staging site as well.
The worst is, that making this change undo didn’t solve the problem. Nor a reinstall of the plugin or cache delete.
The only way at the moment to prevent this error message from occuring is to leave the plugin deactivated. So this setting must have saved values which are not beeing cleaned after plugin deletion.

Strange behaviour also, when using query monitor to see more details of the problem the warning message doesn’t appear.

• This reply was modified 1 month, 3 weeks ago by Alex.

1. Plugin is deactivated.
2. login as User/subscriber
3. Go to profile / settings / user data and change some of this users data like gender, age or whatever
4. Click save
Succesfully saved

5. Now activate the plugin and do the same.
When clicking save data, white screen with the warnings appear doesn’t matter which xprofile field you have changed.

• This reply was modified 1 month, 3 weeks ago by Alex.

Hello Ravi,
thanks for your answer. Unfortunately I cant provide you with these credentials because the site is not public yet and protected.

The tag where I want to change the background color has no different id’s or classes for active, random or newest member seach. So I wonder how you want to assign different colors just using CSS?

SourceCode:
<li id=”members-all” class=”selected” data-bp-scope=”all” data-bp-object=”members”>
Active Members <span class=”count”>4</span>

I can use li a { background-color: blue; } but again, then ALL labels are in blue.

Regards

I know, I know. But after weeks of testing, googling, asking developers and so on, this was the easiest way to make it work. Finally. In my opinion buddypress dev team should remove old tinymce 4.9. Or, at least letting admins use other rich text editors easily. As I wrote this is not only my wish.

Ups, I put the code into functions.php.

But isn’t your approach a security issue? It switch off kses for all fields, right? So isn’t modifying this core file the better choice in this case?

Hello Brajesh,
Thanks again for your answer. To change the editor might be to much effort indeed because of all the wordpress dependencies which have to be considered.
Therefore I tried your code and added this just for testing. I also tried to disable kses at all:
add_action( ‘bp_init’, function () {
remove_filter( ‘bp_get_the_profile_field_value’, ‘bp_xprofile_escape_field_data’, 8 );
} );
remove_filter(‘pre_user_description’, ‘wp_filter_kses’);

But at the profile page, li elements still stripped off. See image.
https://postimg.cc/qzMPggTm

For the biography field richtext is not enabled. How to enable it?
But does BP checking the bio field for richtext possibilities at all?
If not, enabling richtext will make no sense. Any more ideas to solve this on the profile page?

The backend shows the tags
https://postimg.cc/dDX2ZxMz

• This reply was modified 3 months, 2 weeks ago by Alex.