BuddyPress.org

@ubernaut did you apply the fix https://buddypress.trac.wordpress.org/changeset/6679 ?
Let me know and I can help test in your site.

Ok I’ve found a working solution using WP 3.5, bp 1.6.2 and bp-moderation 0.1.6 … I have my flagging and unflagging with backend reports working perfect now.

Here is how I did it so you can fix yours:

Step 1.
Follow these steps to update some plugin code since the plugin is now unsupported.
https://wordpress.org/support/topic/plugin-buddypress-moderation-not-working-with-bp-161-wp-342?replies=9#post-3267296

Step 2.
Step 1 only allowed me to flag and unflag content with the super admin account only. If you have the same problem then open bpModLoader.php and comment the lines 64-66.

Change to following or delete to fix all users can flag posts.

// if (!is_super_admin()) {
// return;
// }

Hope this helps 😀

Cheers

I get this same issue but with blog posts. Every time I edit an old blog post from WordPress it shows up in my activity stream as a new post, not sure if many have experience it since the only way to know is if these posts are getting updated. But in my case, i have to be updating posts all the time and I believe this shouldn’t be happening. Is there a way to stop this?

@akumaseijin you have to find the theme_location of your secondary custom menu. For example, in the Twenty Ten theme, the theme_location is ‘primary’ see https://codex.wordpress.org/Function_Reference/wp_nav_menu#Used_in_the_Twenty_Ten_theme

After you find the theme_location of your secondary menu, replace mamamia in what I posted at http://pastebin.com/jFLsdDJG

There are a number of plugins in the WP plugin repo which could change what shows up in the admin toolbar. For BP-specific nav links, check out https://wordpress.org/extend/plugins/buddypress-custom-profile-menu/

@ubernaut just tested Windows7 and Safari and same behavior applies with the latest WP/BP versions. Please do the honor of posting trac ticket for this issue.

EDIT – DOING_AJAX https://buddypress.trac.wordpress.org/ticket/4736

Email should work but much can go wrong including things connected to plugins, themes and functions.php or bp-custom.php files.

Presuming the email didn’t go into spam, and WordPress sent emails before installing BuddyPress, then one thing that can be tried is disabling all plugins except except buddypress and the ( un-customised ) bp-default theme.

If this is a localhost/dev site then php / server has to be correctly configured and/or upgraded for email. Alternatively WP Mail SMTP may be useful in this situation…

The main email address is set on the wordpress Settings > General page.

There may be other issues with buddypress in some situations. For more info see: https://buddypress.trac.wordpress.org/ticket/4689 and relevant links on that page.

Sure it is. https://codex.wordpress.org/Function_Reference/is_user_logged_in

@doncgarner as of the version I helped with, yes, you would have to add all that code to the BP template files. It all depends on the theme. Open up your theme’s page.php and you’ll see the amount of code added by the theme author to give you all the options added to the theme. Other WP themes required only 2 files for BP compatibility or just less code.

You could wait for BP 1.7 coming up https://buddypress.trac.wordpress.org/roadmap sometime next year where you do not need to change anything in your template files at all (unless you want to totally customize the BP pages further).

hi,

trying to built your own component ? See https://wordpress.org/extend/plugins/buddypress-skeleton-component/

Hi,

sorry to ask that, but why don’t you use the built in BP widget Who’s online ?
for inspiration, see how it is built in bp-core-widget.php:124
You can also use bp-skeleton to built your own widget on a proper maner.
https://wordpress.org/extend/plugins/buddypress-skeleton-component/

Did WordPress send emails before you installed buddypress?

According to trac https://buddypress.trac.wordpress.org/roadmap we are only about 5 weeks away.

hi @michael4fm,

read here: http://alex.leonard.ie/2012/05/24/wordpress-admin-area-favicon/

Sorry @mercime (and, yes, I’ve already read through the ticket in trac, along with the documentation, etc.), but Administrator elevated Moderators from within a community definitely do not belong in there messing around with Group naming structures and descriptions. They are there to merely moderate the internal content and behavior within the Groups/Forums themselves (like I need to tell you that, being that you are yourself a Moderator here on BuddyPress – and a hell of a good one at that if you don’t mind me saying so!), and that’s it.

With this proposed change, will newly elevated Group Moderators then also be able to delete and/or upload Group avatars once given these new permissions, or even change the Groups privacy settings at will? Not a good “fix” at all if you ask me, no matter what the existing documentation and so forth has to say about it.

I believe that the real error here occurred at some point in time within the direction of the documentation if anywhere, and that is actually what needs to be fixed here, and not with keeping on going down a road where the sign with the arrow pointing one on where to safely go somehow got turned around at some point and is actually now pointing off over the cliff, right?

Hugo ( @hnla) has it absolutely right here with his take on this proposed change within the trac ticket located at https://buddypress.trac.wordpress.org/ticket/4737

If you look at our own Group structure within our currently-being-developed site at https://PhysicalActivity.com (which I’d personally registered all the way back in December 1999) you’ll see that we’ve got over 200 meticulously generated Groups, and with thousands more to come, that we definitely do not want members who have been elevated to Moderators digging in and messing around with when it comes to Group names and descriptions, among other things, and I’m guessing a lot of other folks (site Administrators) would feel the exact same way about it as well. Isn’t it enough that Moderators can already pretty much clear out the entire contents of a Group/Forum?

We do not allow our members to create their own Groups, and that is definitely by design. It would certainly create havoc and chaos if we then, eventually, had 100’s of Moderators running wild within our set Group naming structures, descriptions and so forth, especially with thousands upon thousands of Groups to have to keep track of in the future.

When we’re done here, we’re definitely going to be one of the bigger sites making use of the WordPress/Multisite/BuddyPress platform so, needless to say, and like a lot of other folks here too, we’ve got a lot of time, effort and money invested in helping to properly see this whole thing (the ultimate development and direction of BuddyPress) through as well, even if our contributions and/or opinions are just brushed to the side at times.

We’ll definitely be stripping this update out of the code when (if) it drops with, what looks to be from @djpaul, 1.6.3 in the next several days or so here.

If anything, this sounds more like an options type of thing (“Allow Moderators to Change Group Name and Description” – “Do Not Allow Moderators to Change Group Name and Description”), or even plugin territory for the few people who would actually get good use out of something as reckless as this.

All of you guys and gals working on BuddyPress with your time, efforts and skills are absolutely fabulous (and I know, because I’ve been working with and dabbling in BuddyPress since its inception when Andy Peatling was still running the show, and I’ve been working with WordPress since its beginnings as well, even going so far as to register domain names like WordBlog.com, CustomerBlog.com, NoteBlog.com and so forth to use in conjunction with it way back in 2003/2004), so please don’t take this as anything more than me just tossing a little dirt (with a pinch of love) into the gears in the hopes of getting people to stop and take a second, or even third, look into a quick and hastily made change that just shouldn’t be made in the first place.

You know what they say about fixing something that isn’t broken…

Thanks for lending an ear or two to me here. Keep up the good work!

Best regards,

Kyle

@doncgarner as Hugo mentioned above, we have a list of walkthroughs aka “template-packed” WordPress in the Codex. Here’s the link for the Continuum theme before http://wp.me/p1I84P-36

hi curious about your situation @themightymo i also have been experiencing a rather odd bug of my own since we switched to wp engine:

https://buddypress.org/support/topic/my-join-group-button-is-acting-funny/

i have found them to be very knowledgable over there and the service itself seems to be beyond comparison for wordpress hosting.

This link offers an alternate solution: http://wordpress.stackexchange.com/questions/35163/add-buddypress-profile-and-messages-link-to-wordpress-menu

You might also look into custom walkers for the WordPress menu.

Hiya @mercime,

From the network admin you’re correct it will go to wp-admin/network/site-new.php.

Easiest way to see the issue is to go to the “My Sites” link and click “Create new site” from there (assuming logged in users can create sites). This is how non-network admin’s would create a new site.

This link is borked (unless you’re using “blogs” as the slug for “Site Activity” possibly… haven’t tested that). Here’s the trac ticket with the fix (slated for 1.7):
https://buddypress.trac.wordpress.org/ticket/4632

Hope that clarifies. Thanks!