BuddyPress.org

That sounds like a better approach than mine. I just have a rather crude looking button which marks as read all unread notifications.

bp_notifications_mark_notifications_by_type is the function I’m using to do the marking. For example:

if ( bp_is_active( 'notifications' ) ) {
    bp_notifications_mark_notifications_by_type( bp_loggedin_user_id(), buddypress()->messages->id, 'new_message' );
    bp_notifications_mark_notifications_by_type( bp_loggedin_user_id(), buddypress()->activity->id, 'new_at_mention' );
}

Hi @neerajkumar2020

Ah right. So it’s this plugin you’re using:
https://wordpress.org/plugins/buddypress-group-email-subscription/

It’s very easy to update user meta in WordPress. See:
https://codex.wordpress.org/Function_Reference/update_user_meta

But the plugin uses the BP version of this function AND I see that there are conditions in place which govern when this particular meta value is updated.

Have you tried asking on the plugin’s support forum? That might be the best place to start as you’ll have people there far more familiar with the plugin’s code.

https://wordpress.org/support/plugin/buddypress-group-email-subscription

ass_digest_items isn’t a meta key BuddyPress uses (to my knowledge). Are you sure it doesn’t come from a plugin?

@offereins – Thanks for the post.

Grabbing $_GET['s'] is, of course, intended behavior. But not allowing overrides – that, I would interpret as a bug. You can see the behavior here: https://buddypress.trac.wordpress.org/browser/tags/1.9.2/bp-groups/bp-groups-template.php#L335

The proper fix is for us to sniff out querystrings *before* parsing the arguments passed to the function. That way, you can pass a null ‘search_terms’ parameter to bp_has_groups() to bypass our default behavior. Would you mind opening an enhancement ticket for this at https://buddypress.trac.wordpress.org?

For the time being, you can continue to do what you’re doing by manually setting/unsetting $_GET['s'], or you can filter the clause out of the SQL statement, both of which you’ve suggested above. The only other workaround that comes to mind is something like passing a space character ' ' as a search_terms param – though even that might miss groups with one-word names and descriptions.

For their own URL, this will happen automatically with BuddyPress. So to use your example, by default it would be: http://samplesite.com/members/tom-jones

These two membership plugins are both known to play well with BP:

Membership 2 Pro

Home

Responsive.. sounds cool. Yeah BuddyPress will adopt your theme just like any other plugin. So you can design the theme from scratch. BuddyPress has its own HTML content that it will inject into the page via the_content, so you can style it with that in mind. It has its own stylesheet that you can build around, or deregister if you wanna go all out with your custom styles.

I think it might have been the process of updating, rather than the update itself, as I’ve searched and found several similar posts. We rolled back to 1.9.1 and the issue persisted.

https://buddypress.org/support/topic/bad-link-to-profile-edit/ seems to have the same issue, and we’ve tried adjust the database as recommended by breakster, again with no luck. The OP from that post mentioned she was using BP 1.8

Just wasted $19 to find out that plugin only works on multisite with buddypress, not a single site with buddypress.

Ambiguous product description and lack of an easy refund mechanism makes me warn you off wpmudev.

@landwire I see! That explains it.

Is that something that can be taken to core developers and asked if we can enhance the filter functionality

You could always ask? Trac is the best place to do that: https://buddypress.trac.wordpress.org/

@cspowers try the following

//* Remove the entry meta in the entry header (requires HTML5 theme support)
remove_action( 'genesis_entry_header', 'genesis_post_info', 12 );

I too am working on getting rid of the wonky layout issues, it is taking some time. The genesis connect plugin for buddypress is misleading in that it has been recently updated, but is worthless for the latest version of the genesis framework with the latest version of buddypress.

Will keep you posted if I come across anything else as I work on this.

Did you follow the part titled “Advanced Optional Step: Removing the database tables”.

That is the key to your question. The settings are all stored in the database tables. BuddyPress does not have an option to purge the database settings upon deactivation. You have to manually delete the tables.

Be careful! You could screw up your whole site if you remove the wrong tables. Definitely back up your database before attempting any of that.

@iameverywhere

I have thought about this a lot as well. BuddyPress spam is SO obvious for a human to figure out. You can detect spammers with almost perfect accuracy in just a few seconds. They all do the same thing. They create an account, then post garbage links. If you have Groups enabled, they create groups full of links in the description. I don’t know of a plugin that will do this, but the best way to block BP spam I think would be to put users in moderation if they post links to groups or activity, just like the setting we have for blog post comments.

Hi guys !

Most of the publishing stuff is regulated from within WordPress settings.
And allowing blog and forums activity comments is a setting of BuddyPress.

If you don’t want your users writing notices (what’s new ?), the only thing that is published by buddyPress, you can remove the notice form from the template or add a conditionnal if/else for the allowed members…

@boblebad, FYI buddypress is not a forum software. The forum plugin is bbPress.

Yeah, I’m suffering the exact same issue.
Wordpress 3.8.1, Buddypress 1.9.2

At first I thought it was because of an update to my Simplepress plugin, but that doesn’t seem to be the issue.

I’d hazard a guess it appeared after the latest BP update.

That’s something i would like to know too.

I need to have free “members” that can’t interact with the forum and groups, it’s okay that they can read/view them, but not answer or create new topics – that’s only for paying members.

It is actually weird that this feature isn’t in BuddyPress out-of-the-box, most other forum software has it.

All the best
Carsten

https://buddypress.org/support/search/spam/
https://codex.wordpress.org/Hardening_WordPress