BuddyPress.org

OK, but is there a way to just get rid of the “read more” behavior anyway? I would like to please control the length of the excerpt, and make it long enough where it is a non-issue regardless of theme. The posting and other parts of buddypress are working great with the theme I have chosen, and other than this I don’t seem to have any “theme issues” yet. I’ve found the less ajax I have on pages the less conflicts I get with different themes and plugins anyway and would rather increase the size and test getting rid of excerpt cutoffs altogether due to potential conflicts and funky interaction with other ajax components. For this implementation, I think it would be much better to limit the size of posts when people make them, and not attempt to truncate them in the activity stream at all, to avoid other possible ajax interactions with something like lightbox or different themes. I’m not sure the ideal size to allow yet though. I would also like to look at limiting the size of posts but am hoping that’s easier after changing the “…” [read more] behavior. I am comfortable editing code if I have to, I’m just not sure where to yet.

These are the posts I’ve found of people trying to get rid of the “…” and [read more], or change the excerpt size and wording, but they’re old. There may be partial solutions in these threads but I’m afraid I don’t understand how to pull it all together or if they resolved it.

thank you.

Similar issue but didn’t see resolved, just replies stopped- https://buddypress.org/support/topic/activity-stream-read-moreview-link-missing/

https://wordpress.org/support/topic/vexatious-read-more-linkslack-thereof/

https://buddypress.org/support/topic/need-help-with-activity-stream/

I just found this : https://codex.buddypress.org/themes/theme-compatibility-1-7/bp-17-upgrading-template-packed-themes/

But can I do this if I am already using Buddypress 2.2 ?

I am using the plugin “BuddyPress Template Pack” to integrate Buddypress to my template.
The problem can probably come from there. I just saw that this pluging hasn’t been updated since 3 years.

Is there any other plugins to replace this one ? Or a manual way documentation ?

Thanks,

Mathias

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

Hello, if they are getting in some other way, will you please let me know?
I’m not accusing Buddypress, it’s great, but could someone please confirm for me that it doesn’t open up an alternative registration method somewhere?
It could be as simple as just increased users and an incompatibility with my captcha counting.
Thank you very much! 🙂

@r-a-y

hey r-a-y, thanks again.

just to be clear, i should be able to denqueue or whatever is necessary without mucking something up. that is, as long as is_buddypress() returns false then i don’t need all this BP “stuff”, yes?

cheers
mfs

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?

@r-a-y Sure I understand what you’re saying.

According to the end of your previous post, I am forced to load one of three files: buddypress.css in either child or parent, or buddypress.min.css in BP plugin directory.

What I’m saying is I don’t want any extra file loading. I will use my theme’s built in stylesheet to load these styles, not an external file like buddypress.css or buddypress.min.css.

It would be nice if there is a way to deregister or dequeue the stylesheet from loading, something like this:
wp_dequeue_style( 'bp-legacy-css' );
or
wp_deregister_style( 'bp-legacy-css' );

@r-a-y Does this mean that BP will ship with an unminified version of buddypress.css? I like that it’s minified by default, this is less file size to load. Is there not an option within BP to load the minified version if specified?

@danbp I guess there’s a misunderstanding so let me try to clear myself up. 🙂

I understand that buddypress.min.css has baseline styles for BP and I do plan to reuse some of the code. However, it is not necessary for this code to be loaded in an external file when I can incorporate it into my compressed CSS file generated by the preprocessor.

Secondly, disabling buddypress.min.css, I remove one HTTP request that doesn’t need to be there. In order to optimize the site’s load time, I need to get rid of any extra HTTP requests that are not necessary.

Third, buddypress.min.css is a stylesheet that contains styles. There should not be anything within that affects the functionality or interactivity of BP, right? I can’t see how getting rid of this file will cause BP not to work correctly, as you first stated. What do I not understand?

@bp-help

Thanks. I will have a look around the site and see what others are using. Im assuming most people do use the default Buddypress reg. Urgh I am rubbish at this stuff. Thanks. 🙂

Many thanks, @henrywright, for your response and support.

Your suggestion was what the theme developers also suggested.

As far as I am aware, on wpengine users are unable to access their php.ini. file.

Perhaps i might define the memory in wp-config.php which is accessible ! ??

In the meantime i have replicated/tested a SUCCESSFULL implementation on THREE other servers (bluehost, hostgator & hostingireland).

All are basic bog standard very very cheap shared hosting and carrying a multisite/buddypress installation – and all that that entails. (and one of these is very slow which is understandable)

However the latest response from a very considerably more expensive wpengine is

As for the issue with the memory limit on the server, this is unfortunately a limitation on the server here.

Thank you and have a great day!

Quite!

Hi @bp-help,

Yes I have, but I am so busy with other stuff at the moment I just wanted to know if I can stick to the buddypress reg for now? I mean, I have no idea if I did that and gained say 100 members and decided to start charging – how difficult would it be? Could I just export (or whatever) my members out and switch over to a payment option like s2member? And then in the future I can start to research payment registration options. I dont even know if I can add a payment (Paypal tab) to the default Buddypress sign up page? I guess I can right?