BuddyPress.org

You will need to make a function that finds the role for the displayed user.
See: https://codex.wordpress.org/Class_Reference/WP_User
You will want to use a BuddyPress function in the ID paramenter instead of the wordpress functions shown in that codex article (see BP codex).

Havn’t looked into it fully for what your trying to do, but you will proburbly want to filter ‘bp_core_get_username’ and echo the function we made above.

Well, it’s one of the things I am more interested in to look at adding to core. Of course, just like anyone else, I need to make the case to the rest of the team that there ought to be a Like in BuddyPress, which is why I had a bit of an experiment in my Labs plugin.

If people like the idea for core, I would suggest they think the idea of a Like button through — bearing in mind we are changing how theming will be easier in 1.7 — in terms of where the button(s) should be, what should it do, any options it might merit, how it would replace Activity’s existing Favourite button. Perhaps even think about how it could be implemented in the code, and where the likes should be stored in a database, and how other 3rd party plugins could extend the Like button (I might want to make it work with my Achievements for BuddyPress, for example).

Once you’ve got something meaty, either post it somewhere on the BuddyPress.org forums, or make an enhancement ticket on https://buddypress.trac.wordpress.org/

@artsupplywarehouse the new links have been added to the Help Us Help You page. Thanks for the reminder to update the links.

I’m also interested in this, as forums will be an important part of my site when I put it up.

== Does the same thing in the bp-default theme? ==

Are you asking me if the issue will still be there using bp-default theme or are you telling me that it’s doing the same thing using the bp-default theme and mistakenly added the question mark?

The thing is, there’s something wrong with your BP theme – Bodybuilder Yukon ‘child theme – or your customization of the theme. I can’t even open up the site activity page. There are BP pages like my test account > activity > friends which is not rendering at all and the source code shows that it ends at “ Aside from which, each page takes too long to load, So different from what I see for example at http://demos.ithemes.com/buddypress/yukon/members/justin/

Is this a test site or did you install WP/BP in a physical subdirectory?

Something like this would do what you are looking for: https://wordpress.org/extend/plugins/custom-profile-filters-for-buddypress/

I run it on a School Board site where students and teachers self identify what school they are from in a dropdown, and that link takes you to a member directory of all of the users who selected something similar.

If the options were small enough, you could probably create a custom menu for each item that would take people to the listing for each selection using the URL format: http://domain.com/members/?s=photographer.

You could do it manually with something like this: https://wordpress.org/extend/plugins/buddypress-verified/. I’m not savvy enough to suggest how something like this could be built, but you might find that this is a good starting point.

@wassimo – it would require a major rewrite of many files.
Much easier solution would be to find decent hosting.

Currently, favs are stored as serialized array in wp_usermeta.

The OP is just asking for a total count.
Pretty easy to hook in and ++ / — a count within wp_bp_activity_meta table.

But a custom table would be better, imo,
You could use it for a total count scan.
And you could get specific about favs based all members – not just favs specific to a member as per the serialized array.

AND – get it out of wp_usermeta table – hurrah.!
The use of that table is becoming a real scalability issue.
Things like last_activity in user_meta is slooooow.
I think boone wants to move last_activity for BP 1.7 and use an existing activity table.

So maybe a redo of favorites is a natural task for 1.7 ?

edit – just saw the Paul comment that says:
“During development of BuddyPress 1.7, I’ll be revisiting the Like in BP Labs.”

Cool.

@djpaul was creating something “like” this in his BP Labs plugin. Here’s a link: http://byotos.com/2011/12/19/bp-labs-you-may-like-this/

You mean your Archive Slug for your Sitewide Forums and the Page name were also xforumsx as per your post above, Buddypress Forums page ( http://msflights.net/xforumsx ) ?

That would require major changes in your theme files. See how @sbrajesh at BuddyDev help others do this http://buddydev.com/forums/topic/ajax-tabs
DISCLAIMER – you’d need to update some deprecated or revised template tags/functions.

That would be at line 27 of https://buddypress.trac.wordpress.org/browser/tags/1.5.5/bp-themes/bp-default/registration/register.php which should be located at wp-content/themes/yourCurrentTheme/registration/register.php

@magoo25 glad you resolved it. If you were using a WP theme with BP template pack, that means that the transfer of BP template files to your active WP theme was corrupted/incomplete otherwise you wouldn’t have had to upload settings.php into your theme folder..

Please post at https://buddypress.org/community/groups/bp-jobs-board/ which has its own feed which some follow and at http://jobs.wordpress.net/

The reason you are having problems is due to mal-formed markup, if markup is broken then rendering engines have to make best guesses at how to render a DOM that makes sense to it and then try and apply what CSS properties it can .

Your immediate problem – the white text – is due to your header elements being unclosed. You have two unclosed elements in the <div id=”header”> block this means that the parser has to guess at what makes sense and it sees the last unclosed div and then takes the closing header tag and applies it to that last child div, the result is that #header is still actually open any properties it has are inherited if that’s their aspect to all further elements until the parser can find a suitable closing div thus the rule color: #fff; applied to #header is filtering through.

Finish off the two inner divs in #header with correct closing tags and the colour for the majority of body text will return to bp-default body colour.