BuddyPress.org

Never mind I used this css coding to add line breaks, still not perfect but it looks so much better than it used to!

#buddypress table.profile-fields p {
	margin-top: 10px !important;
	margin-bottom: 10px !important;
}

Hello,
actually I mean to merge content of members/single/settings/general.php and members/single/profile/edit.php.
My idea is to get custom BP profile fields (username) along with the email and password fields in the general settings tab.
When I copy plugins/buddypress/bp-templates/bp-legacy/buddypress/members/single/ to mytheme/buddypress/members/single/, those files don’t override plugin core files.

Hello danbp,

So far i understand you use bbPress and now you want a members directory, and eventually some additionnal fields on user’s profiles. And most of this should be private or “members only”, right ?
>> Correct, combined with private bbpress forums on a website with also public content.

I have set the “members” page I created as private, but it is still displayed when I go on the page as a logged out user. Why is that so?
Would it work if I would not connect the “members” page with BuddyPress in the settings, set the page to private and pull the dynamic content for the members list by a stortcode?

I can read into the codex of course, but do I need to learn to code to use BuddyPress?

Nicole

Thank you for your reply @danbp.

I actually created the profile field myself in Dashboard > Users > Profile Fields to emulate a captcha plugin. For some odd reason it appears under Account Details instead of under Profile Details on the Register page and is missing from the backend so I am unable to edit/delete it.

Today I found there was a member-loop.php added to my theme files. Could this be part of the problem? Should I add the member template file to the theme as well?

<?php

/**
 * BuddyPress - Members Loop
 *
 * Querystring is set via AJAX in _inc/ajax.php - bp_dtheme_object_filter()
 *
 * @package BuddyPress
 * @subpackage bp-default
 */

?>

<?php do_action( 'bp_before_members_loop' ); ?>

<?php if ( bp_has_members( bp_ajax_querystring( 'members' ) ) ) : ?>

	<div id="pag-top" class="pagination">

		<div class="pag-count" id="member-dir-count-top">

			<?php bp_members_pagination_count(); ?>

		</div>

		<div class="pagination-links" id="member-dir-pag-top">

			<?php bp_members_pagination_links(); ?>

		</div>

	</div>

	<?php do_action( 'bp_before_directory_members_list' ); ?>

	<ul id="members-list" class="item-list" role="main">

	<?php while ( bp_members() ) : bp_the_member(); ?>

		<li>
			<div class="item-avatar">
				<a href="<?php bp_member_permalink(); ?>"><?php bp_member_avatar(); ?></a>
			</div>

			<div class="item">
				<div class="item-title">
					<a href="<?php bp_member_permalink(); ?>"><?php bp_member_name(); ?></a>

					<?php if ( bp_get_member_latest_update() ) : ?>

						<span class="update"> <?php bp_member_latest_update(); ?></span>

					<?php endif; ?>

				</div>

				<div class="item-meta"><span class="activity"><?php bp_member_last_active(); ?></span></div>

				<?php do_action( 'bp_directory_members_item' ); ?>

				<?php
				 /***
				  * If you want to show specific profile fields here you can,
				  * but it'll add an extra query for each member in the loop
				  * (only one regardless of the number of fields you show):
				  *
				  * bp_member_profile_data( 'field=the field name' );
				  */
				?>
			</div>

			<div class="action">

				<?php do_action( 'bp_directory_members_actions' ); ?>

			</div>

			<div class="clear"></div>
		</li>

	<?php endwhile; ?>

	</ul>

	<?php do_action( 'bp_after_directory_members_list' ); ?>

	<?php bp_member_hidden_fields(); ?>

	<div id="pag-bottom" class="pagination">

		<div class="pag-count" id="member-dir-count-bottom">

			<?php bp_members_pagination_count(); ?>

		</div>

		<div class="pagination-links" id="member-dir-pag-bottom">

			<?php bp_members_pagination_links(); ?>

		</div>

	</div>

<?php else: ?>

	<div id="message" class="info">
		<p><?php _e( "Sorry, no members were found.", 'buddypress' ); ?></p>
	</div>

<?php endif; ?>

<?php do_action( 'bp_after_members_loop' ); ?>

@shanebp Thanks for the reply.

[…]in any relational table, if an item is assigned to a group ID and that group ID no longer exists in the table that holds group IDs, then that data will not be displayed, ie. orphaned.

I deleted through the admin panel so I am not sure what was deleted, that was what I meant by asking if is was standard behaviour. Possibly what I should have said is; when a user deletes a group by using the ‘bp-profile-setup’ page to click on the ‘delete group’ button, is buddypresses default behaviour to just drop the group and leave the profile data in the table or does it also iteratively remove the profile fields?

I can see the reason why you would want to leave the data in the table (and also reasons why you wouldn’t). I had a quick look at the code but I am not familiar enough with it yet to pinpoint the exact code block.

If fields are not deleted then I guess any fields directly referenced would still be visiable on the site. That may be misleading to user as they may assume deleting a group would also remove fields. However you wouldn’t want a group to be deleted by accident and then a large amount of data be lost. I would guess a system of deleting the group and then updating each profile field to explicitly notify calling functions that their parent has been deleted would be appropriate in the circumstance.

I have used a relational database before but I am unfamiliar with the logic employed by buddypress to interact with it.

The behaviour I was was getting was weird. When I deleted a group and created it again no fields were showing. Then when I added a field, it had a value immediately after creating so something weird was going on so I thought I would ask to see if you knew if the profile data gets deleted when a user clicks delete group in admin panel.

I am starting again now so will pay closer attention to all data as it goes into fresh tables but sometimes it is harder to see to absence of data compared to the addition of new data.

Why? BP will always create a Base group.

I am running a multisite where individual user blogs can create their own fields (https://codex.buddypress.org/themes/guides/segregated-x-profile-fields-for-multisite/).

As the article says:

This code will not create dummy content, so for every new site you will need to create a Profile Fields group and add profile fields to it manually.

When I create new site there are no field groups made at all which I assumed is what it was talking about. Also I wanted to have a default set of groups but allow subsite to edit them. If they want to get default groups back they can just delete all their groups and default will be restored. I could add a separate button for that but I just figured I’d do it like this, no particular reason, I am still in early stages of project.

I think there were other errors at play so starting from scratch with a little more understanding will hopefully enlighten me. I will be duplicating tables this time instead of using meta table.

Well, group meta allows meta data to be applied to groups. I’m thinking along the lines of data in the usermeta table which is only consumed by specific groups. This might be expressed as a name/value pair in the profile. So with reference to my original example, a GroupName profile value would include:
school:Robert
home:Bobby
coolGame:Zarcon

The BuddyPress Profile Shortcodes plugin allows for custom fields and related shortcodes to be used. This is much closer to my needs but still not quite there. I can’t create a profile field for every possible group. Ideally there would be a pulldown of groups to which the user belongs, where they can enter the name they wish the use for that group, and the group/name pairs would be displayed in a grid.

Now I’m thinking one of the better user meta plugins could handle that. But I would also need to customize it so that there can only be one WP user with a specific value for a specific group. This is a unique key per group, as some reference to @Bobby can’t apply to more than one person, but the @Bobby in one group can be different from @Bobby in another group.

On the client side, I would then need to modify bbPress to get the user name that’s specifically for the current group, rather than using wp_get_current_user()->display_name or whatever it has there. For example:
get_user_meta($user_id,’groupName_’.$group_id,true)
or better
get_user_meta($user_id,’groupNames’,false)[$group_id]

Actually I’d rather abstract all requests for a user name to a function which can then be replaced with custom code just once. I don’t suppose anyone has already done that, or it’s been proposed as a BP/BBP enhancement?

I’m a noob with coding into WP, haven’t touched BP/bbP, and know little about the APIs, so please bear with me on the syntax and other specifics and focus on the concepts. Thanks.

The more I try to flesh it out above the more it seems possible for me to do this myself. But it would be really helpful if someone has already done it. Or if someone with knowledge in this area can see a more direct line from an exiting plugin to the solution I’m describing.

Thanks for your time!!

My apologies @danbp I had a plugin called “BuddyPress xProfile Custom Fields Type” set up, that’s where the button came from. I just deactivated the plugin. But even when I still try to fill out the registration form, there’s no error that shows up this time, however, it takes me right back to that same registration page and it still did not create that new user for me. It would still just show up on the screen like this:

New registration screenshot

Any suggestions why this is still happening? Also, is there a good plugin that anyone can recommend for me to use so that when users create their profiles, they’ll be able to upload a profile picture?

I’ve been staring at the code for a while and it’s starting to make sense.

I’m not great with databases but looking at the function I gather it changes a few fields into primary keys that point to the data table so fields can be individual.

It runs the table modification code on the dbdelta_create_queries hook.

The wordpress codex seems to say that this action will happen anytime a database or a table is created.

Am I right in saying that this only ever has to be run once? Can I just run it once on admin init then remove it and add the modify_bp_global_xprofiles_tablenames at runtime or have I misunderstood it?

Hello Shane,
I called manually the URL in the browser with the ?var1=TEST to be sure that it’s called properly but nothing change.

I’m calling it from the buddypress-xprofile-custom-fields-type plugin, do you think could be some filter that intercept querystring and reset it ?

Ok now everything works as you mentioned, but there’s just one caveat. The xprofile gets updated fine, but it’s not updating the actual Members Type field in the Extended Profile section of the Users panel in the backend.

To clarify, when we make the xprofile field it’s a completely separate field than the Members Type field that Buddypress introduced recently. So in the Users->Extended Profile section there’s two fields for Member Types, the one we created and the one Buddypress introduced. Your code is only affecting the one we created and not the real Buddypress Member Type field. Is there a way to have the BP Member Type field get updated with the corresponding member type from the xprofile field?