BuddyPress.org

I setup a fork of the original github repo, I can’t guarantee it 100% works, especially like with following blogs and stuff like that as I haven’t tested that throughly. I also haven’t tested it with legacy themes. However, for regular following and for the following activity filters in bp_noveau etc… it should work.

https://github.com/Alexanderwbell/buddypress-followers

Hi,
I am also testing this plugin, and I am using it with buddyboss platform and buddyx pro theme. I am encountering the same issues, especially this one with hitting enter to send a message, I hope so omeone can help with this, but it seems this thread is not active 🙁 I might end up getting help from ChatGPT 🙂

I see that this is a multisite installation, not that this should matter, it’s just that more information gets revealed over time. I noticed that define(‘WP_ALLOW_MULTISITE’, true); is listed twice; is this verbatim or just something that happened with copy & paste, just curious?

As to base64_decode, this may not apply, this would have been a malicious attempt to obfuscate, I was just trying to rationalize why you aren’t finding where the BP_GROUPS_DEFAULT_EXTENSION constant is being defined.

Perhaps I should ask the question differently; what tool are you using to search for the BP_GROUPS_DEFAULT_EXTENSION constant? Typically constants are defined in wp-config.php, it appears, however, the BP_GROUPS_DEFAULT_EXTENSIONcan be defined in a child theme'sfunctions.php` or a “Must Use” plugin, etc, etc.

Hi @davesumpter,

It would depend on the theme in use on how you would edit the Site Title link, assuming the Site Logo has the same link as the Site Title, you would use a URL similar to:

https://example.com/members/me

The “me” is the default shortlink redirector member slug. IOW, this will redirect to the profile area of the logged in user, typically, their activity stream/feed

Hi @asmaajaved,

I’m not sure if this an edge case, so more information is required, e.g.:

1. WordPress version
2. WordPress permalink setting(plain or pretty URLs)
3. WordPress theme in use
4. BuddyPress version
5. BuddyPress template pack in use
6. What does your error log reveal?

It would also help to have a screenshot of:

the single groups pages show up empty

Unfortunately, you’ve applied a band-aid at the Theme level. The next Theme update will remove your band-aid and you will have to apply it again, given the approach you’ve taken.

The bp_loggedin_user_domain( ) function should have returned a URL with a trailing slash, for example:

http://www.url.com/members/username/

Which is why the Theme has it written as:

bp_loggedin_user_domain() . $bp->notifications->slug

Something is causing the trailing slash to be missing, solving for this will be the fix. Maybe a plugin or some custom code is filtering the return value, such that is stripping the trailing slash.

Assuming you are using BuddyPress 14.3.3, see the following URL for the source code:

bp_loggedin_user_domain()

Try this in the functions.php file of your child theme. I have put 777 as filed id but you will have to put in the correct field id and the correct field name:-

function validate_required_profile_fields() {
$required_fields = [
‘field_777’ => ‘The so and so field is required.’,
];

foreach ( $required_fields as $field_key => $error_message ) {
if ( empty( $_POST[ $field_key ] ) ) {
bp_core_add_message( $error_message, ‘error’ );
}
}
}
add_action( ‘bp_signup_validate’, ‘validate_required_profile_fields’ );

This is quite strage. I am having a similiar problem. When Elementor is activated it breaks all my buddypress links. But I found out that when switching to Hello theme the links work again.
But since my design was made for Astra this is not a solution for me.

So my links work if

• either Elementor is disabled or
• Hello theme when Elementor is activated.

Any solutions for this? The hope to get help here dies last.

To apply a different template for BuddyPress pages in the latest WordPress block theme, you can create a custom template (e.g., bp-custom-template.html) in your theme’s templates directory. Then, use a filter in your functions.php file to assign this template to BuddyPress pages using code like:

php
Copy code
add_filter(‘template_include’, function($template) {
if (bp_is_buddyPress()) {
$custom_template = locate_template(‘bp-custom-template.php’);
return $custom_template ?: $template;
}
return $template;
});
This allows you to customize the layout for BuddyPress pages without relying on the default “pages” template.

I’m having the same problem.

I’ve been testing many themes, however none fit quite good. I’m really thinking about to develop a theme from scratch!

Hi, I have a very similar issue in that the ‘Group Invites’ item in the ‘Account Settings’ returns a 404 Page. Tried with three themes with same problem. I wonder if @dreampixel wouldn’t mind testing this on our behalf. Using Buddypress 14.3.3 and Mediapress. Thanks.

Hi,

The CSS file that gets loaded depends on which template pack is in use, e.g. Legacy vs Nouveau. Additionally, styles (CSS) can be customized via a Child theme and, if a Classic theme is in use, via the Appearance > Customize > Additional CSS menu path within the wp-admin area. Thus, which CSS file gets loaded is irrelevant/moot.

Specific to Avatars, How to Customize BuddyPress Avatars With CSS has some info (Note: might be a tad outdated). There are other sources on wordpress.org that contain general info regarding custom CSS, e.g. from the Advanced Administration Handbook – Custom CSS in WordPress

Hopefully, this is enough information to get you started.

Hi @glenphillips33,

Anything is possible, what’s unknown is the probability. IIRC, I had a similar experience, but it involved the wordpress.org site and drop-down menu items that affected Chromium on a AlmaLinux distro. Google Chrome worked fine as well as Firefox. On a Ubuntu and Debian distros (Linux), Chromium work just fine, as was with Windows 10. Long story shorter, eventually, the AlmaLinux distro received an update with a new Chromium build that fixed the issue with Drop-down menus.

That said, it doesn’t seem likely for a Windows platform since Google Chrome should be automatically updated and is usually ahead (stable release) of Edge, Opera and other browsers that share the Chromium engine or, maybe you are using cutting edge/beta releases/builds but, as previously mentioned, anything is possible.

If you want to supply the Web URL, I suggest you add that to your BuddyPress Profile, there is a field specific for this purpose (Web URL). That way, you can remove it later, if you don’t want the URL to remain public. I can then either confirm or deny whether I see something unusual while visiting a profile area with Google Chrome.

Next up are a couple of housekeeping items, that you require your attention, of which should not be related to the issue you reported in this thread.

(1) BuddyPress 12.4.1 is not compatible with WordPress 6.7.x. The effect is that your server error log(s) are filling up with an error notice, e.g.:

Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>.
Translation loading for the <code>buddypress</code> domain was triggered too early. This is
usually an indicator for some code in the plugin or theme running too early. Translations
should be loaded at the <code>init</code> action or later. Please see <a
href="https://developer.wordpress.org/advanced-administration/debug/debug
-wordpress/">Debugging in WordPress</a> for more information. (This message was added in
version 6.7.0.) in /var/www/html/wp_test/wp-includes/functions.php on line 6114

The solution is to either to roll back WordPress to version 6.6.2 or upgrade BuddyPress to version 14.3.3.

(2) BuddyPress 12.4.1 is missing 2 security patches, if you are going to continue to use the BuddyPress 12.x branch, it is recommended that you upgrade to BuddyPress 12.5.2, see If you are using BP 12.x and can’t upgrade to 14.2.1, and apply (1), accordingly.

Hi @glenphillips33,

My apologies for a belated response but, my default browser is Chromium (just a preference thing) on a Linux platform and all looks as expected. Although, Chromium, Google Chrome, Microsoft Edge, and others share the same basic engine, there may be differences in builds across the various OS platforms. Without knowing more information, it is difficult to assess the issue. For example, we currently don’t know, at a minimum, which may or may not prove to make a difference:

• WordPress version
• BuddyPress version
• PHP version
• BuddyPress template pack in use
• If you have tried using a WordPress default classic theme (non block theme or non FSE)

The layout appears broken, with profile sections overlapping or not displaying at all.

This is a generalization, meaning there isn’t enough specificity to truly understand the situation. Perhaps, a screenshot would suffice without having to visit your site.

Here is my setup as it relates to the following screenshot of an arbitrary Profile page with Google Chrome:

• WordPress: 6.7.1
• Active Theme: twentyeleven child theme (twentyeleven-child)
• PHP: 8.2.25
• OS: AlmaLinux 9.5 (Teal Serval)
• Browser: Google Chrome – 131.0.6778.85 (Official Build) (64-bit)
• Page caching: No
• Object caching: No
• BuddyPress: 14.3.3
• BuddyPress URL Parser: BP Rewrites API
• BuddyPress Active template pack: BP Nouveau

For me, the profile area renders as expected with Goggle Chrome based on the given setup. I also looked at the same page with Windows 10 and Google Chrome (131.0.6778.86 (Official Build) (64-bit), logged-in and logged-out and it looks the same. I don’t have a Mac, so I can’t provide a verification. Also, I’m serving up the profile page from a development site on my LAN.