Should we consider this situations?

Error:

Fatal error: Uncaught Error: Call to undefined function BP\Rewrites\bp_core_get_directory_pages()
in /var/www/html/wp-content/plugins/bp-rewrites/inc/update.php on line 22

Using a custom BP component...
Using a BP_Group_Extension, in __construct() I need to get the group id so I can retrieve a groupmeta value and determine if a tab should be added.
This works when the Rewrites plugin is not active:

class Group_Events extends BP_Group_Extension {
    function __construct() {

	$setting = groups_get_groupmeta( $this->get_group_id(), 'events-assignable'  );

	if ( $setting == '1' ) {
		$show_tab = 'anyone';
	} else {
		$show_tab = 'noone';
	}  // etc 

With the Rewrites plugin active, $this->get_group_id() is always zero and so the tab is never added.
Also tried using bp_get_group_id() and $this->group_id

So far, only Directory and Members single item primary nav slugs can be customized.

If you go to the Settings > BuddyPress > URLs administration screen, you'll see:

Before removing/adding Notices hooks, it's important to check the Messages component is active.

I have a custom navigation item for members component. It occours a fatal error when BP-Rewrites is active. The reason of this error nav property creating just for admin requests. Is there any reason to do it?

Here is my mu-plugin to see the fatal error:

<?php
namespace NefisYemekTarifleri\Custom_Nav;

add_action( 'bp_init', __NAMESPACE__ . '\\init', 999999 );
function init() {
	if ( function_exists( 'bp_core_new_nav_item' ) ) {
		bp_core_new_nav_item(
			array(
				'name'            => 'Custom Nav',
				'slug'            => 'custom-nav',
				'parent_slug'     => buddypress()->members->slug,
				'position'        => 10,
				'screen_function' => __NAMESPACE__ . '\\custom_nav_screen',
			)
		);
	}
}

function custom_nav_screen() {
	do_action( 'bp_members_screen_display_profile' );
	bp_core_load_template( apply_filters( 'bp_members_screen_display_profile', 'members/single/home' ) );
}

Error:

Fatal error: Uncaught Error: Call to a member function add_nav() on null
in /var/www/html/wp-content/plugins/buddypress/src/bp-core/bp-core-buddybar.php on line 172

See: https://wordpress.org/support/topic/wp-signup-php-errors/

There are a lot of customizable slugs into this screen. Using the Site-Health screen accordion UI might improve the user experience.

Moreover, it should be possible to edit the Title of the components directories.

I missed this specific part so far! Using the bp_get_search_slug() as the current component inside the URL can be used to search inside members, blogs, groups or posts.

See: https://wordpress.org/support/topic/breaks-similarly-named-permalinks/

Describe the bug
My buddypress-docs plugin uses a BP_Group_Extension to add an item to group navigation. The nav item is properly loaded, and the BP_Group_Extension display() method properly called, with bp-rewrites activated.

However, the logic inside of my display() method depends on some other setup that buddypress-docs does at runtime, including determining the current "view" based in part on bp_current_component(). The particular line in question is https://github.com/boonebgorges/buddypress-docs/blob/130328dc3000d22c35e642950b10b8a17454cfd7/includes/integration-groups.php#L113: without bp-rewrites, bp_is_current_component( 'groups' ) (and bp_get_current_group(), bp_is_group(), etc) works properly, but with bp-rewrites, it incorrectly returns false.

It appears that this is because current_component etc are made available much later in the load process with bp-rewrites:

• Without bp-rewrites: bp_core_set_uri_globals() happens at bp_init:2, which is hooked to WP's 'init'
• With bp-rewrites: Component parse_query() methods are hooked to WP's 'parse_query'

The specific way that buddypress-docs operates here is based on very old legacy code. If I switched it so that my BP_Group_Extension directly checked the global at display time, instead of depending on a global that's set very early in the page load, it would work properly. However, this compatibility break might point to a broader problem with plugins that expect current_component etc to be available before parse_query.

I'm unsure if this will simply have to be a documented break, or if there's a way to shim the globals so that they're available earlier for backward compatibility reasons.

To Reproduce
Steps to reproduce the behavior:

1. Install and activate buddypress-docs
2. Visit a group
3. Click on 'Docs' nav item
4. You'll see that the plugin templates aren't loaded into the content area

Expected behavior
buddypress-docs content appears in group content area

Hi, i just tested Version 1.0.0-beta2 on my wp multisite install with BP network aktivated and it does not work, the plugin seems to expect BP to be activted on the main site instead of network activated, posts error "BP Rewrites requires the BuddyPress plugin to be active. Please deactivate BP Rewrites, activate BuddyPress and only then, reactivate BP Rewrites."

tested also to have BP network activated and the rewrite plugin activated on the main site, without success.

br, Eric

This file will (in particular) explain how to quickly set up the BuddyPress local env to include BP Rewrites.

Contributors simply need to add a .wp-env.override.json into the buddypress folder containing:

{
	"core": "WordPress/WordPress#master",
	"plugins": [ ".", "~/path-to-the-plugin/bp-rewrites" ],
	"config": {
		"WP_DEBUG": true,
		"SCRIPT_DEBUG": true
	}
}

BP Rewrites is currently creating a custom post type called buddypress. I think we shouldn't use our main plugins name as a custom post type. I suggest to use bp-rewrites instead of buddypress. Any thoughts?

Describe the bug

1. I could not activate the bp rewrites plugin I keep getting the error that (the following link has expired)
2. After trying to activate without any success I also noticed that all my current buddypress pages were totally deleted.

WP/BP Configuration (please complete the following information):

• WordPress: [version 5.9]
• BuddyPress [version 10.0]

Is your feature request related to a problem? Please describe.
As the plugin is supporting all Group views, there's no reason to work on this extra effort to have all BuddyPress slugs customizable.

On every page: Notice > Undefined variable: structs in
wp-content/plugins/bp-rewrites-trunk/src/bp-blogs/classes/class-blogs-component.php:262

Perhaps this: return parent::add_permastructs( $structs );
Should be return parent::add_permastructs( $permastructs );

Describe the bug
Activating bp-rewrites breaks page_on_front

To Reproduce
Steps to reproduce the behavior:

1. Without bp-rewrites, set a BP directory page (such as Groups or Members) to page_on_front (Dashboard > Settings > Reading)
2. Visit home page. You should see the selected directory.
3. Activate bp-rewrites.
4. Visit home page. You now get the 404 message. Furthermore, when you visit wp-admin/options-reading.php, the directory page is no longer selected in the dropdown.

I haven't debugged this at all - I wanted to report the bug before I forgot :-D