BuddyPress.org

Is item #2 a custom email that you created and if so, how did you create it, i.e., what steps did you take?

FYI – Typically “mail logging” plugins log mail sent via wp_mail() (WordPress) and by default BuddyPress doesn’t use WordPress to send emails thus they won’t show in those logs.

Sounds like that group’s database entry might be corrupted. Try repairing BuddyPress tables from wp-admin → Tools → BuddyPress, or delete/recreate the Texas Roadhouse group. Also clear object/page cache after changes—often fixes group-specific feed and upload issues.

This appears to be related to ticket #9302, primary navigation in site editor fails to allow creation of a group. The ticket was submitted by the OP for this topic and has more information regarding the steps to reproduce.

The URLs come from the WP Posts table in the database. In your db client, you can query/search the “post_type” field/column with a value of “buddypress” (without the quotes) and the results should be all the entries that are associated with URLs/Directories.

When reviewing the history for this BP Add-on, this appears to be a bug that was first reported in April of 2024 in the WordPress support forum for this plugin. However, it appears that the only action taken was the submission of a GitHub issue #112 that acknowledges the bug and this issue has remained open since that time.

Long story shorter, the fatal error is due to, what appears to be, missing parameters which is unforgiving with PHP version 8.0+. Rolling the PHP version back to 7.4.33 produces PHP errors as a warning and notice for the same file and line number. This bug appears to affect the posting of am image in an activity post; meaning the image is uploaded but does not get attached to the associated activity post. What does seem to work is uploading images from a user’s profile media area (where the image gallery is shown).

All I can suggest at this point is that you deactivate the plugin until a remedy can be found and a new version is released.

For the following items, there will either be URLs or Pages:

• Activate
• Activity
• Groups
• Members
• Register

The default when installing or upgrading to BuddyPress versions of 12 or greater is URLs. In order to change to Pages, the BP Classic add-on (plugin) should be installed and/or activated.

Most likely, the reason for the -2 for the Activity Directory slug in URLs is that there is a Page with the title of “Activity” and a slug with a name of “activity” which should be visible within the WP Pages area. The indicated items are WP posts that will either have a post type of “buddypress” (indicates URLs) or a post type of “page” (indicating Pages). Meaning they should all be of same post type, not a mixture of both nor duplicates,

Installing and/or activating the BP Classic add-on should revert all the previously indicated items to Pages and then you should be able to remove (trash) any duplicate Pages within the WP Pages area. You can the keep things as Pages or deactivate the BP Classic add-on to revert to the default of URLs.

If anyone comes to this post looking for help on using Divi with BuddyPress here’s the first thing that you need to do.

1. Log in to your WordPress site.
2. From the WordPress sidebar select “Divi > Theme Options”.
3. Go to the “General” tab (which should be selected by default) found below the Divi Theme Options text.
4. Click on the “Performance” sub-tab.
5. Disable “Dynamic CSS”.

This should fix the header and footer formatting issues that most people see when using Divi with BuddyPress.

Update, in legacy view as to why when expanding your ‘Child groups’ each group is listed again.

So not sure exactly, however, cause is related to the template stack not getting loaded when called via ajax. Not being an expert in buddypress nor wordpress, I’d guess that BP now requires something special for ajax style calls (or frankly maybe the code should be rewritten to remove ajax… in my mind that’d be preferable)

This is the code line not getting executed when called via ajax… cuz your not in the groups directory… or wherever the groups directroy might be on your verson of BB

"public/class-hgbp.php" 
    /* Changes to the groups directory view. **********************************/
    /** 
     * Add our templates to BuddyPress' template stack. 
     *
     * @since    1.0.0
     */ 
    public function add_template_stack( $templates ) {
        if ( bp_is_current_component( 'groups' ) ) {
            $templates[] = plugin_dir_path( __FILE__ ) . 'views/templates';
        }
        return $templates;
    }

Simply executing the template stack add, gets you much better results, but is the right answer, doubt it?

Great plugin.

But yup, needs some attention to update to latest… logically works though, just visuals seem to be programmatic.

wordpress: 6.8.2
buddypress: 14.3.4

legacy:
almost works 100%, groups directory view shows a caret for groups, unfortunately when you expand the caret (groups are not getting filtered for the child groups, ie the children are simply the list of all groups again)

nouveau:
ehh, no tree view, but the include top-level groups only kind of functions, but again don’t think there’s any code to support this under nouveau

I hope to do some debugging and work on this plugin, wish me luck.

I meant the link because there is no button.
To risca, it depends which template you use, default or novoue. If it is novoue pick up the template file for the emails, search for the unsubscribe link and delete or comment it out. Then save this file in a directory called buddypress with the same folder structure in your child theme directory.

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 );

From what I can tell, the snippet replaces the text portion of what BuddyPress would normally add to the meta “title” with the text “XXXX” (without the quotes). For example on a members profile view page (site.url/members/username/profile):

Display name of user: test
Website name: Apple

Without snippet: Profile | test | Apple

With snippet: XXXX | Apple

The snippet (copy & paste) was checked for use in the bp-custom.php file and the functions.php file of a child theme. Perhaps, you could elaborate a bit more as to the steps you took to implement the snippet and what you expected the result to be.