BuddyPress.org

You could take a look at this free plugin we’re developing: FansPaysite MicroPayments https://wordpress.org/plugins/paid-membership/ .

Flexible Monetization: Offer creator subscriptions, pay-per-view content, and memberships tailored to various creator needs.

Direct Content Sales: Creators can directly sell access to posts, videos, downloads, live video streams, enhancing revenue opportunities.

Versatile Payment Integration: Supports all major gateways with WooCommerce, including PayPal, Stripe, CCBill for broad accessibility.

Reduced Transaction Fees: Streamline finances with microtransactions that cut down on costs.

Dynamic Wallet System: Enables secure, in-site transactions with internal credits and support for other popular wallets like TeraWallet and MyCred.

Enhanced User Engagement: Features like crowdfunding and donations add interactive elements to content monetization.

Comprehensive Admin Control: Manage access, monitor transactions, and customize content offerings with ease.

BuddyPress Integration: Enhances community features, allowing for real-time updates and user interactions within the platform.

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.

Hi @mike80222

This is an issue with bbPress and there is an open ticket Deprecated Warning ##3589 in bbPress Trac.

You will have to ask the folks over in bbPress as to the status of this ticket.

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 @stephunique,

Long story short, the “screenshot” file is added to the wp cache, e.g., $this->cache_add( 'screenshot', 'screenshot.' . $ext );.

Additionally, it appears that the extensions for the “screenshot” file can be any of the following 'png', 'gif', 'jpg', 'jpeg', 'webp', 'avif'.

Last but not least, in the future, it would, most likely, be best to ask WordPress related questions in one the WordPress related forums.

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,

Thanks for reporting this issue, I can confirm the error messages for the BP REST API when using the BP Nouveau template pack. Unfortunately, something went wrong with the build and these errors didn’t get caught when testing the build. 14.3.1 was released to fix an issue with WordPress 6.7 (_load_textdomain_just_in_time issue) and another issue (heartbeat) with the BP Legacy template pack.

Looks like we need another build to get this fixed. At the moment, the only recourse is to roll back to 14.2.1 and continue to use WordPress 6.6.2.

My apologies for the inconvenience.