BuddyPress.org

Okay, so after some more testing, I’ve realized that Disqus does not work here (although it overwrites WP comments when on) and my theme is Optimize Press. Traditional blog posts and pages show in the activity stream when WP comments are used. However, for the better looking page templates, the comments do not show (these are built with their live editor).

Any thoughts on how to make this type of page work with BuddyPress and the Activity Stream?

Posted Enhancement Request – https://buddypress.trac.wordpress.org/ticket/6575#ticket
If you have any suggestions or changes @shanebp your input is appreciated.
Thanks

Thanks @shanebp,

Sadly neither of these filters will allow me to modify the ‘(required)’ text itself which is what I’m looking for, I guess I’m a little off in my request encompassing the entire label text as you pointed out the field name is filterable it’s the required portion that is outside of it as you can see in the code snippet;

<label for="<?php bp_the_profile_field_input_name(); ?>">
	<?php bp_the_profile_field_name(); ?>
	<?php if ( bp_get_the_profile_field_is_required() ) : ?>
		<?php esc_html_e( '(required)', 'buddypress' ); ?>
	<?php endif; ?>
</label>

And yes I realize I can replace it through the text-domain and a .po file, but I’d like to keep the (required) in the Buddypress Xprofile and target the inclusion of these fields specifically on the Woocommerce Checkout page where they’re included through the Buddypress for Woocommerce integration.

I’ll open an enhancement request, thanks for pointing that out, and specify the targetting of the (required) portion of the label specifically.

Appreciated,
Cheers

maybe can help us this post:

Making WordPress SEO plugin compatible with BuddyPress

i stil have to read it, but i hope this is the right track.

Thanks again

I opened a ticket at https://buddypress.trac.wordpress.org/ticket/6573

Per @hnla “It’s due to recent changes to how media is handled in BP activity streams, the problem is the removal of image attr such as class tokens and the image name references the WP image size.”

For some reason, I’m not able to comment on the ticket.

Does anyone have any idea how to fix this? Is it going to be fixed on an upgrade?

@djsteveb

– I disabled buddypress-social-icons & mycred
But it is still not working. Debug Log still shows this:
(happening on a desktop computer). I checked: the media that was attached ends up in the media library, but why is it not showing in the activity feed ?

[03-Aug-2015 21:40:49 UTC] PHP Notice: bp_core_get_notifications_for_user is deprecated since version 1.9! Use bp_notifications_get_notifications_for_user() instead. in /homepages/26/d553229553/htdocs/clickandbuilds/kawaii/wp-includes/functions.php on line 3391
[03-Aug-2015 21:40:50 UTC] PHP Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /homepages/26/d553229553/htdocs/clickandbuilds/kawaii/wp-includes/functions.php on line 3560
[03-Aug-2015 21:40:51 UTC] PHP Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /homepages/26/d553229553/htdocs/clickandbuilds/kawaii/wp-includes/functions.php on line 3560

So when I view the Activity in the backend I see an error:

Warning: usort() expects parameter 1 to be array, string given in **********/wp-content/plugins/buddypress/bp-activity/bp-activity-akismet.php on line 652

Should I disable Akismet?

The links are enclosed in single quotes e.g. <a href=’http

If I change it to <a href=”http

then the problem is sorted. But new activity still has the links in single quotes.

I am using the latest wordpress and buddypress- with kleo from seventhqueen

This is my current code:

<?php

/* Link parent CSS file */
add_action( 'wp_enqueue_scripts', 'enqueue_parent_styles' );
function enqueue_parent_styles() {
    wp_enqueue_style( 'parent-style', get_template_directory_uri().'/style.css' );
}

/* Count number of user notifications */
function cg_current_user_notification_count() {
    $notifications = bp_core_get_notifications_for_user(bp_loggedin_user_id(), 'object');
    $count = !empty($notifications) ? count($notifications) : 0;
 
    echo $count;
}

/* Remove register BuddyPress Widget creator */
function remove_bp_core_register_widgets() {
    remove_action(bp_core_register_widgets());
}
add_action('init','remove_bp_core_register_widgets()');

function new_bp_core_register_widgets() {
	add_action('widgets_init', create_function('', 'return register_widget("new_BP_Core_Login_Widget");') );
}
add_action( 'bp_register_widgets', 'bp_core_register_widgets' );

/* New BuddyPress Login Widget */
class new_BP_Core_Login_Widget extends WP_Widget {

	/**
	 * Constructor method.
	 */
	public function __construct() {
		parent::__construct(
			false,
			_x( '(BuddyPress) Log In', 'Title of the login widget', 'buddypress' ),
			array(
				'description' => __( 'Show a Log In form to logged-out visitors, and a Log Out link to those who are logged in.', 'buddypress' ),
				'classname' => 'widget_bp_core_login_widget buddypress widget',
			)
		);
	}

	/**
	 * Display the login widget.
	 *
	 * @see WP_Widget::widget() for description of parameters.
	 *
	 * @param array $args Widget arguments.
	 * @param array $instance Widget settings, as saved by the user.
	 */
	public function widget( $args, $instance ) {
		$title = isset( $instance['title'] ) ? $instance['title'] : '';

		/**
		 * Filters the title of the Login widget.
		 *
		 * @since BuddyPress (1.9.0)
		 * @since BuddyPress (2.3.0) Added 'instance' and 'id_base' to arguments passed to filter.
		 *
		 * @param string $title    The widget title.
		 * @param array  $instance The settings for the particular instance of the widget.
		 * @param string $id_base  Root ID for all widgets of this type.
		 */
		$title = apply_filters( 'widget_title', $title, $instance, $this->id_base );

		echo $args['before_widget'];

		echo $args['before_title'] . esc_html( $title ) . $args['after_title']; ?>

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

			<?php

 		 	/**
		 	 * Fires before the display of widget content if logged in.
		 	 *
		 	 * @since BuddyPress (1.9.0)
		 	 */
			do_action( 'bp_before_login_widget_loggedin' ); ?>

			<div class="bp-login-widget-user-avatar">
				<a href="<?php echo bp_loggedin_user_domain(); ?>">
					<?php bp_loggedin_user_avatar( 'type=thumb&width=50&height=50' ); ?>
				</a>
			</div>

			<div class="bp-login-widget-user-links">
				<div class="bp-login-widget-user-link"><?php echo bp_core_get_userlink( bp_loggedin_user_id() ); ?></div>
				<p>TEST</p>
				<div class="bp-login-widget-user-logout"><a class="logout" href="<?php echo wp_logout_url( bp_get_requested_url() ); ?>"><?php _e( 'Log Out', 'buddypress' ); ?></a></div>
			</div>

			<?php

			/**
		 	 * Fires after the display of widget content if logged in.
		 	 *
		 	 * @since BuddyPress (1.9.0)
		 	 */
			do_action( 'bp_after_login_widget_loggedin' ); ?>

		<?php else : ?>

			<?php

			/**
		 	 * Fires before the display of widget content if logged out.
		 	 *
		 	 * @since BuddyPress (1.9.0)
		 	 */
			do_action( 'bp_before_login_widget_loggedout' ); ?>

			<form name="bp-login-form" id="bp-login-widget-form" class="standard-form" action="<?php echo esc_url( site_url( 'wp-login.php', 'login_post' ) ); ?>" method="post">
				<label for="bp-login-widget-user-login"><?php _e( 'Username', 'buddypress' ); ?></label>
				<input type="text" name="log" id="bp-login-widget-user-login" class="input" value="" />

				<label for="bp-login-widget-user-pass"><?php _e( 'Password', 'buddypress' ); ?></label>
				<input type="password" name="pwd" id="bp-login-widget-user-pass" class="input" value="" <?php bp_form_field_attributes( 'password' ) ?> />

				<div class="forgetmenot"><label><input name="rememberme" type="checkbox" id="bp-login-widget-rememberme" value="forever" /> <?php _e( 'Remember Me', 'buddypress' ); ?></label></div>

				<input type="submit" name="wp-submit" id="bp-login-widget-submit" value="<?php esc_attr_e( 'Log In', 'buddypress' ); ?>" />

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

					<span class="bp-login-widget-register-link"><?php printf( __( '<a href="%s" title="Register for a new account">Register</a>', 'buddypress' ), bp_get_signup_page() ); ?></span>

				<?php endif; ?>

			</form>

			<?php

			/**
		 	 * Fires after the display of widget content if logged out.
		 	 *
		 	 * @since BuddyPress (1.9.0)
		 	 */
			do_action( 'bp_after_login_widget_loggedout' ); ?>

		<?php endif;

		echo $args['after_widget'];
	}

	/**
	 * Update the login widget options.
	 *
	 * @param array $new_instance The new instance options.
	 * @param array $old_instance The old instance options.
	 * @return array $instance The parsed options to be saved.
	 */
	public function update( $new_instance, $old_instance ) {
		$instance             = $old_instance;
		$instance['title']    = isset( $new_instance['title'] ) ? strip_tags( $new_instance['title'] ) : '';

		return $instance;
	}

	/**
	 * Output the login widget options form.
	 *
	 * @param $instance Settings for this widget.
	 */
	public function form( $instance = array() ) {

		$settings = wp_parse_args( $instance, array(
			'title' => '',
		) ); ?>

		<p>
			<label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title:', 'buddypress' ); ?>
			<input class="widefat" id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" type="text" value="<?php echo esc_attr( $settings['title'] ); ?>" /></label>
		</p>

		<?php
	}
}

?>

I was trying to following the below guide to remove the function that initializes the login widget and then redirect it to my own new one:

http://venutip.com/content/right-way-override-theme-functions

Obviously hasn’t worked. Any ideas ?

The other CMS is bespoke, so I know that it won’t be just plug and go.

Automatically signing up makes sense… although I thought that I had seen somewhere in the forums that using an API to sign new members up was “a bad thing”. But I can’t remember why!

Can you point me to where I should be adding a the member (in the code) – I am assuming that I need to create the member / user in WordPress, and allow BuddyPress to use that authentication. Or should I be adding the user in BuddyPress? As you can tell, I haven’t downloaded it yet, until I check if I can use it.