[@1a-spielwiese Participant 12 years, 1 month ago]

@modemlooper:

Install BP extended settings plugin and choose option to hide activity tab on profiles.

Does this plugin still exist and work? – I couldn’t find it on wordpress.org.

[@1a-spielwiese Participant 12 years, 1 month ago]

@sharmavishal:

i have deleted/remove the activity post form in the user profile

How did you this?

@ All:

that leaves the activity post form in activity directory

I too want do delete the post form as well from the activity page. – Any ideas regarding this?

[@1a-spielwiese Participant 12 years, 1 month ago]

It works e.g. with:

#buddypress ul.item-list li img.avatar {
    width: 45px;
  	height: 45px;
}

Note:

1st #buddypress ul.item-list li img.avatar is also used for the photos within the member list. – So, I decided finally for 80px for the first pictures within in the activity list, and for 90px for the second photos there as well as for the photos within the member list.

2nd I tried to change within the member-loop.php

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

into

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

and to define within the ‘Simple Custom CSS’-Plugin:

#buddypress ul.item-list li img.avatar_2 {
    width: 110px;
  	height: 110px;
}

But this didn’t work.

[@1a-spielwiese Participant 12 years, 1 month ago]

@ 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?

[@1a-spielwiese Participant 12 years, 1 month ago]

@ Section 3rd, a)

I deleted now that code

    #user-role-section {
      width: 48%;
      float: left;
      clear: left;
    }
    #wp_rar_user_role {
      width: 50%;
    }

directly within the original wp-roles-at-registration.php (within the /wp-content/plugins/wp-roles-at-registration-folder) – and now the width is as I want.

How can I determine the same effect within ‘Simple Costum CSS’-plugin respec. inside by child-theme?

[@1a-spielwiese Participant 12 years, 1 month ago]

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?

[@1a-spielwiese Participant 12 years, 1 month ago]

Additional remark:

For my point of view such splitting of the member list would be useful for alle social networks, where we have members, which have already offline distinct social roles – like, e.g., offerers of certain products or services on the one hand and there clients on the other hand – and where it is not necessary (or not wanted) to bring all members of the social network into contact with each other, rather only the members of the one category (e.g. offerers) into contact with the members of the other category (e.g. clients).

[@1a-spielwiese Participant 12 years, 1 month ago]

My mistake:

On the subdomain-blog level there is not within the admin panel a section users/capabilities.

There are such sections. I assume, I had overlooked them before simply (- though I made in the meantime one of the subdomain-blog users to a root-blog user as well. But I guess not, that this could made thoses sections visible for me.)

So, now I can change the user role of the subdomain-blog users.

Persisting problem:

The xProfile field is still changeable for them:

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

[@1a-spielwiese Participant 12 years, 1 month ago]

Further update:

To the users of the root blog I can asign the new user roles ‘Team’ and ‘Fan’; but I can’t neither on the network level (there isn’t any change of user’s role possible) nor on the subdomain-blog level (there are the roles only: administrator, editor, author, contributor, subscriber).

• On the root-blog level there is within the admin panel a section users/capabilities.
• On the subdomain-blog level there is not within the admin panel a section users/capabilities.

[@1a-spielwiese Participant 12 years, 1 month ago]

@ D.:

I guess, the mistake was, that I – after creating the new user roles ‘Team’ and ‘Fan’ – forgot to asign my already existing members to that categories. But, however, when I try it now, then I can’t:

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

However, as alreday mentioned: On the registration page the new user roles are displayed:

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

[@1a-spielwiese Participant 12 years, 1 month ago]

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?

[@1a-spielwiese Participant 12 years, 1 month ago]

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.

[@1a-spielwiese Participant 12 years, 1 month ago]

@Hugo:

That is a wp setting – settings>general ‘New User Default Role’ You should be able to select any new role created from the dropdown.

It seems, that is only a WP SingleSite feature. I can’t find it within the WP general settings of my MultiSite installation – neither on the network level, nor on the root-blog level.

[@1a-spielwiese Participant 12 years, 1 month ago]

En passant: Is there any way for truly renaming the user roles from ‘contributor’ to ‘team’ and from ‘subscriber’ to ‘fan’, sothat I could keep the ‘Label’ simple (i.e.: without explaining: ‘Choose as Team: Contributor; and as Fan: Subscriber’)?

Whether renaming, I still don’t know. But with ‘Capability Manager Enhanced’-plugin I could create entirely new user roles ‘team’ and ‘fan’ – and with ‘WP Roles at Registration’-plugin i could place them on the registration page:

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

But a problem remains: How can I make ‘Subscriber’ not being the standard user role anymore?

[@1a-spielwiese Participant 12 years, 1 month ago]

@ 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.

[@1a-spielwiese Participant 12 years, 1 month ago]

@triplebit:

Now there is such text editor for form / profile fields:

https://buddypress.org/support/topic/new-plugin-xprofile-rich-text-field/

Thank you @needle (Christian Wach) for writing and @danbp for information.

PS.:

I just installed and activated the plugin, and my user ‘Fan Eins’ used it, for writing the word ‘Keine’ in italics:

http://1a-spielwiese.de/members/fan1/

[@1a-spielwiese Participant 12 years, 1 month ago]

@mercime:

It’s resolved now; the child-theme was activated only for the network-level, but not for the root-blog-level. Activating it for the root-blog-level as well, it works:

https://buddypress.org/support/topic/buddypress-2-1-bp-language/page/2/#post-200308

Thank you, @shpitzyl (https://buddypress.org/support/topic/buddypress-2-1-bp-language/page/2/#post-200062).

[@1a-spielwiese Participant 12 years, 1 month ago]

But nevertheless it does not work.

[@1a-spielwiese Participant 12 years, 1 month ago]

Thank you for answering. And I understood the answer.

And my file name is with “s”.

Best

🙂

[@1a-spielwiese Participant 12 years, 1 month ago]

‘Don’t ask if you don’t understand the answers.’

Don’t answer, if you do not understood the question (request)!

‘There is no text editor for form fields. This doesn’t exist. Or give the url if you know one.’

@triplebit and me know this! But we want to have it (in future times).

Best

🙂

[@1a-spielwiese Participant 12 years, 1 month ago]

Please, make an effort to read more carefully the answers you receive and avoid asking for the same thing in multiple topics ! 👿

@mercime: functions

1st:

The file name is functions.php

@mercime wrote ‘functions‘!

It was @shpitzyl (https://buddypress.org/support/topic/buddypress-2-1-bp-language/page/2/#post-199810), who wrote ‘function’ (without ‘s’).

‘Please, make an effort to read more carefully’ 😉

2nd:

I guess, different users follow different topics. 🙂

[@1a-spielwiese Participant 12 years, 1 month ago]

@mercime:

Let’s double-check that you have all the necessary materials:
– theme folder e.g. reddle-child
– style.css file in reddle-child theme folder
– function<strong>s</strong>.php file in reddle-child theme folder
– buddypress.php file in reddle-child theme folder

Should it be ‘function.php’ [singular] or ‘functions.php’ [plural]?

Cfr. https://buddypress.org/support/topic/buddypress-2-1-bp-language/page/2/#post-199810:

‘You need to put this code in function.php in your child theme.’

[@1a-spielwiese Participant 12 years, 1 month ago]

@danbp / https://buddypress.org/support/topic/creating-a-new-profile-field-type/#post-198965:

‘Maybe nice, but it’s a commonly admited bad idea to let users style your site.’

As I alreday said elsewhere, I would prefer anyway to place the profiles within the subdomain-blogs and not in root-blog.

Then it would be not “style my site” (by my users), but “style their [my users] own site” (by themselves).

‘If you want italics for some field title’

No, what I imagined what not a field title, rather a book or movie title, e.g.:

Favorite movie [= Field title]

Mädchen in Uniform by Leontine Sagan [= user content within that field]

Favorite Book [= Field title]

Tractatus Logico-Philosophicus by Ludwig Wittgenstein [= user content within that field]

[@1a-spielwiese Participant 12 years, 1 month ago]

/plugins/buddypress/bp-languages […] I can see the file in the original plugin folder I downloaded but it looks like it was removed when uploaded.

That folder is an “update-victim” of BuddyPress 2.1:

‘I’m using Buddypress 2.1. Now bp-language folder is lost’

https://buddypress.org/support/topic/buddypress-2-1-bp-language/

‘Same problem. bp-language folder is lost.’

https://buddypress.org/support/topic/buddypress-2-1-bp-language/#post-197888

[@1a-spielwiese Participant 12 years, 1 month ago]

The ability to favorite is already available though

By the way:

What does ‘favorite’ mean here: To ‘favorite’ the activity? Or to ‘favorite’ the subject (author) of that activity?

What is within BuddyPress the difference between ‘friends’ and ‘favorites’?