BuddyPress.org

To build this kind of feature, you need to be a PHP developer:

• You’d add new profile field groups for each type of stat (or if the stats are too complex for profile fields – a custom component to handle them).
• You’d then assign a role to each member based on whether they are a batter, pitcher or fielder – ideally implemented using the underlying WordPress user roles.
• Finally, you’d implement conditional logic in your templates to display appropriate profile field groups based on the member’s role.

Hi websitevala,

To add custom fields to your registration page, you’ll need to add xprofile fields. To do so in WP Backend, you should go / BuddyPress menu / Profile fields submenu

And for the other thing, as you noticed emails are hidden, there might be a spam risk reason to that. And as a user, i wouldn’t like to have my email shown on my profile.. So i dont think it’s a good idea.

hi @enderpal444

I think i would use BP members loop to do what you want to do as you can send meta_key to BP_Core_User::get_users. Then i would take benefit of the filters included in the 2 sql to change its behavior. This is what i’ve tried to add a filtering by geo position to the main BP Members directory. I guess you’ll need to ask Roger and Paul about efficiency…

in the functions.php of my active theme > http://pastebin.com/2HKsSZCc

i tried to have a ‘one pass’ approach

@pgideonbolger — I ran into this as well. I was going around in circles trying to override the defaults selector by selector. To override the defaults en masse, you have to address the fact that BP 1.5 uses enqueue to load the styles. You’ll want to stop it from loading the default styles and instead copy/paste the styles you want to retain from default.css into your child theme’s styles.css.

FYI, I got this info from https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/ – which is a helpful page – and am using it with success. But if you don’t want to search that page for the info, just grab the code below and add it to your child theme’s functions.php:
`
if ( !function_exists( ‘bp_dtheme_enqueue_styles’ ) ) :
function bp_dtheme_enqueue_styles() {

// You should bump this version when changes are made to bust cache
$version = ‘20120625’;

// Register stylesheet of child-theme
wp_register_style( ‘child-theme’, get_stylesheet_directory_uri() . ‘/style.css’, array(), $version );

// Enqueue stylesheet of child-theme
wp_enqueue_style( ‘child-theme’ );
}
add_action( ‘wp_enqueue_scripts’, ‘bp_dtheme_enqueue_styles’ );
endif;
`

Sorry, I was up late: BuddyPress.svn.WordPress.org

Thanks for the reply. Would you be able to go into further detail about what you mean by alternative sign-up page?

Ok. Before we play on your test server you need to contact your host and ask if you have SSH access to use a terminal. In the interim, we can try the concept out locally on your Mac.

How familiar are you with using the Terminal app? (it’s in Applications > Utilities) If not very, you’ll have to do some Googling to figure things out.

Open the Terminal app. Type these 2 commands:

cd ~/Desktop
svn co https://buddypress.trac.wordpress.org/trunk BuddyPress

That last command might take a couple of minutes. It’ll download a copy of BP trunk. Look at your desktop, and you’ll find a folder called “BuddyPress” containing… BP trunk

Then wait for the BuddyPress team to do a new update to trunk. Easiest way to do this is keep an eye on https://buddypress.trac.wordpress.org/log and remember what “Rev” it’s up to. When you spot an update, open Terminal again:

cd ~/Desktop/BuddyPress
svn up

“svn up” is an “update” command. It figures out what SVN revision your checkout of BuddyPress is on, compares that to the version on the server (it remembers what URL you fetched it from originally), and then downloads and applies any updates automatically.

This is the method I like doing on my servers, so maybe see if it works out for you.

@enderpal444 – thanks for posting your solution – that’s the sort of approach I was suggesting as ‘two pass’ – getting all the users unsorted, then sorting them, before iterating over them.

Efficiency might become an issue if your member numbers increase.

https://codex.buddypress.org/extending-buddypress/customizing-labels-messages-and-urls/

Plaza is a very nice website – it’s also a significant custom development.

Are you a skilled PHP developer with solid WordPress development experience (writing custom post types, taxonomies, url rewrites and such like)?

If you have those development skills (and in the case of Plaza – some strong design skills as well) or are willing to hire them in, then yes, BuddyPress is a suitable underlying platform to build the user profiles on, and to provide a backbone where you can unify their reviews and hotel submissions.