BuddyPress.org

I’ve done some more detective work now, and it seems that it has to be a PHP bug of some sort. Changing themes doesn’t work, even BuddyPress default wont display the “Notice for all” message to normal members with status “Participants”. Higher role levels like Editor or Administrator does get to see the message though, so this definitely has something to do with WordPress roles in combination with BuddyPress plugin. I also checked the source code of the page. When logged in as a low ranking member ( role Subscriber ) the text in the notice isn’t even part of the page source code…

Thanks BuddyBoss!

Looks like I have to use filters to modify the output. But the function itself is meant to be customized in BuddyPress 2.0 for easier modification of the output.

Yes, we are using database cache. The page is too slow without cache and Buddypress somehow unusable with.

sounds like a lot of servers-and a lot of ram. Is concurrent users and speed a priority for the buddypress teams I wonder?

Unfortunately, that doesn’t help at all. One is to create a demo kind, which is used to check if things are working in the expected way, is not for use for live sites also plus it is not compatible. (the groupomatic,the Second plugin is not compatible)

P.S 🙂 Though I stated what version of WordPress, buddypress and bppress versions am using on in my first post, I will restating it here also. (am using wordpress version 3.7.1 suffusion theme) (budypress 1.9 and bbpress 2.0 )

Pls

thanks guys. I understood that buddypress was working on splitting queries etc but wondered how it handled concurrancy issues in its present state and how the proposed query changes were expected to improve the situation.

The question was asked ‘how big a scale?’. Our project is not spec’d out that way yet (it will be), but I’m exploring possible solutions, but I’d say in the 100k concurrent user order of magnitude. We would expect a large number of groups and within those groups very large numbers say in the 6 figure order of magnitude.

cheers

I’ve been reading a lot about this issue and it looks like BP is missing some very basic functionality. This is the first time using it and right out of the gate I see that there are some things that have me baffled.

1) No way to create conditional fields. I’ve tried using the Gravity Forms User Registration Add-On plugin but there is no way to map fields properly. For example, in Gravity Forms I have Country, State and City fields. If someone selects United States as a Country for example, the next field that the user sees is the State field, but then I run into a problem when someone selects a City. In order to use conditional fields with Gravity Forms, I need to create many City fields (alabama-cities, alaska-cities etc). One City field for each State. These City fields are conditional fields that displayed to the user Cities based on what the user selects in the State field.

The problem is that Gravity Forms wants me to first create User Profile Fields in BuddyPress. Then map each Gravity Forms field to the appropriate User Profile Field. Since I have many Gravity Forms cities field, there is no way I can tell Gravity Forms to use the City that the user selects and map it to a City User Profile field in BuddyPress.

I’ve read a lot of posts on this forum dating back 5 years and no one has offered a working solution.

2) Also, Why is there no option for an admin to be able to deny users from changing their Screenname? How about an option that prevents user from modifying a specific field such as Gender? All I see is havoc and chaos if you allow users to change certain fields.

3) Why doesn’t BuddyPress offer a way to have different registration fields based on the user? Teacher / Student Registration, Doctor / Patient etc? It doesn’t make sense. Look at the core of BuddyPress. It’s a social network plugin. In almost every circumstance you have a need for one user have certain fields and another to have other fields. Trying to figure out how to show certain profile fields for one user and not another should be at the core of this plugin. Not to mention making it easy for the site owner to layout those fields so that they look nice. For example something as easy as defining the length of the fields. You can’t make those modifications without Firebug and CSS and PHP experience, or worse yet another plugin. If you use a plugin, then you have to pray to God the author of that plugin not to fall off a cliff or pray that he / she keeps that plugin conducive with the latest version of BP.

I don’t mean to gripe but BuddyPress it seems to me that at it’s core, very little thought was given to how people would actually use it. Almost like it’s piecemealed together.

Another big complaint is that it’s not compatible with the best WordPress themes on the planet – StudioPress. Shouldn’t the contributors of BP make sure that BP and StudioPress be compatible?

I’m sorry if this sounds like a rant, it’s not. It’s just frustration. BP looks awesome but underneath the hood, there are a lot of obvious problems. My suggestion is to do what WooCommerce, StudioPress and others do. Sit down and figure out how to handle the big issues first. If need be, charge for BuddyPress. If the problem is that you have a bunch of contributors who work on things “they” deem important and at their own leisure, then the plugin suffers. Charge for it. Sit down and listen to the complaints and address them based on customer priority. Pay someone to reply to this forum so we’re not waiting days for a response. You’ll have much happier users and a much better plugin. Just my 2 cents worth. Honestly, since BP is virtually the only Plugin of it’s kind, not taking my advice will lead to someone creating a better wheel and that point, it’s only a matter of time before BP becomes obsolete.

It’s been close to 24 hours and no response to my original question. If ANYONE has an answer as to how I can get a user to simply select a Country, then State, then City based on previous fields, I’d greatly appreciate it. Also if someone could please tell me how to prevent users from modifying certain fields that would be appreciated as well.

Thanks

UPDATE:

I’ve changed BuddyPress from being ‘network activated’ to just ‘activated’ on the main/root site. I don’t know what the recommended setup is these days, but we’ve had it network activated since BuddyPress only ran on WPMU.

Having it activated on the main site only means that the ‘bug’ now only affects the main site and not every site across the network. So the example I give above no longer shows the issue.

However, you can still see it on this page:

http://blogs.lincoln.ac.uk/test/

See how, whenever there is @lincoln.ac.uk either in the content of the page, or in a mailto link, BuddyPress injects a hyperlink with a random user’s email address following the root domain:

http://blogs.lincoln.ac.uk/amakrzanowska%40lincoln.ac.uk/

I’ve no idea how or why it’s constructing that URL and automatically inserting it whenever @lincoln.ac.uk is found in the body content.

Ideas much appreciated!