Hi Mike,
Hope you are doing well. I am sorry I could not reply in time as got overwhelmed by the work.

Are you using multiple member type fields? If yes, It will be a problem in future.

Member Types are like single taxonomy.
For example, if we are organizing books, we can use member types as Genre or as Publishing House. The member type terms allows us to group item by a single classification.

For example, “keyboard” in your case is a good candidate for member types. But all the type of keyboards can not be sub organized using it.

I am not sure how much sense that makes but it seems to me you are most probably looking for multiple way to classify and not multiple terms to classify into.

A user can have more than 1 member type but we do not have a way to sub divide member types to smaller lists and properly sync the field(multiple field) to user’s actual member type.

We need to think some other strategy for it.

If you can tell me what other purposes you are trying to accomplish(other than auto adding to groups), I may have some idea.

Thank you
Brajesh

Hi,
Just updating.

I will be assisting you tomorrow on this.

Thank you
Brajesh

Hi Vivek,
Please visit the posts screen on user profile and note down the part after username.

For example, if it is http://example.com/members/vivek/abc/xyz
our slug is ‘abc/xyz’

After that, Please change this line

 $redirect_url = bp_core_get_user_domain( get_queried_object_id() );

with that slug as

 $redirect_url = bp_core_get_user_domain( get_queried_object_id() ) .'abc/xyz';

Hope that helps.

Regards
Brajesh

Hi Carsten,
You may want to take a look at this
https://css-tricks.com/almanac/properties/h/hyphenate/

Regards
Brajesh

Hi Vivek,
Thank you for reporting.

It seems you have following code in your child theme

@media (max-width: 767px)
.bpmts-moderation-button-wrap.generic-button {
    position: absolute;
    top: -50px;
    right: 0;
}

....some other code

}

This is causing the issue. It is most probably added by someone to fix the positioning on button on some other place and has the side effect here.

If you can tell me why this code was added originally, I may be able to provide a better context specific solution.

Regards
Brajesh