Thank you.

You are welcome.

Regards
Brajesh

Hi Carsten,
1.0.6 is available now.

1. It fixes the position. Thank you for contributing.
2. The buttons can be generated with any markup now.

I am sharing two snippets(Please only use only of them)

Example 1:- Change the button markup to use “li” instead of div everywhere.

/**
 * Modify the button args for BuddyPress Moderation Tools.
 *
 * @param array $args args.
 *
 * @return array
 */
function buddydev_modify_bpmts_button_args( $args ) {
	$args['wrapper_tag'] = 'li'; /* make the button like <li ...><a href=...>Report</a></li>*/

	return $args;
}

add_filter( 'bpmts_report_button_args', 'buddydev_modify_bpmts_button_args' );

Example 2:- Change only the markup for the User profile header Report button to use li. In this case, we check for context.

/**
 * Modify the User profile button args for BuddyPress Moderation Tools.
 *
 * @param array $args args.
 *
 * @return array
 */
function buddydev_modify_bpmts_button_args_for_user_profile( $args ) {

	// On User profile header button, use li tags.
	if ( 'bp_user_header' === $args['context'] ) {
		$args['wrapper_tag'] = 'li'; /* make the button like <li ...><a href=...>Report</a></li>*/
	}

	return $args;
}

add_filter( 'bpmts_report_button_args', 'buddydev_modify_bpmts_button_args_for_user_profile' );

Please let me know if that works for you or not?

Regards
Brajesh

PS:- The support for post type will be available next week’s release.

Hi Chris,
Yes, you can certainly protect it. It is doable.

I don’t think the code is the problem, others will have similar approach. I did not say that specific code is bottleneck. I said, this approach of serving media using php may become a bottleneck. But if there is a regulation that needs it, You may use their code.

Regards
Brajesh

Hi Andi,

Thank you for the kind words.

1. I am still not sure as I have never found this issue. Try using 2 or 3 and see what happens.

2. That’s good.

3. I am sorry but the function ‘bp_core_new_nav_default’ is broken in BuddyPress 3.x . It is not working with 3.2 too and I have seen a ticket where it seems it will be available in 3.3. We will have to wait for it to use it again.

Regards
Brajesh