BuddyPress.org

Right place, but there’s lots of people with questions here and only so many answers and time to answer them.

I’m assuming that you’re using BP Default theme on a blog which is not the main blog on a WPMU install?

Right place, but there’s lots of people with questions here and only so many answers and time to answer them.

I’m assuming that you’re using BP Default theme on a blog which is not the main blog on a WPMU install?

Basically, check your register.php main loop and only show the groups you want to show.

You’re looking for the while loop after the bp_is_active( ‘xprofile’ ) call.

Within the loop, you can filter out groups by doing a simple if check using if (bp_the_profile_group() == "group number") where group number is the number of the group you want to show.

Similar sort of idea in this thread: https://buddypress.org/forums/topic/profile-fields-questions

Basically, check your register.php main loop and only show the groups you want to show.

You’re looking for the while loop after the bp_is_active( ‘xprofile’ ) call.

Within the loop, you can filter out groups by doing a simple if check using if (bp_the_profile_group() == "group number") where group number is the number of the group you want to show.

Similar sort of idea in this thread: https://buddypress.org/forums/topic/profile-fields-questions

I’m pretty new to Buddypress but thinking about implementing S2Member as well. It looks very good but one thing I’m trying to do is allow my premium members to display more information about themselves than free members.

I think I might be able to restrict free members from accessing a certain field group in their profile so that they just can’t submit the particular details such as Location and Occupation but that seems a little messy.

I’m trying to setup a directory based site for Alternative Therapists such as Reflexologists, Nutritional Therapists, Accupunctuists, Yoga Teachers, etc, etc. I’m doing it for a client and she really likes the idea of having a social network side to the site as well because the therapists will be interested in networking with eachother and their potential clients (free members) will also be able to find them and ask questions or just read what they have to say.

Unfortunately, however, because the search functionality in Buddypress seems quite limited not only is it difficult to narrow down a search for a particuar kind of therapist in a particular location, but it also doesn’t seem possible using S2Member to show only premium members.

I’m thinking I might either have to scrap the idea of using Buddypress or else integrate separate directory pages but if I do that it probably won’t be very easy to tie their details for each system together.

Sorry for the long post – but said it was best to explain it fully to see if anyone has any experience of trying to do something similar or has any good advice.

@DJPaul, oooh, that is a nice setup.

http://help.deanjrobinson.com/

cool, thanks! 2 more questions

1) how do you get to show a list of all the tracks that have been posted?? not the activity but just the tracks..can this be done?

2) any idea if i wanted it to pick up when i wrote a ‘#’ in the post form?? like i wrote #artist and it turns the #artist into a link for that artist..? like how the @ mention works…

Lots of questions to address, so I’ll do it in the order they were posed.

@stwc

On the BP install I’m currently working on, the following long list of plugins (all of which seem to be working flawlessly activated non-sitewide) do not even offer the option for Site-wide Activation.

Is there a reason (or reasons) for that? Is there any possible downside? Or are they fine the way they are?

These plugins should work fine whether or not they are activated sitewide. However, there are two reasons why a BP plugin should be tagged to activate sidewide automatically:

1. Because they are BuddyPress-dependent plugins and require BuddyPress to work. Since Buddypress operates sitewide, then all add-on plugins are sitewide-acting by implicit reference.
2. By virtue of the first point, only Site Admins should have access to any plugin configuration. Offering all members with blogs access to these BP-dependent plugins in their admin dashboard only creates confusion as these plugins are for BuddyPress only and not for WordPress blogs.

______________

@hnla

So for clarity if one adds ‘Site Wide Only: true’ to pluginin files main description then it forces site wide activation regardless of whether one chooses to activate normally non site wide

This is correct. When the Site Wide Only tag is set to true, it does not matter which activation link is clicked as either action will result in sitewide activation. In fact, for all BP plugins I test, I simply click the “Activate” link right under the plugin name and not the “Activate Site Wide” link. If the plugin then shows under the Site Wide listing of plugins, I move on. If it does not, then I know that the plugin author failed to set the tag properly.

Edit/ found a plugin that already had ‘Site Wide Only: true’ set yet does not activate site wide using the plain activate link placing it self in the site wide section unlike bp-links. Is there something else that must be set to enable the site wide activation link or the ability to force the plugin to activate site wide?

Not that I am aware. It might be that the plugin has two Site Wide Only tags and there is a conflict. To which plugin do you refer?

______________

@MrMaz

Still unsure if I should add this tag to my plugin header. Shouldn’t it be up to the site admin to decide how the plugin is activated?

See my response in this post to @stwc. Since your plugin requires BP to operate, there is no value in letting non-admin members have access to your plugin via their blog dashboard. The more you can do to make installation, activation, and operation of your plugin foolproof the better. Is there actual functionality that your plugin offers if activated non-sitewide? What features of your plugin even make non-sitewide activation a desirable option to Site Admins?

______________

@hnla

In an ideal world I would like BP installed much as is but described differently but along with BP are installed a series of modules that can be activated or not by admin but that these are only activated from within BP so to speak always sitewide as BP is these modules representing some essential core set of features

I agree completely. I always refer to BuddyPress as a plugin suite but that never sat quite right with me. BuddyPress is a feature-rich platform as far as I’m concerned. It transcends the idea of a simple WordPress plugin. I also agree that many of the BP “plugins” are best described as modules as well. In fact, I consistently refer to my privacy “plugin” as the BuddyPress Privacy Component to separate it from the idea of it being just another plugin.

I could see the possibility of BuddyPress modules having their own set of 3rd-party plugins. So BuddyPress > 3rd-party BP modules > 3rd-party module plugins.

I also like your idea of requiring that all BP-dependent “plugins” get activated within a BuddyPress dashboard–instead of outside of BP. That could take care of all activation conflicts.

In my version of an “ideal BP world”, BuddyPress would become the foundation of the WordPress ecosystem as it is a user-centric platform and not blog centric. WordPress then would be a layer that sits on top of BuddyPress and could be activated if desired. So, Site Admins would install BuddyPress and then could check a box to install WordPress (in single or multisite mode), bbPress, and other modules.

Now I’m taking this thread too far of topic.

Redirect to User’s Profile Page on Login

Place the following snippet in either wp-content/plugins/bp-custom.php or in your child theme’s functions.php file.

function oci_login_redirect($redirect_to, $set_for, $user){

$redirect_to = bp_core_get_userurl($user->id);

return $redirect_to;

}

add_filter('login_redirect', 'oci_login_redirect', 10, 3);

From https://buddypress.org/forums/topic/two-questions-about-the-login-process#post-8380

(alternate method)

Use Brajesh’s plugin (which does basically the same thing as above):

https://wordpress.org/extend/plugins/bp-redirect-to-profile/

Searching works but so does following tags.

https://buddypress.org/forums/topic/two-questions-about-the-login-process#post-8380

@gian-ava: For your second question, check out this post https://buddypress.org/forums/topic/faq-how-to-code-snippets-and-solutions#post-13243

I haven’t tried this but it would suggest you could do something like:

<?php if ( bp_has_profile('profile_group_id=9') || bp_has_profile('profile_group_id=7') ) : ?>

<?php while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

<div id="widget1">

<?php if (bp_the_profile_group() == "9") : ?>

// Do whatever you want with group 9

<?php endif; ?>

<?php if (bp_the_profile_group() == "7") : ?>

// Do whatever you want with group 7

<?php endif; ?>

</div>

<? endwhile; ?>

<?php endif; ?>

The only part I’m not sure about is if you need the first call to bp_the_profile_group() on the second line (after the start of the while loop).