BuddyPress.org

However, not only dots are a problem: with ‘oder Entsprechendes’ (instead of ‘o.ä.’) it doesn’t word as well.

As well it does not work with ‘Jahr der Teamgründung oder Geburt’.

So, maybe the length of the field names is the problem. –

Therefore again: Is there a possibility to address profile fields by other means than with their field names? Are there e.g. id-numbers or something like that, which I could use (instead of the names)?

Nice, I was actually looking at that a couple of days ago. I had tried a few things out, but to no avail.

Here’s where i’m at: I’ve commented the above edited section of members-loop.php.

In my bp-custom.php i’ve copy/pasted the code from the link you sent, and have applied the following edits to it:

    private function get_custom_ids() {
        global $wpdb;
 
        // collection based on an xprofile field
		// WP_User_Query arguments
		$args = array (
			'role'           => 's2member_level2',
			'fields'         => array( 'id' ),
		);

		// The User Query
		$user_query = new WP_User_Query( $args );	
		//The User Loop
		if ( ! empty( $user_query->results ) ) {
			foreach ( $user_query->results as $user ) {
				$custom_ids = $user.",";
			}
		} else {
			// no users found
		}
        //$custom_ids = $wpdb->get_col("SELECT user_id FROM {$wpdb->prefix}bp_xprofile_data WHERE field_id = 8 AND value = 'no'");
		
        return $custom_ids;
    }  

I also, made the lower two edits you suggested to the $query_array and return $new_count.

currently i’m getting this error:

Catchable fatal error: Object of class stdClass could not be converted to string in /home/collegi8/public_html/wp-content/plugins/bp-custom.php on line 30

line 30 is:

$custom_ids = $user.",";

Thanks for all your help man,

M

The basic issue is resolved.

Regarding the two persting problems I have started more specific topics:

https://buddypress.org/support/topic/age-for-each-user-instead-of-age-for-logged-in-user/

and

https://buddypress.org/support/topic/addressing-profile-fields-with-complex-names/

Therefore, for my point of view, this topic could be closed.

@hnla / https://buddypress.org/support/topic/different-profile-types-and-different-user-roles-part-ii/#post-201146:

By chance I found the solution regarding the ‘default user role’-issue:

Within the wp-admin-folder there is not only an options-general.php, rather as well an options.php.

Within the comment at the beginning of this file is written: ‘If accessed directly in a browser this page shows a list of all saved options along with editable fields for their values.’

Therefore I adressed this file with 1a-spielwiese/wp-admin/options.php – and there I found the opportunity to change the default user role:

http://1a-spielwiese.de/wp-content/uploads/2014/10/wp-admin-options-php.jpg

After changing it into ‘fan’ (note: it’s not possible to leave the line blank!), on the page options-general.php?page=wp-roles-at-registration it is now possible to select only the roles ‘fan’ and ‘team’:

http://1a-spielwiese.de/wp-content/uploads/2014/10/rar-settings_without_subscriber.jpg

And after saving it, ‘subscriber’ disappears from the registration page as well:

http://1a-spielwiese.de/wp-content/uploads/2014/10/register-page_without_subscriber.jpg

—-

However, these other above mentioned problems:

A. How can I make profile fields, which are asigned only to one member category / user role, ‘required’? Cfr. above.

C. What is the purpose of the penultimate step of the instructions of @noizeburger? – What have I to check for seeing, whether it works or not?

and

D. Why does the last step of the instructions of @noizeburger do not work for me? How can I make the member category / user role unchangeable for my members?

@amalsh / @jonaro / @lebearuk / @kamillamonkey and @jeffacubed:

Do you have any idea regarding this issues?

– cfr. regarding D.: http://kampfsportlerinnenneuwied.1a-spielwiese.de/wp-content/uploads/sites/2/2014/09/user_role_still_changeble.jpg –

are still unresolved.

I found two more solutions:

1st:

a) The place of the field for determining the user role is depending on the plugins/wp-roles-at-registration/wp-roles-at-registration.php

The relevant line of the original version of that file is:

add_action('bp_after_signup_profile_fields', array($wp_rar_plugin, 'bp_choose_roles_registration_form'));

I substituted there bp_after_signup_profile_fields by template_notices and now the field at issue is displayed not the end, rather at the beginning of my registration page:

http://1a-spielwiese.de/registrieren/

b)

For creating the headline and the introductory text I made a second change within the same file. I changed the following section. The first and the last line of the quote is the original code, and the lines inbetween I inserted:

    <div class="register-section" id="user-role-section">
    
    <h4-a><?php _e( 'Benutzer/in/rolle', 'buddypress' ); ?></h4-a>

    <p><small><em>Entscheide Dich bitte als allererstes f&uuml;r eine der Benutzer/in/rollen "Team" oder "Fan" (bitte w&auml;hle nicht die Rolle "Subscriber"; diese Angabe soll noch gel&ouml;scht werden). In Abh&auml;ngigkeit von Deiner Antwort wirst Du nach Abschluss der Registrierung und wenn Du Dich das erste Mal bei 1a-Spielwiese einloggst und Dir Dein Profil ansiehst, die M&ouml;glichkeit haben, einige erg&auml;nzende rollenspezifische Profilangaben zu machen.</em></small></p>

    <label for="wp_rar_user_role"><?php echo $this->wp_rar_role_label; ?></label>

2nd:

As well I was able to integrate now not only the ‘base’-profile field group. For that it is neccessary to copy a long section of the buddypress register.php. This sections begins with:

			<?php /***** Extra Profile Details ******/ ?>

			<?php if ( bp_is_active( 'xprofile' ) ) : ?>

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

				<div class="register-section" id="profile-details-section">

					<h4><?php _e( 'Profile Details', 'buddypress' ); ?></h4>

					<?php /* Use the profile field loop to render input fields for the 'base' profile field group */ ?>

					<?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

And it ends with:

					<input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php bp_the_profile_field_ids(); ?>" />

					<?php endwhile; endif; endif; ?>

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

				</div><!-- #profile-details-section -->

			<?php endif; ?>

The only two things, which are obligatory then:

• You have to insert the entire copied section behind the last line of the original section.
• And you have to change 'profile_group_id' => 1, into 'profile_group_id' => 2, (for adressing your second profile field group – and so on regarding the further profile field groups).

Besides I changed the <h4>-headline and inserted introductory text behind that headline. Therefore my code there is:

					<h4-a><?php _e( 'Profile Details - Teil II: Kontaktendaten', 'buddypress' ); ?></h4-a>

				<p><small><em>Beachte bitte, dass Du in zu den Profilfeldern in diesem Abschnitt selbst entscheiden kannst, wem Deine Angaben, die machst, angezeigt werden sollen.</small></em></p>

I get now managed to place the information from the profile fields Geschlecht, Jahr, Bundesland/Kanton in one line (instead below each other):

http://1a-spielwiese.de/teams/

The code is now:

<table-member border="0">
  <tr>
	<td>| Geschlecht: <?php bp_member_profile_data( 'field=Geschlecht' ); ?> | </td>
	<td>Geburts-/Gr&uuml;ndungsjahr: <strong><?php bp_member_profile_data( 'field=Jahr' ); ?></strong> | </td>
	<td>Bundesland/Kanton: <?php bp_member_profile_data( 'field=Bundesland, Kanton oder Wahlkreis' ); ?> / </td>
	<td><?php bp_member_profile_data( 'field=A:Bezirk oder Statutarstadt; CH: Bezirk o.ä.; D: LANDKREIS oder KREISFREIE STADT; Li: Gemeinde' ); ?> |</td>
   </tr>
</table-member>

Nevertheless

• the problem regarding the field ‘A:Bezirk oder Statutarstadt; CH: Bezirk o.ä.; D: LANDKREIS oder KREISFREIE STADT; Li: Gemeinde’ persits: That information should appear at the ende of the line, betwen ‘/’ and ‘|’.
• and as well I would still like to know, whether it is possible to transform the ‘year of birth’-information into an ‘age’-information.

1. I renamed the second field from ‘Teamgründung bzw. Geburtsjahr’ into ‘year’ – and it works.

2. With the field ‘Bezirk oder Statutarstadt; CH: Bezirk o.ä.; D: LANDKREIS oder KREISFREIE STADT; Li: Gemeinde’, again, it does not work. – Therefore I guess, the problem are blank, points etc. – Is true? Is there a any way to resolve the problem?

3. Is there any way to get displayed the age at any current moment (instead of the year of brith or team fundation, which is inserted into profile fields)?

@ https://buddypress.org/support/topic/modifying-the-member-list/#post-187019:

wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress/members/members-loop.php

To modify this file, you make a copy of it and put it into your child-theme
/your-child-theme/buddypress/members/members-loop.php

I did it, and inserted behind:

<?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' );
*/

?>

the following code:

				<?php bp_member_profile_data( 'field=Geschlecht' ); ?>
				<br>
				<?php bp_member_profile_data( 'field=Teamgründung bzw. Geburtsjahr' ); ?>
				<br>
				<?php bp_member_profile_data( 'field=Bundesland, Kanton oder Wahlkreis' ); ?>

The first and the third fields are displayed; the second not. – Why and how can I change it?

I decided to test theses instructions – and in general they work.

My registration page has now a new design:

http://1a-spielwiese.de/registrieren/

This result I got using two means:

1st:

I tested with ‘Simple Custom CSS’-Plugin that code:

#buddypress .standard-form #basic-details-section, #buddypress .standard-form #blog-details-section, #buddypress .standard-form #profile-details-section {
    border: 2px solid #8b008b;
	float: none;
  	clear: left;
  	width: 100%;
  	padding: 10px;
  	margin-bottom: 1em;
}

#user-role-section {
  	border: 2px solid #8b008b;
    float: none;
    width: 100%;
  	padding: 10px;
}

#wp_rar_user_role {
      width: 100%;
    }

h4-a {
	color: #8b008b;
	font-size: 11px;
	font-size: 1.1rem;
  	font-weight: bold;
	letter-spacing: 0.05em;
	line-height: 1.9091;
	text-transform: uppercase;
}

.wp-editor-container {
    border: 1px solid #DCDCDC;
}

Finally I will insert it into my child-theme.

2nd:

The relecant section of the register.php with in my reddle-child/buddypress/members-folder is now:

		<?php if ( 'request-details' == bp_get_current_signup_step() ) : ?>

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

			<p><?php _e( 'Mitglied bei 1a-Spielwiese zu werden, ist sehr einfach - und kostenlos. F&uuml;lle einfach die Felder unten aus und wir erstellen f&uuml;r Dich umgehend ein Benutzer/in/konto und in K&uuml;rze auch einen eigenen Blog (Webseite).', 'buddypress' ); ?></p>

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

			<div class="register-section" id="basic-details-section">

				<?php /***** Basic Account Details ******/ ?>

				<h4-a><?php _e( 'Account Details', 'buddypress' ); ?></h4-a>

				<p><small><em>Diese Daten werden f&uuml;r Deine Registrierung als neues Mitglied und die Einrichtung Deines eigenen Blogs (Webseite) ben&ouml;tigt.</em></small></p>

				<label for="signup_username"><?php _e( 'Username', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
				<?php do_action( 'bp_signup_username_errors' ); ?>
				<input type="text" name="signup_username" id="signup_username" value="<?php bp_signup_username_value(); ?>" />

				<label for="signup_email"><?php _e( 'Email Address', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
				<?php do_action( 'bp_signup_email_errors' ); ?>
				<input type="text" name="signup_email" id="signup_email" value="<?php bp_signup_email_value(); ?>" />

				<label for="signup_password"><?php _e( 'Choose a Password', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
				<?php do_action( 'bp_signup_password_errors' ); ?>
				<input type="password" name="signup_password" id="signup_password" value="" class="password-entry" />
				<div id="pass-strength-result"></div>

				<label for="signup_password_confirm"><?php _e( 'Confirm Password', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label>
				<?php do_action( 'bp_signup_password_confirm_errors' ); ?>
				<input type="password" name="signup_password_confirm" id="signup_password_confirm" value="" class="password-entry-confirm" />

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

			</div><!-- #basic-details-section -->

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

			<?php /***** Extra Profile Details ******/ ?>

			<?php if ( bp_is_active( 'xprofile' ) ) : ?>

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

				<div class="register-section" id="profile-details-section">

					<h4-a><?php _e( 'Profile Details', 'buddypress' ); ?></h4-a>

				<p><small><em>Diese Daten werden k&uuml;nftig in Deinem Profil angezeigt. Einige Angaben sind verpflichtend, um aussagekr&auml;ftige Profile zu erhalten; bei anderen Formularfeldern ist es Dir selbst &uuml;berlassen, ob Du Angaben machst oder nicht.</small></em></p>

					<?php /* Use the profile field loop to render input fields for the 'base' profile field group */ ?>

					<?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

					<?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>

						<div<?php bp_field_css_class( 'editfield' ); ?>>

							<?php
							$field_type = bp_xprofile_create_field_type( bp_get_the_profile_field_type() );
							$field_type->edit_field_html();

							do_action( 'bp_custom_profile_edit_fields_pre_visibility' );

							if ( bp_current_user_can( 'bp_xprofile_change_field_visibility' ) ) : ?>
								<p class="field-visibility-settings-toggle" id="field-visibility-settings-toggle-<?php bp_the_profile_field_id() ?>">
									<?php printf( __( 'This field can be seen by: <span class="current-visibility-level">%s</span>', 'buddypress' ), bp_get_the_profile_field_visibility_level_label() ) ?> <a href="#" class="visibility-toggle-link"><?php _ex( 'Change', 'Change profile field visibility level', 'buddypress' ); ?></a>
								</p>

								<div class="field-visibility-settings" id="field-visibility-settings-<?php bp_the_profile_field_id() ?>">
									<fieldset>
										<legend><?php _e( 'Who can see this field?', 'buddypress' ) ?></legend>

										<?php bp_profile_visibility_radio_buttons() ?>

									</fieldset>
									<a class="field-visibility-settings-close" href="#"><?php _e( 'Close', 'buddypress' ) ?></a>

								</div>
							<?php else : ?>
								<p class="field-visibility-settings-notoggle" id="field-visibility-settings-toggle-<?php bp_the_profile_field_id() ?>">
									<?php printf( __( 'This field can be seen by: <span class="current-visibility-level">%s</span>', 'buddypress' ), bp_get_the_profile_field_visibility_level_label() ) ?>
								</p>
							<?php endif ?>

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

							<p class="description"><?php bp_the_profile_field_description(); ?></p>

						</div>

					<?php endwhile; ?>

					<input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php bp_the_profile_field_ids(); ?>" />

					<?php endwhile; endif; endif; ?>

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

				</div><!-- #profile-details-section -->

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

			<?php endif; ?>

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

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

				<?php /***** Blog Creation Details ******/ ?>

3nd:

Nevertheless I have two questions regarding the design:

a) Why the 100%-width for #wp_rar_user_role is ignored?

b) How can I place the third section (‘Mitglieder-Kategorie’) above the other two sections (or between the other two sections)?

4th:

I recognised as well: Deleting there:

<?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

'profile_group_id' => 1, results in getting not only displaying the ‘base group’ of the xProfile fields, rather all fields of all field groups. 🙂

Questions:

a) How can I get the names (titels) of the different xProfile field groups displayed as well?

b) How can I ensure, that only new members, which choose the user role ‘team’, get displayed the profile fields for teams and new members, which choose the user role ‘fan’, get displayed the profile fields for fans?

I’ve played with various membership plugins and user role assignments, but the more I play, the more combinations I stumble upon and the more customization is required (or additional plugins for mapping and linking fields).

I’m currently exploring Users Ultra out of the box, which seems to do everything I want (minus geolocation), however their documentation isn’t very helpful so I’m waiting to hear from their support staff.

Regarding Geo Mashup, does it have the ability to map a custom profile field (address) to display a map on the user’s profile via shortcode?

The User Pro plugin is also starting to look like a viable option.

So, the following questions remain:

A. How can I make profile fields, which are asigned only to one member category / user role, ‘required’? Cfr. above.

B. Anyone knows, whether there is a function already written, which allows to change or delete the standard user role in WP MultiSite?

C. What is the purpose of the penultimate step of the instructions of @noizeburger? – What have I to check for seeing, whether it works or not?

D. Why does the last step of the instructions of @noizeburger do not work for me? How can I make the member category / user role unchangeable for my members?

@amalsh / @jonaro / @lebearuk / @kamillamonkey and @jeffacubed:

Do you have any idea regarding this issues?

Follow-up:

7th:

Capability Manager Enhanced to define custom user roles, if you’re not satisfied with the default wordpress roles (subscriber, contributor,…).
The first step is to create your user roles

https://buddypress.org/support/topic/resolved-different-profile-types-and-different-user-roles/

As ready implied there: I did this – and it works so far.

8th:

Create a xprofile field (selectbox) with the title “User Role” and name the options “Band Role” and “Fan Role” – in my case. You can call them whatever you want. Place this field in the “base” profile group, otherwise it won’t be shown during registration. Also make the field “required”. In my case the user can’t decide, if the visibility of the field can be changed.

I did it already, when I installed and activated ‘BP Profile Search’-plugin – and it works.

However, to choosed a dropdown menu and the categories ‘team’ and ‘fan’.

9th:

I modified:

?php
function custom_bp_core_signup_user($user_id) {
    $user_role = strtolower(xprofile_get_field_data('User Role', $user_id));
    switch($user_role) {
        case "Band Role":
            $new_role = 'band';
            break;
        case "Fan Role":
            $new_role = 'fan';
            break;
    }
    wp_update_user(array(
        'ID' => $user_id,
        'role' => $new_role
    ));
}
add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 10, 1);

into:

function custom_bp_core_signup_user($user_id) {
    $user_role = strtolower(xprofile_get_field_data('Mitglieder-Kategorie (Team oder Fan?)', $user_id));
    switch($user_role) {
        case "Team":
            $new_role = team';
            break;
        case "Fan":
            $new_role = 'fan';
            break;
    }
    wp_update_user(array(
        'ID' => $user_id,
        'role' => $new_role
    ));
}
add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 10, 1);

(I omitted <?php, because I created not a new bp-costum.php, rather inserted the code into my yet existing bp-costum.php. I inserted the modified code above the line ?>.)

I did not understand, which effect this insertion should have – but, however, – as far as I see – it causes no harm.

Did anyone understood, for which purpose the above mentioned code is?

10th:

I inserted as well:

//hide the user role select field in edit-screen to prevent changes after registration
add_filter("xprofile_group_fields","bpdev_filter_profile_fields_by_usertype",10,2);
function bpdev_filter_profile_fields_by_usertype($fields,$group_id){

//only disable these fields on edit page
if(!bp_is_profile_edit())
return $fields;
//please change it with the name of fields you don't want to allow editing
$field_to_remove=array("User Role");
$count=count($fields);
$flds=array();
for($i=0;$i<$count;$i++){
if(in_array($fields[$i]->name,$field_to_remove))
unset($fields[$i]);
else
$flds[]=$fields[$i];//doh, I did not remember a way to reset the index, so creating a new array
}
return $flds;
}

into my bp-costum.php – again above the line ?>.

It does not work:

— threre the user role is still changeable:

http://kampfsportlerinnenneuwied.1a-spielwiese.de/wp-content/uploads/sites/2/2014/09/user_role_still_changeble.jpg

— http://1a-spielwiese.de/members/kampfsportlerinnenneuwied/profile/edit/group/1 causes an redirection error. – The redirection error disappears, when I’m not logged in as kampfsportlerinnenneuwied, rather as superadmin.

@ section 5th, part c):

'I guess it’s, because the “fan-question” requires as well an answer; but it is not answered, because that member is a team (not a fan).'

It’s in deed that: When I change the (first) “fan-question” from ‘required’ into ‘not required’ it’s possible to save the answer of kampfsportlerinnenneuwied regarding the team question, and it is displayed correctly in the frontend:

http://1a-spielwiese.de/wp-content/uploads/2014/09/kampfsportlerinnen_answer.jpg

But I don’t want to change the “fan-question” from ‘required’ into ‘not required’.

—-

PS.:

The text of the second “fan-question” was still not displayed; and the text of the 5th question (‘Ergänzende Hinweise zu Deinem Geschlecht’) of the ‘base group’ wasn’t displayed as well:

http://1a-spielwiese.de/wp-content/uploads/2014/09/text_missing.jpg

It was because I deactivated (by chance) ‘Buddypress xProfile Rich Text Field’-Plugin. Reactivating it, both profile fields get displayed again.

Sorry:

This is the list of my plugins:
BackWPup
Better WordPress Minify
Breadcrumb NavXT
Buddypress
BuddyPress Registration Groups
Formulario de Contacto 7
Cookie Law Info
Gears
Hide Admin Bar From Non-admins
Hide User Profile Fields
Límitador de intentos de login
Nav Menu Images
Paid Memberships Pro
PMPro Check Levels
PMPro Customizations
PMPro Email Templates
PMPro Register Helper
Regenerate Thumbnails
Remove Dashboard Access
Revolution Slider
Simple Social Icons
Editor de Roles
WordPress SEO
WP-Optimize
WPBakery Visual Composer
WP Google Fonts
WP Smush.it
WP Super Cache
WP User Frontend Pro

My theme is Klein (http://klein.dunhakdis.me/)

BP ver 2.0.2
Theme name OneCommunity
I’m able to create a new field in another group
I saved changes
I installed Buddypress Xprofile Custom Fields Type and if I select for the field type something that offered by this plugin it works fine.
Regards
I. Lesher

Thank you all,
As ACF doesn’t do the job,
is there any other way to add an edit box to the fields profile as my client wants?
Thanks in advance
I. Lesher

Ya I’m using sweetdate. Definitely a child-theme issue. I restored to base SD and it went away. I’ve disabled all plugins (other than BP) and am deleting functions.php code like 100 lines at a time.

interestingly, I added a 4th profile group, and now this problem only occurs on the FIRST profile group. The second profile group (About) no longer repeats fields.

I know it’s not your job to support this! 🙂 just wondering if anything popped into mind. I have the production site in maintenance mode because if people edit + save their profiles with the repeated fields populated, it’s saving the information doubly as well, which will persist even after I fix this bug. D: eek.