BuddyPress.org

Is there anyone on this thread that can provide the specific css or javascript that I can copy and paste into my child theme to resolve this issue with Load More until a plugin update is provided?

I understand that updates can be followed at the link provided but I need help translating that activity/conversation (I am not a developer). Gratitude in advance for anyone that can help me take the next step.

@sjregan, @vapvarun. Thank you so much guys. My site had the issue for a while, but upon updating my Kleo theme to 4.3.8, the issue was resolved.

However, Kleo 4.3.8 at the moment doesn’t work with Buddypress Nouveau Template Pack, just Legacy Template Pack. So, users may find out that the Kleo reverts your Nouveau selection to Legacy.

Do you still get the errors with all other plugins deactivated and running the 2017 theme?

That’s right, to overload them copy them into your themes/child-theme/buddypress directory, maintaining the directory structure and you will be able to edit at your leishure.

BP has a large number of files that can be overloaded by copying them to your child-theme directory, these are located in plugins/buddypress/bp-nouveau (or bp-legacy) /buddypress for one off builds it’s usually easiest to overload the template file you require. If the solution needs to be re-useable then it’s better to build a plugin and use filter and action hooks. Also some things you can’t do with Template files alone.

I have a correction to make with my post: I did not replicate this issue with Nouveau; my site is using Legacy template and experiencing these problems with Load More.

For reference to other BuddyBoss Boss theme users: BuddyBoss has confirmed that they are overriding the BuddyPress settings to only run Legacy and have no timeline for supporting Nouveau template on their Boss themes. Even if you have Nouveau selected in your BuddyPress settings, it will default to Legacy. This caused my assumption that I was using Nouveau (since I had it selected).

@r-a-y is there an updated javascript patch by this point? This problem persists (on multiple devices including mobile) and an update would be very helpful. Thanks.

Which theme are you using? I don’t see an RSS feed in my group homepages. RSS is a form of XML, what I find is that some browsers will interpret it correctly and others don’t. Does it not display correctly in a feed widget or ?

I’ve just copied activity-loop into the theme/buddypress/activity directory and the overload works for me.

Yep switching theme should not affect it, and it’s only this one call that it’s doing it on. One thing you could try, is calling the master function direct – bp_core_get_active_member_count() just to see if that behaves any differently. If that does not shed light then it’s down to the workings of the core function, something is different about how it’s applying the excludes list.

First step is to switch theme to 2017 or another default theme and deactivate your other plugins to rule out conflicts.

You could probably do it by overloading your theme, just find the place where it’s adding the post_author link and overload that using a child theme.

The file in question is usually themes/yourtheme/single.php somewhere it will probably be calling get_author_posts_url($author_id) which points to the WP author page, you’d replace that with bp_core_get_user_domain( $author_id ).

That’s the general gist if what you need to do, but it might get complicated depending on your theme.

Ah so it’s includes/members/functions.php you need to look at, line 50 is calling bp_get_total_member_count(), it’s called by the legacy theme also so there’s a thing – the same function returning two different numbers depending on the theme, and only on one site.

That looks like a theme issue to me, it looks like it’s applying the comments to the wrong page.

Could you try with the Graphene theme? It’s not a default theme but it’s the one I’ve been using and I know it loads the file.

And if you deactivate any other plugins and switch to the 2017 theme, does the problem remain?

It works fine of my test system, have you ruled out plugin and theme conflicts?

Have you ruled out plugin and theme conflicts?

The p’s are a bug, being fixed.

You should however be able to see the next step button, if it’s missing you will probably need to rule out plugin and or theme conflicts