Hi there
When I’m on the Groups page it defaults to show groups, but I would like it to default show “My Groups” as I use hidden groups a lot and if a user logs in it might look like there are no groups to them and it’s not obvious to click the My Groups Tab.
If anyone has a good solution that does not involve hacking into the BuddyPress plugin but can be done with a function or plugin that would be great 🙂
Thanks
Hi,
I am running buddypress plugin on wordpress 3.8.1 and using Windows hosting for http://haflongbosconians.org/ . While the front pages are working fine, the buddypress pages are showing a 404 error.
I found this solution for APACHE http://www.youtube.com/watch?v=m9zESEfNzSQ . What can I do for Windows hosting?
Appreciate your help.
Regards.
Soumya
> the hobbled together mess
Just to push back a little on this one. There are a couple of key ways in which BP’s current permalink router is not ideal (it’s not amenable to caching; it’s not non-pretty-permalink friendly; it’s hard to write unit tests for it; it leaves some slugs difficult to change). Moving toward the WP Rewrite API is a worthwhile project, because improving on these areas are worthwhile things to do.
However, it’s important not to overstate the problem. The current system works just fine for many thousands of BuddyPress sites. While there would be new efficiencies and configuration possibilities with a new system, it’s unlikely that their absence to date has ever been a dealbreaker for any BuddyPress site. @synaptic or others, I may be wrong about this, and if there are specific ways that the current router is holding you back, it would be very helpful to know more about those details.
In any case, while it will require a large amount of work to build a new system that’s compatible with the old, it’s not doing any active harm to existing (or new) sites to use the current (perfectly functional) system. So let’s not get too carried away with the idea of forking our own project 🙂
On sign-up to my website, users are asked there account type in a custom profile field (Type of account).
At the top of every buddypress page in the h1 title area the users name appears. I am looking for a way to place the profile field “Type of account” beside the username in the page title?
I have been looking into this for a couple of weeks without any luck as my coding skills are just not up to the challenge,
any help would be very much appreciated as it is one of the last things i need to do before i can launch my website,
Thanks guys and gals!
This is what I did, ignoring the bit above:
The function bp_displayed_user_mentionname is declared in /plugins/buddypress/bp-activity/bp-activity-template.php:1027
As this function is a filter, we can simply remove it to remove the @username from the template. But because the hardcoded @ sign before the username, we have to add a CSS rule with the remove_filter function. The function above will do all that.
Add these snippet to your bp-custom.php (read here if you don’t know this file)
/* remove @username from the profile header */
function bpfr_remove_mention_from_profile() {
echo ‘<style> h2.user-nicename { display:none; } </style>’; // hide the h2 containing the @
if( bp_is_user() && ! bp_get_member_user_id() ) { // be sure we get the right user_id
$user_id = ‘displayed: ‘. bp_displayed_user_id();
} else {
$user_id = ‘get_member_user: ‘. bp_get_member_user_id();
}
remove_filter( ‘bp_get_displayed_user_mentionname’, bp_activity_get_user_mentionname( bp_displayed_user_id() ) );
}
add_filter( ‘bp_get_displayed_user_mentionname’, ‘bpfr_remove_mention_from_profile’ );
I would totally not recommend to disable it. You should spend more time to figure the problem out. In my BuddyPress test installations (local and live), it sends the emails just fine, so there is a problem, maybe in your server, template, I don’t know, somewhere.
But, if you really wanna disable this, after a quick search here and in Google, I found some possible solutions.
Obs.: I haven’t tested it, so use it at your own risk.
https://buddypress.trac.wordpress.org/ticket/3443
https://buddypress.org/support/topic/i-would-like-to-disable-email-activation/#post-43483
I am having this exact issue. I am a developer and I know how to run through the steps mentioned here..
What I have tried is to find a user that is stuck in not being activated and running putting this on one of my pages:
<?php $user = get_userdatabylogin('busaany'); echo $user->ID; echo get_user_meta( $user->id , 'activation_key', true );
?>
This yeilded an activation key:
2429b4ee92830f6557b5b5be271b5078defe
So I tried to plug that into the activation key url as such:
http://bounty.co.nz/activate-account/?key=2429b4ee92830f6557b5b5be271b5078defe
This brought me to the invalid key page as mentioned by others… This is a major issue and I am getting all sorts of stress/grief from my client. I am 100% committed to fixing this issue myself if that is what has to be done. But I was hoping that my putting this here could give the buddy press devs some more info on what is going on. This use HAS signed up, this use HAS tried to go to this link and it failed first time.
I have used a plugin called buddypress pending activations to try and remedy this and trouble shoot it. It allows me to figure out who is being caught and it is a non-trivial amount of users. The user remains in the pending regardless of visiting that link or entering the code into the box on the page…
Any leads? I will be getting this locally set up and try and debug buddypress as I am certain this is buddypress thing now not a server issue. But if you can get me any help or direction that would be great. If I can fix this I will let you guys know and we can get this resolved in the core.
Regards,
Justsayno1
I am managing a few different school-related websites at http://sites.unishanoi.org. One of them is a site called Tech Connect that is at http://tech.unishanoi.org. I was able to install Buddypress on that particular sub-site. Thanks to @aces for your help with that – I defined
define ( ‘BP_ROOT_BLOG’, $blog_id );
to the subsite blog number.
However, now I have a new problem – lots of redirect loops. Whenever I go to my main network dashboard, Settings>Buddypress>Pages, all of the pages there give me redirect loop errors. I’ve managed to get around it a little bit by using plugins rather than the actual Buddypress pages, but this seems like a bad solution in the long term. I’m also using the Domain Mapping plugin, so that my site at http://sites.unishanoi.org/tech redirect to http://tech.unishanoi.org.
Any help I could get with this would be greatly appreciated!
Aces – thanks for your help on this. Now I have a new problem, though – lots of redirect loops.
Whenever I go to my main network dashboard, Settings>Buddypress>Pages, all of the pages there give me redirect loop errors. I’ve managed to get around it a little bit by using plugins rather than the actual Buddypress pages, but this seems like a bad solution in the long term. I’m also using the Domain Mapping plugin, so that my site at http://sites.unishanoi.org/tech redirect to http://tech.unishanoi.org.
Any help I could get with this would be greatly appreciated!
I just watched this short clip of JJJ on wordpress.tv talking about the permalinks issue:
that the developers are facing for both bbPress (http://bbpress.org/forums/topic/any-way-to-eliminate-redundancyweirdness-in-permalinks-i-e-forumsforum) and BuddyPress. As JJJ explains, a mistake early on in the dev has ‘painted them in a corner’ and now the way out is complicated because as they try to fix this, they have to consider how that fix will affect the many already existing buddypress sites out there.
I totally understand their care and concern about existing sites and the conflicts that may occur if a solution is not implemented correctly.
But what seems to be missing is an equal amount of concern for those people who have yet to deploy a BuddyPress or bbPress and are only given a choice of using what is currently available (the hobbled together mess). Since the relevant ticket has been officially opened on trac, this group has been waiting for a long time with no foreseeable solution on the horizon.
So I’d like to suggest a potential third way out of this:
Put out a version of buddypress that does not concern itself with backward compatibility for those who do not have an existing install (so it is NOT an upgrade) but who want to do fresh installs and create new websites and communities.
Pushing out a solution for them would be much simpler because you would not need to accommodate all manners of backwards compatibility isses. And this ticket of going on 12 months would be closed (sort of):
https://buddypress.trac.wordpress.org/ticket/4954
And for those who are on the upgrade path, the devs can continue to work on a fix that would accomodate them.
This approach would allow for both camps to be happy. In contrast, what’s happening now is that the already deployed buddypresses out there are in effect hampering this feature for those who have not yet deployed buddypress and are going to in the future (fresh new communities).
I hope my idea was expressed clearly. If not, let me know and I’ll see if I can give it another crack.
Does that make sense? what do you think?
BuddyPress doesn’t have an API, what are you using to get json?
Hello,
I want to extend buddypress favorite function:
Particularly I want to check if user is author of that post before favoriting an activity and if so dont allow favoriting. In other words I want to disable favoriting on own post, but doing this on server side and not just hiding button.
Well, I can rewrite this function with my own.
function bp_legacy_theme_mark_activity_favorite() {
// Bail if not a POST action
if ( 'POST' !== strtoupper( $_SERVER['REQUEST_METHOD'] ) )
return;
if ( bp_activity_add_user_favorite( $_POST['id'] ) )
_e( 'Remove Favorite', 'buddypress' );
else
_e( 'Favorite', 'buddypress' );
exit;
}
But here rises question: can some smart user override my function and post request to the original ajax? In devTools I could change scripts “action” to original one action: 'activity_mark_' + type, and sent with that action so user will still be able “favorite its own activity”
well, one thing I would do, is remove filters that are responsible for marking activity favorite, but is there any other thing/security you can think of?
@tietoep the Group Forums I am speaking of *are* bbPress, as chosen by the BuddyPress Group in the Group’s settings. I explained this quite clearly in the first post 😉
Upon further review buddypress is actually causing this same thing to happen to all my theme options. (using Atahualpa)
I don’t know what exactly it is. I just know if the buddypress plugin is enabled, nav-menu.php doesn’t work. I have to turn off buddypress so I can edit my menu, then enable it again.
I have not, I installed 1.9.2, thru the plugin installer inside WordPress. Might that newer version help then?
What exactly in BuddyPress is the problem? Have you tried the 2.0 beta?
BuddyPress 2.0 Beta 1 is now available
Howdy all
I am getting an internal server error when trying to access WordPress’ nav-menu.php (to create custom menus).
I have narrowed the problem down to the buddypress plugin causing it. How do we fix this?
Anonymous User 5853594Inactive
@halo-diehard
The Group Forums component in BuddyPress has been retired and it is indeed advised to use bbPress (version 2.x).
Fixed it, seems like BuddyPress had a conflict with me turning ?s= into /search/.
Anyone got an idea how I can make this work?
Hello, I want the administrator of a buddypress site to be friends with all users on the buddypress site. I don’t really want to go through every single user on the site and manually friend request everyone because that will take a LONG time.
Is there any way to just have the administrator be friends with all users in bulk?
THanks!
Hi Mike,
I don’t think that you can entirely remove the xProfile name field from BuddyPress (Even with the plugin that is available). So I decided why fight it? I cloned the WP username. The only potential problem with this is that the WP username is public – I used a plugin to force stronger WP username and passwords to help with this.
Here is the base of what I did:
– On the registration form hide the xProfile name field (CSS display: none) and make a javascript listener (CHANGE) function to change the xProfile name field to the value of the WP username. This will take care of the form validation – xProfile name field is required. See reference…
– For the edit your profile section I hide the xProfile name field, I also included a PHP function that made the value of this equal to the WP username, in the state that a user was added from the dashboard. (I did not provide PHP, I essentially grabbed WP logged in username…) – You can also display the xProfile name field input as readonly (add attribute: readonly).
Now all xProfile name field instances in BP are the same as the WP user.
Reference:
jQuery(‘input#signup_username’).change(function () {
jQuery(‘input#field_1’).val(jQuery(this).val());
});
Hi @metalmick
@username on the profile header is displayed with this code in BP 1.9.2
(see bp-themes/bp-default/members/single/members-header.php:28)
if ( bp_is_active( 'activity' ) && bp_activity_do_mentions() ) : ?>
<span class="user-nicename">@<?php bp_displayed_user_mentionname(); ?></span>
endif;
The @ sign is hardcoded in the span, so you have to remove it manualy from the file.
To do this, you can hide it with a CSS rule or you can remove the whole if statement if you use member-header.php file within a child theme/theme.
A more elegant solution would be to do this with a function, so we haven’t to think about theme modification or to forgot a CSS rule or to check BP after each update.
The function bp_displayed_user_mentionname is declared in /plugins/buddypress/bp-activity/bp-activity-template.php:1027
As this function is a filter, we can simply remove it to remove the @username from the template. But because the hardcoded @ sign before the username, we have to add a CSS rule with the remove_filter function. The function above will do all that.
Add these snippet to your bp-custom.php (read here if you don’t know this file)
/* remove @username from the profile header */
function bpfr_remove_mention_from_profile() {
echo '<style> h2.user-nicename { display:none; } </style>'; // hide the h2 containing the @
if( bp_is_user() && ! bp_get_member_user_id() ) { // be sure we get the right user_id
$user_id = 'displayed: '. bp_displayed_user_id();
} else {
$user_id = 'get_member_user: '. bp_get_member_user_id();
}
remove_filter( 'bp_get_displayed_user_mentionname', bp_activity_get_user_mentionname( bp_displayed_user_id() ) );
}
add_filter( 'bp_get_displayed_user_mentionname', 'bpfr_remove_mention_from_profile' );
Succesfully tested on BP 1.9.2 and 2.0 beta 1
Great Scott!
These time issues crop up every blue moon, so any insight you can provide into the following time settings would be awesome:
- Your physical timezone
- The timezone setting of your server(s)
- The timezone setting of your PHP configuration
- The timezone setting of your WordPress installation
Seems somewhere down the line, there’s a problem with our calculations in a certain configuration. It could be the math, could be daylight savings time, could be a WordPress bug, a BuddyPress bug, or a rip in the space-time continuum!
Hi,
I have this probem:
When i try to do this json request http://koora.altervista.org/members/?json=get_page/COOCKIE-OF-THE-USER
The response of my web-site is: {"status":"ok","page":{"id":25,"type":"page","slug":"members","url":"http:\/\/koora.altervista.org\/members\/","status":"publish","title":"Members","title_plain":"Members","content":"","excerpt":"","date":"2014-02-17 18:11:44","modified":"2014-02-17 18:11:44","categories":[],"tags":[],"author":{"id":1,"slug":"koora","name":"koora","first_name":"","last_name":"","nickname":"koora","url":"","description":""},"comments":[],"attachments":[],"comment_count":0,"comment_status":"closed","custom_fields":{}}}
I don’t understand why it don’t display me the list of all users registered.
Any idea??