BuddyPress.org

This feature does not currently exist in BuddyPress.

The core team has talked about what a robust member-to-member role and capability system would look like for a few years now (to allow for this sort of functionality) however we haven’t prioritized it yet.

Hi Hugo, my bad, should have given the link: https://codex.buddypress.org/getting-started/improving-performance/ at the bottom of page

but I see you, or maybe another mod? has already removed the link to this thread

does anyone know if Fredrick Townes has said anything about adding functionality to W3 total cache for buddypress? all I found was this 4 year old comment

Maximize WordPress and BuddyPress Performance With W3 Total Cache

I’m asking for same. Since buddypress revolves round members, it will be tricky to remove it. I only want to remove the notification figure for logged in users and reserve it for admins…

>deem some activity as more important

I never understood that either.
It seems arbitrary and esoteric.

Try this:
Create a template over-ride of
bp-templates\bp-legacy\buddypress\members\members-loop.php

And replace
bp_member_avatar()
with
bp_member_avatar('type=full&width=50&height=50')

Hi,
have you read the Codex about avatars ?
https://codex.buddypress.org/getting-started/guides/customizing-buddypress-avatars/

Jumping the gun a bit, but your enthusiasm is greatly appreciated. The core team will likely put together a wish list immediately before we start 2.1 development. Until then, you can watch the state of all-things-2.1 over on trac at: https://buddypress.trac.wordpress.org/milestone/2.1

Hi,
as you probably know, spam is a world wide disease and there are no ready to use solutions against it. Only tips at least.

So can you please search and read on this forum before asking for such a remaining question ?

https://buddypress.org/support/search/spam/

@sooskriszta totally agree with you on your 3 (relatively) objective tests – this is why I suggested 2 key features that need to be improved in buddypress *immediately*:

1) spam fighting
2) fragment caching

First, 99.9% of buddypress communities have to deal with spam and it is mission critical (who wants a website overrun with spam? users leave, google rank drops, etc.). How many forum threads are opened again and again about people asking for help dealing with spam? how many different methods need to be cobbled together? it just makes sense to take the best practices and build them into the core.

Second, performance is an issue that is more and more important not only because speed is a do or die issue (there is ample evidence of a direct link between a website’s speed and its success in converting and in pageview counts)

with buddypress, regular caching plugins simply do not work, we need fragment caching, and we need it YESTERDAY!

there is already a tentative step in the right direction with rarst’s fragment cache plugin but this should be developed into a full solution and built into core.

everyone will benefit from improvements in caching and it will make a MASSIVE impact on the overall quality and success of buddypress as a platform

/drops mic

And tables are not suitable for mobile devices

@sooskriszta Noted. But it can be done. If you look again at the BP survey results via mobile device, the table is responsive with some modifications made on Coyler’s code. Morever, as hnla mentioned in earlier post which I agree with, you do not change semantic markup to suit devices.

when 62.31% people list Responsive and 41.33% list Responsive, mobile-first as their Preferred BP Theme Features, to which specific aspect do you think they are referring?

Refers to whether the theme’s responsive styles (via CSS media queries or JS solution) were prepared for mobile viewing or for desktop viewing first.

1GB RAM is a minimum, 2GB RAM is ideal. As you scale up you may need more. On a good server setup you can actually see live (via SSH) how much of your RAM is being used up and how much is free. If you’re bottlenecking, you can contact the hosting company to add more RAM or bump you up to the next server. That is not the same as migrating to a new host… if it’s within the same company they should handle it for you seamlessly in the background.

Another option is to use Amazon (AWS) instead of a private server and it just scales up automatically as needed – they mostly charge by data rather than by server. They will be more expensive for most sites and will be slightly harder to set up, but they are also incredibly scalable.

A CDN isn’t really a “cache” in the way you imagine W3 working. It’s only caching resources (stylesheets, images, javascript files, etc) but not caching “content”. Your resources usually don’t go stale because they are not updated often. And if you do it properly, the cache can be broken any time you update a resource (by adding a version number to the enqueue in your theme). The version number gets appended to the URL of the resource, so if it changes the CDN thinks it’s a different file and immediately serves up a new file.

Content does go stale. By content I mean the data that is outputting for everyone to see right on the website. Like a profile, activity page, member directory, etc. This is the stuff that plugins like W3 are primarily used to cache (among other things as well).

You can integrate a CDN very easily using WP Super Cache. You can just turn off the content caching stuff and use it only for pushing your resources into a CDN. It’s a set it and forget it kind of setup for the most part.

If you happen to be in the Miami area on May 9, I’ll be speaking about scaling BuddyPress at the BuddyCamp (1st day of WordCamp Miami). http://2014.miami.wordcamp.org/
Should be a fun event.

@pswanson22
https://codex.buddypress.org/getting-started/customizing/changing-internal-configuration-settings/ has the following:

Set which blog ID BuddyPress will run on:
define ( ‘BP_ROOT_BLOG’, $blog_id );

Where $blog_id is the actual blog id number…

You could be using an older theme, which needs the new notification templates.

Contact the theme developer and tell them to look at the following change:
https://buddypress.trac.wordpress.org/changeset/7688/

Take note of the five additional files that need to be created and the change to /members/single/home.php

You could create sidebar-buddypress.php and change the BuddyPress page you are using to load this particular template:

<?php get_sidebar('buddypress'); ?>

That would be one way of doing this.

All of those are good.

Also, the BuddyPress code is on GitHub if you need to reference quickly

https://github.com/buddypress/BuddyPress

ajax.php is for bp-default theme. Theme compatibility uses buddypress-functions.php