BuddyPress.org

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.

@flamuren,

Support is provided by volunteers and is subject to when someone has time and/or expertise for any given topic request. Additionally, this is not a Job Board, if you require this type of help then you may want to use the following link to make a request of such type:

WordPress Jobs

Hi,

Your best option is to flag it in the #buddypress channel on Slack or to flag it in this forum (Request & Feedback), given that posting in any of the forums doesn’t automatically flag a post as spam or as requiring moderation.

That said, your post was automatically flagged for moderation due having 3 links (3 or more links will automatically place your post into moderation). As to how long it will take will depend on whether a moderator notices the post or is made aware of such, as you have done.

Last but not least, I edited your initial post such that the links don’t register as links, basically encapsulated the links within the code tag/element. Additionally, I released your Topic from moderation.

Let’s me know if my “final final” guess worked. I had a look at how add_filter works in wordpress and I can’t imagine any other method being correct.

Hi,

In order to select WP pages (as it was prior to BP 12), you will have to install the BP Classic add-on/plugin.

Those are the 21 situations that are installed by BuddyPress. If a situation for password reset had existed it would have had to be installed by, at the momenent, an unknown plugin which then would have made the count 22.

So, at this point, it is still unclear whether an email template and associated situation existed prior to March 25. OK, so let’s try something that might provide some insight as to what may be occurring:

1. In an Activity post, @mention yourself, so that you would receive and email. We need to look at the email header information to see whether that email was sent by BuddyPress or by WP Mail SMTP.
2. Send yourself a test message from WP Mail SMTP (once for HTML and once for plain text), again to check the email header information.

Personally, I only use the built-in emailing capabilities for WordPress related messages and BuddyPress for its related messages. However, I did install WP Mail SMTP (default PHP configuration) just to check how it functions with sending emails.

I will also attempt to install All-In-One Security (AIOS) to see if it is installing the password email template and situation.

In the meantime, I’m interested in knowing the results of the email header information specifically 2 key value pairs:

• Content-Type
• X-Mailer

The above list are the keys and an example for the @mention test would be:

Content-Type: multipart/alternative; boundary="b1=_pryh1yml4xJIzLfYeFcRRVRuhNzbjtZon2KyTKgas"
X-Mailer: PHPMailer 6.9.3 (https://github.com/PHPMailer/PHPMailer)

For WP Mail SMTP the results for the HTML test would be:

Content-Type: text/html; charset=UTF-8
X-Mailer: WPMailSMTP/Mailer/mail 4.4.0

For WP Mail SMTP the results for the plain text would be:

Content-Type: text/plain; charset=UTF-8
X-Mailer: WPMailSMTP/Mailer/mail 4.4.0

What I’m attempting to do here is to fill in the blanks, in my mind/have an historical record, and via the process of elimination attempt to figure out what is preventing password reset emails from being delivered.

The issue at this point, as I see it, is that there is additional information that is missing or yet to be uncovered/disclosed. Do you know as a matter of fact that this email template existed prior to March 25? If the email template, it’s corresponding situation (what you call a trigger) and any underlying code to make all of this function, for a password reset to be sent via BuddyPress, would have had to have been created by a plugin (that is not BuddyPress) and if true then that plugin needs to be identified in order to figure out why it has not reinstalled the email template with an associated situation (trigger). Otherwise, if the email template never existed then your problem lies elsewhere.

Normally, password resets are a function of WordPress and are sent via the wp_mail() function that is executed via the retrieve_password() function. However, I noticed that you are using the WP Mail SMTP plugin of which password resets would be sent via this plugin instead of the wp_mail() function (WordPress).

There is an old plug-in to set a default cover image. I have it running without any problem on the current WP & BP
https://wordpress.org/plugins/buddypress-cover-photo/

Easiest is to use the Code Snippets plugin. Download it from the wordpress plugins site. I can’t link to it because this fu***** sh** website holds my comment for moderation when I link to the Official wordpress website. Go figure.

For an e-commerce website, I recommend using Elementor over Gutenberg because it offers a more flexible and user-friendly design experience. Elementor provides a drag-and-drop interface, allowing you to customize your pages easily without any coding. It also has a wide range of pre-designed templates and advanced features like custom headers, footers, and integrations with popular e-commerce plugins like WooCommerce. While Gutenberg is a solid choice for simpler sites and is built into WordPress, Elementor will give you much more control over the design and functionality, which is crucial for creating a professional-looking and high-performing e-commerce site.

Both have their strengths! If you want full design flexibility and a user-friendly drag-and-drop interface, Elementor is great. If you prefer speed, simplicity, and better performance, Gutenberg is a solid choice—plus it’s built into WordPress. It really depends on your design needs and how lightweight you want your site to be.

Both have their strengths! Elementor offers more design flexibility with a drag-and-drop interface, making it great for complex layouts. Gutenberg, on the other hand, is lightweight and integrates natively with WordPress, which helps with performance. Are you prioritizing ease of use or site speed?

You could check if this plugin still works. It segregates BuddyPress social networks in a multi network WordPress install so that each WP network has a different social network. One for each Network.

You could also check if this plugin still works. It allows each site on an individual network have its own separate buddypress social network.

It would appear that you may even, at present*, be able to run separate (though members shared) buddypress social networks on every site in a WP Multi Network setup.

AFAIK they both still work in with WP 6.7.2, BP 14.3.3 PHP 8.3.11 MYSQL8.0.35 but you should check yourself if they still do. (i am not a developer or coder)

*The Buddypress Development Team has stated that consideration has been given by the Team to perhaps in the long term to deprecate the multiblog feature sometime in the future. This (AFAIK) would not effect the first scenario but would effect the second