Thanks Brajesh,
I would not have such a problem if WordPress would use the latest tinymce one but instead integrates tinymce 4.9 which is very old.

I am using the biography field already. This is currently the only solution to me using the cdn-tinymce version 7 – with the problem that it changes bullet lists to words line by line separated by an <br> on the profile view page. The edit page looks fine.

Furthermore I only can use it on the biography field with this code:

function antipole_remove_rich_text() {
return false;
}
add_filter(‘bp_xprofile_is_richtext_enabled_for_field’, ‘antipole_remove_rich_text’);

Another solution might be use it on the rich multiline textarea as you wrote.
BUT with using the above code I am only able to integrate tinymce 7 cloud on the biography field and not on the multiline xfield.
Without the code I cannot load it either on the bio nor on the multiline text field.

Do you have a solution to make it running on the multiline-textarea field? I would need to get rid of the integrated one and then load the cloud one.

Otherwise I only can prevent buddypress from changing the bullet lists on biography profile view page where I also have no idea how to.

Long story short:
1. If using the biography field. How can I prevent buddypress from stripping off html on these field? On user profile edit and view page.
2. If using the rich multiline textarea field. How to use the tinymce 7 cloud version which currently conflicts with the old 4.9 implemented one.

Tinymce 4.9 which WordPress and Buddypress uses has security issues. Maybe someone should tell the buddypress dev team for a solution on that??
See this: https://core.trac.wordpress.org/ticket/47218

Sorry for asking again:
And there is no way to load just the tiny 7 cloud one with wp_editor()?

https://www.tiny.cloud/docs/tinymce/latest/editor-and-features/

If I could use the cloud version without switching off rich text options with the code below, no HTML would be stripped off on the frontend profile page.

function antipole_remove_rich_text() {
return false;
}
add_filter(‘bp_xprofile_is_richtext_enabled_for_field’, ‘antipole_remove_rich_text’);

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

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 4 months, 3 weeks ago by Alex.