BuddyPress.org

The login page shown in the 1st screenshot is due to having the Community Visibility option set to “Members Only” (Private Community) within BuddyPress options. This option was introduced in version 12.0.0 and there appears to be some situations in which the default WordPress login page appears as opposed to the intended “Private Community” login page. Nevertheless, the “Private Community” login page can be disabled by utilizing the bp_view_no_access_redirect_to_login_screen filter hook and you will want your callback function to return a value of true. The following link is the line of code where the filter hook resides for v14.3.4:

bp_view_no_access_redirect_to_login_screen

The registration page shown in the 2nd screenshot is actually the BuddyPress registration page. Why it looks different is because the Buddyx theme is utilizing CSS rules to alter/change the appearance. You should contact Wbcom Designs support regarding the restoration of the default appearance.

The snippet does what it is coded to do, therefore, either the snippet is not being invoked or there is something else (possibly a plugin, theme or other custom code) that is counteracting the snippet.

I’m not familiar with the “username only” plugin, is this plugin available via the WordPress plugins directory? I’m asking because this plugin or some other external factor (a different plugin or theme) might be disrupting the normal flow of events.

The snippet relies on the bp_get_title_parts filter hook which relies on the bp_modify_page_title() function to be invoked by the wp_title filter hook.

You can try hooking the snippet to the wp_title filter hook to see if that makes any difference, i.e., change:

From:

add_filter( 'bp_get_title_parts', 'yz_change_buddypress_browser_tab_title', 999 );

To:

add_filter( 'wp_title', 'yz_change_buddypress_browser_tab_title', 999 );

BuddyPress utilizes the WordPress login page by default. There are plugins that will alter or replace the standard WordPress login page.

I stated that the visibility for WordPress Fields are “currently” not user selectable. Why this decision was made was unknown to me, until recently, and appears to be along the same lines of why the “Requirements” metabox doesn’t appear for the WordPress Fields, as well.

Given this conversation, I looked for a possible reason that might uncover a decision to not include such capabilities and found that ticket #8487 (Add visibility and required controls to the WordPress profile fields) provides the history behind why the decision was made not to include the capabilities (visibility and requirements) and why these capabilities have yet to be incorporated (no one has provided a patch).

Currently, the visibility for the following xprofile fields aren’t “user” selectable:

• 1st Text Field – labeled as “Name” by default
• Single Fields – Checkbox Acceptance
• WordPress Fields – Biography
• WordPress Fields – Text Field (First Name, Last Name, Website)

In your example, “surname” as you have applied would be “WordPress Field – Text Field – Last Name” and as indicated the visibility is not “user” selectable.

As to the other xprofile fields the visibility can be set for either:

• Allow members to override – visibility is selectable by users
• Enforce field visibility – visibility is set per selection

Admin can set the visibility during creation or editing of xprofile fields that allow for “Visibility” settings, e.g., Single Fields – Text Box will have a “Visibility” metabox whereby an Admin can set the “Visibility” parameters. See BuddyPress xProfile fields administration for other information.

I’m not clear on which/what email that is not being sent. AFAIK, there are 2 emails sent for a successful email address change, for example from the WordPress (WP) backend:

1. Email Change Request <- contained in subject line as sent by WP
2. Email Changed <- contained in subject line as sent by WP – after a successful change of email address

For the BuddyPress (BP) frontend:

1. Verify your new email address <- contained in subject line as sent by BP
2. Email Changed <- contained in subject line as sent by WP – after a successful change of email address

For the BP process, please indicate which of the 2 emails is not being sent.

With BuddyPress 12.x.x or greater, URLs, a.k.a., BuddyPress Directories, is the default configuration (see BuddyPress URLs settings) as opposed to pages. See Navigation menus for additional set-up information.

In the event that you require BP pages, you will have to install and/or activate the BP Classic plugin.

As to shortcodes, there are no built-in (internally defined) shortcodes for BuddyPress.

What WordPress theme are you using? Also, when you are in the wp-admin area, go to Settings > Permalinks and make sure the “Permalink structure” is not set to “Plain”.

What might help is that you include a screenshot of the menus and what a page looks like with no content. For example, the following is a screenshot of a page (with content) when the “Activity” menu item is selected:

Additionally, what WordPress theme are you using?

If you had installed BuddyPress prior to version 12.x.x, e.g. versions 11.x.x and below, then you would have had pages. If you install versions 12.x.x and above, the default will be directories as opposed to pages. If you wish to have pages again, then you need to install and/or activate the BP Classic plugin.

Hi @locker17,

I don’t know the answer to your question (sorry!) But I’m also trying to reorder the members list in various ways, and I’d be interested in knowing what that plugin is that you’re using. Maybe the code in the plugin would yield some interesting ideas.

Unfortunately, if I’m not mistaken, imath left buddypress (and wordpress) sometime back.

Mike

Hi @timostr79,

I’m not sure if this is exactly what you’re asking, but I use the User Switching plugin:

User Switching

Which allows you (as an admin) to switch to being another user, so that you can see the site as they see it. It does have side effects. For example, if you’re tracking when a user was last active, the user will appear to have been logged in when you switched to them. I have a “test user” (with normal user privileges) that I switch to for testing the site.

Hope that helps,

Mike

Hi @rayray23,

Since nobody seems to be replying to this … I’m definitely no expert, but I think it’s possible you might want something like:

if (is_user_logged_in()) {
        $user = wp_get_current_user();
        $username = $user->user_login;

I personally find it hard to search the WP documentation, but there should be information in:

https://developer.wordpress.org/reference/functions

Hope that’s helpful,

Mike

When using the Classic Widget plugin, deleting a widget from a sidebar or footer area will remove the widget from that area. Widgets that can be added are listed under the “Available Widgets” section (left-hand side).

For BuddyPress widgets to appear in the “Available Widgets” section, when using the Classic Widget plugin, you will have to install and/or activate the BP Classic plugin.

The URL provided in the email notification is just to a page that requires access by an appropriate logged-in user. The issue appears to be related to the process that is constructing the redirect URL. The example you provided appears to be mangled for an unknown reason:

https://infosecportal.ru/wp-login.php/?redirect_to=https%3A%2F%2Finfosecportal.ru%2Fpolzovateli%2Fpauls%2Fbp-messages%2F#/conversation/11

The slash that is after wp-login.php seems to be misplaced, additionally, there should be a slash after 11 and then I would expect &bp-auth=1&action=bpnoaccess after that.

The redirect is constructed in the function bp_core_no_access() which can be viewed at the following URL for BP 14.3.4:

https://github.com/buddypress/buddypress/blob/14.3.4/src/bp-core/bp-core-catchuri.php#L328-L405

Typically, $mode is equal to 2 which will then execute the code represented by lines 371 through 381: i.e.:

		case 2:
			if ( ! empty( $redirect ) ) {
				bp_core_redirect(
					add_query_arg(
						array(
							'bp-auth' => 1,
							'action'  => 'bpnoaccess',
						),
						wp_login_url( $redirect )
					)
				);

$redirect should be the URL that is represented in the email notification. The function wp_login_url(), which is a WordPress function, constructs/builds the redirect URL. The function wp_login_url() without arguments should, in your case, return:

https://infosecportal.ru/wp-login.php

The fact that there is a slash after the .php indicates that you should look there for why the slash is present, see the following regarding information on wp_login_url():

wp_login_url()

Hi,

Unofficially, AFAIK, BuddyPress v14.3.4 is compatible with the 6.8 branch of WordPress.

Officially, we (the BP team) are behind with the scheduling of the next release. As to when this will occur is, currently, up in the air. Lastly, thanks for the reminder, I’ll have a chat with one of the BP committers to see if we can get things moving forward.