BuddyPress.org

Hello @juriss

From my experience it can be tricky sometimes to translate BuddyPress content (since it’s dynamic). For this reason, I use a combination of 2 plugins.

Loco Translate – This can be used to translate “fixed/most” content.
TranslatePress – This can be used for “dynamic content” like activity and so on.

You should be able to translate the “What’s new in” with the LocoTranslate plugin itself.

If not, you could try the TranslatePress – both free and no premium/pro/payment is required.

Hello @ph59

I personally only allow my members to create private groups, since I don’t want them to have public groups flooding the main activity wall and so on. Also it just makes sense with the setup I personally have.

If the only fix you need, is for members to only save/create group with settings as (just an example) private groups, this can be done with some custom code.

The code is available in my post here: BuddyPress – Limit creation of groups (private only) – WITH CODE

This can be done by targeting specific site roles.

Also the code could probably be modified to also exclude users from invitations and so on (hiding the option).

Maybe this helps! 🙂

Hello
The solution is as follows
Install the plugin BP Classic
Create related pages and configure the pages in BuddyPress settings
Deactivate the plugin BP Classic

Hello
The solution is as follows
Install the plugin BP Classic
Create related pages and configure the pages in BuddyPress settings
Deactivate the plugin BP Classic

Did anyone ever find a solution to this? It seems like a lot of people struggle with the buddypress avatar system and I haven’t been able to find one myself. Any insight into this would be greatly appreciated.

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,

BuddyDev has a commercial plugin, BuddyPress Profile Data Moderator, that may serve your purpose. If you are looking for something free then you should search the WordPress Plugins Directory, if you’ve not done so.

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.

Hi,

BuddyPress 14.3.3 Maintenance Release fixes the issue with “deprecated class” error messages.

Please upgrade at your convenience.

Hello

You might already have solved this, since the post is 2 months old – however – I just wanted to mention that this can be done with a simple setting.

Go to Settings > Forums > Forum Integration for BuddyPress

Change the setting in the box “Allow BuddyPress Groups to have their own forums”.

Hope it helps. 🙂