BuddyPress.org

First one is available out of the box and the second one can be done through plugins

late to the party but I think $bp->loggedin_user->domain will do it if you global $bp;
I saw this @ https://codex.buddypress.org/developer-docs/the-bp-global/ FYI

@janismo I’ve slightly lost track of what you are trying to do and need to reference the other threads, if this is running in a profile loop then I’m not sure there isn’t a simpler approach than this one outlined here (not sure you really need to do xprofile_get_field_id_from_name), but it’s late , I’m tired and not thinking clearly

`<?php
$field_id = xprofile_get_field_id_from_name( ‘Type’ );
$field = xprofile_get_field( $field_id );
$value = $field->data->value;

if ( bp_the_profile_group_name() == ‘Type’ && $value == ‘114’ ) {
( bp_has_profile( ‘profile_group_id=1,3,4′ ) ) : while ( bp_profile_groups() ) : bp_the_profile_group();
}
?>`

Full code, which should be placed in profile-loop.php,
Did I understand correctly, what @boonebgorges tried to explain?
@hnla please, take a look on this.

thank you guys!

here’s the link to custom community theme in the WP repository:
https://wordpress.org/extend/themes/custom-community

demo site is now here:
http://www.custom-community.themekraft.com/

I’ve added to the ticket, found the cause.

I’ve added to the ticket, can’t replicate the issue.

date() returns a string, it doesn’t display it. You’ll need to use the ‘echo’ statement to display it.

That’s a basic PHP question, not anything BuddyPress specific – Google “php echo”

To work with the templates and significantly modify BuddyPress look and feel, a basic grounding in PHP is a pre-requisite.

Obviously when you edit a user in WP, it doesn’t append anything to the user_nicename.This happens when BP is active.

I’ve put my comments on the trac ticket.

@nuprn1
fwiw – the wordpress backend checks if the same user_nicename AND user_login exist. if it does, it will attach a suffix (this is part of wp-includes/registration.php – wp_insert_user)

So does that imply it’s not strictly a BP issue/ in which case the ticket really needs directing to WP if it’s to be dealt with.

i think its a hybrid issue – if you update the user via wp-admin – that uses wp_insert_user (maybe the name is being changed or something to trigger the suffix increased that is used in wp instead of the buddypress front-end way)

edit// ignore my ramblings: Previous two posts added while writing – mine null and void

Are you sure this is a BP issue though? I can’t replicate your issue on a local test install, that you have a customised site with members listed in some manner of grouping is suggestive of a plugin at work possibly? I may be wide of the mark though on that.

As was asked is there actually a ticket on this that we can look at or do you have a link to the post you made raising the issue.

fwiw – the wordpress backend checks if the same user_nicename AND user_login exist. if it does, it will attach a suffix (this is part of wp-includes/registration.php – wp_insert_user)

did you file a trac ticket?

nevermind – found it
https://trac.buddypress.org/ticket/2642

@Nit3watch No, I wasn’t suggesting that. But your plugin should take that into account if the functionality is dependant on BuddyPress. See https://codex.buddypress.org/extending-buddypress/make-your-plugin-buddypress-aware-v1-2/