[@apeatling Keymaster 17 years, 5 months ago]

look in bp-messages.php for the send function.

[@apeatling Keymaster 17 years, 5 months ago]

Sounds like the plugin has not been updated for 1.0.

[@apeatling Keymaster 17 years, 5 months ago]

https://codex.buddypress.org/developer-docs/custom-buddypress-loops/

[@apeatling Keymaster 17 years, 5 months ago]

Check out the template loops, you can make a new widget using one of those loops, and set a “filter” value of “male” or “female”.

[@apeatling Keymaster 17 years, 6 months ago]

Already patched in the trunk, this will be updated in 1.0.1 very soon.

[@apeatling Keymaster 17 years, 6 months ago]

Codyb: Don’t install WPMU in a sub-directory, can you try installing in the root if possible?

[@apeatling Keymaster 17 years, 6 months ago]

Not tested, but this would probably do it (put it in a plugin and activate it or add it to your theme’s functions.php file):

<?php

function disable_name_change( $data ) {

if ( 1 == $data->field_id )

$data->field_id = false;



return $data;

}

add_action( 'xprofile_data_before_save', 'disable_name_change' );

?>

[@apeatling Keymaster 17 years, 6 months ago]

<?php echo xprofile_get_field_data( $field_name, $user_id ); ?>

[@apeatling Keymaster 17 years, 6 months ago]

Jfcarter: you should be able to enable deep integration by adding this to the very top of your bb-config.php file:

require_once( $_SERVER['DOCUMENT_ROOT'] . '/wp-blog-header.php' );

Assuming WordPress is installed in the root.

[@apeatling Keymaster 17 years, 6 months ago]

Make sure you have deep-integration set up inside your bbPress. Basically make sure WP is loaded.

You’ll need to add a call to the wp-footer action so the BuddyBar is loaded:

<?php wp_footer() ?>

Add that before the closing HTML tag in your bbPress template footer and the bar should show up.

You’ll also need to add a wp_head() call to inside the header of your template too, so that the CSS works:

<?php wp_head() ?>

[@apeatling Keymaster 17 years, 6 months ago]

@Svenl77 – Let me check this out, and I’ll let you know.

[@apeatling Keymaster 17 years, 6 months ago]

It looks like the options bar is showing up on the directory pages when it shouldn’t – most likely because I forgot to add a hide function. All the other pages are working fine. I will update this.

[@apeatling Keymaster 17 years, 6 months ago]

Closing this as the first post is now out of date.

[@apeatling Keymaster 17 years, 6 months ago]

I should change this, right now this is not in the groups functionality, but it will be in upcoming versions.

[@apeatling Keymaster 17 years, 6 months ago]

Friends > Requests

[@apeatling Keymaster 17 years, 6 months ago]

Connect URL should be the URL of the website, so for http://testbp.org it is simply that.

[@apeatling Keymaster 17 years, 6 months ago]

Is the user a member of the group already?

[@apeatling Keymaster 17 years, 6 months ago]

http://wpmudev.org/project/WPMU-Signup-Captcha

[@apeatling Keymaster 17 years, 6 months ago]

https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-user-blog-posts-loop-bp_has_posts/

Specifically look at the template tags for pagination and the ‘per_page’ parameter.

[@apeatling Keymaster 17 years, 6 months ago]

I’m closing this, lets start a fresh thread, this one dates back to RC1 months ago.

[@apeatling Keymaster 17 years, 6 months ago]

The home theme controls the front page, and any blog pages in the root blog. It’s essentially just a blog theme with a front page that is emtpy, ready for widgets. Everything else is controlled by the BuddyPress member theme.

[@apeatling Keymaster 17 years, 6 months ago]

You could easily do this with a plugin. Use the ‘messages_message_before_save’ action and check the sender_id’s signup date. If it’s less than X amount of time, reject the message.

[@apeatling Keymaster 17 years, 6 months ago]

Make sure you have re-selected the member theme in “BuddyPress > General Settings” and hit the save button, even if it is already selected.

[@apeatling Keymaster 17 years, 6 months ago]

The span is used to inject the actual time-since, as this is not stored in the database. If you remove the span it’s going to break the output (which is why you won’t find it in any template files).

Is there another way you can do this? There is a filter on the output if you know how to use WordPress filters.

[@apeatling Keymaster 17 years, 6 months ago]

It’s not really going to cause that many headaches – it’s not like the time is actually displaying – it’s the “time since”.

Your time zone is irrelevant – it’s still going to say “active 45 minutes ago”. The only bug would be that blog posts would state they were posted at the time of the server not the local time. I can’t call that one a blocker though, but it will be addressed.