BuddyPress.org

Hey,

thank you for the prompt reply!

1) we are using the BP Nouveau template
2) no errors in the inspector
3) no errors in the Network – AJAX – Response

I am including two screenshots of this:
https://www.dropbox.com/s/9242oirs5ja3efu/BP%20Member%20Directory%20Stuck%20Inspector.png?dl=0
https://www.dropbox.com/s/oshty829ab2jnn2/BP%20Member%20Directory%20Stuck%20Network%20AJAX%20Response.png?dl=0

As I did the upgrade to BuddyPress v7.0, I am fairly positive that was the one change that triggered the member directory getting “stuck” – and with it the Buddypress Widget, which we (used to) use prominently.

However, we did several upgrades all around WP 5.6 (we document everything). Here is an excerpt of our Change Log:

12 DEC 2020 – Saturday
☠ [08:40 UTC – @kerrie ] Filed a support request / bug inquiry here regarding the Buddypress membership / widget bug
☠ [07:45 UTC – @scaffiesadmin ] Replaced the Buddypress “Recently Online” widget with the GD “Currently Online” widget (much fewer displayed) on the newspaper, and added the “Find New Friends” widget, until the Buddypress widget has been fixed (member list does not update, it is a bigger issue than just the widget displaying it). Sadly, with Buddypress updates something goes wrong regularly – but it is usually fixed quickly.
11 DEC 2020 – Friday
☠ [12:30 UTC – @kerrie ] The Buddypress “Recently Online” widget on the newspaper seems to have stopped working. Must be connected to the v7.0 upgrade hours earlier (not that there is a choice to upgrade or not, really — security issues are also always fixed with those).
☠ [01:40 UTC – @kerrie ] Updated Advanced Editor Tools (previously TinyMCE Advanced) to v5.6.0
☠ [01:35 UTC – @kerrie ] Updated WordPress to v5.6 – ‘Simone’ … “Code is Poetry”
☠ [01:34 UTC – @kerrie ] Updated Autoptimize to v2.8.0
☠ [01:33 UTC – @kerrie ] Updated BP Better Messages (Premium) to v1.9.7.60 (no public change log) – “other bugfixes and improvements”
☠ [01:32 UTC – @kerrie ] Updated Buddypress to v7.0 – “a major BuddyPress feature release” .. named “Filippi“
☠ [01:31 UTC – @kerrie ] Updated EU Cookie Law to v3.1.6
☠ [01:30 UTC – @kerrie ] Updated GP Premium (GeneratePress theme plug-ins) to v1.12.3 (no public change log)
☠ [01:29 UTC – @kerrie ] Updated Jetpack to v9.2.1
☠ [01:28 UTC – @kerrie ] Updated MyCred (Points, Rewards, Gamification, Ranks, Badges & Loyalty) to v2.0
☠ [01:27 UTC – @kerrie ] Updated Newsletter to v7.0.0
☠ [01:26 UTC – @kerrie ] Updated Paid Memberships Pro – Gift Levels v0.3 (no public change log)
☠ [01:25 UTC – @kerrie ] Updated UpdraftPlus Premium to v2.16.42.24 (no public change log)
07 DEC 2020 – Monday
☠ [22:46 UTC – @scaffiesadmin ] Updated WP Maintenance Mode to v2.3.0
☠ [22:45 UTC – @scaffiesadmin ] Updated BP Better Messages (Premium) to v1.9.7.59 (no public change log) – PM Pro incompatibility fix (affected Scaffies)

THANK YOU FOR LOOKING INTO THIS!!
Kerrie

I’ve tested the described issue (Two friends User A & B, both subscribers, both having a group) with latest WordPress (5.6) and BuddyPress (7.0) and into the Twenty Twenty-One theme. I can’t reproduce your issue. If it was a BuddyPress issue, then it should be the case.

I advise you to try the above configuration on a testing site, you should see the issue won’t be there. Then activate your theme, check if the issue appeared, if so: the theme should fix it, then activate all the plugins you use on your site one by one making sure to test again the issue before activating a new plugin. As soon as you can reproduce the issue, you’ve found the problematic one.

Have you tried https://wordpress.org/plugins/bp-simple-private/

Hello,

after the upgrade to v7.0 the membership directory is “stuck” (no longer updates), and the Buddypress “Recently Online” widget no longer works (also stuck, frozen in last status).

Any idea what this may cause, and is this an already known issue (which will be fixed soon)?

We use the latest version of WordPress (5.6) andkeep all plug-ins up-to-date.

Thanks!
Kerrie
Volunteer Admin Team, Scaffies

Yes, LIKE is slow.
Mentions are handled differently as you can see; a css class is added to the content field.
So perhaps the id of the mentioned user could be added to the item_id or secondary_item_id field.
Then the query could just look for matching integers.
I suggest you open an enhancement ticket – and reference this thread.

The plugin shanebp linked does normal wordpress pages, if you read the instructions it adds an option to each page/post so you can select whether it is private or not. Also did you ask the creators of “Restrict User Access – Membership Plugin with Force” about blocking groups etc as it says BP is supported.

Have you tried this plugin?

BP Simple Private

Hi,

Which buttons are you trying to remove? What have you tried so far? The simplest is often using css, something like https://www.ostraining.com/blog/wordpress/hide-element-css/ may help

HI,

I have the same concern.

Particularly since WP uses the ‘username’ as a unique id and a login. Meaning its not only shown in profiles and BP member information, its also used in Url paths like member and author links. Not to mention individual plugins and themes might directly reference and use ‘username’ in ways you might not anticipate. Which would mean lots of audits of all the themes, plugins and updates you use on the site. and a huge testing effort.

It seems to me that trying to shut down all those threats is time consuming, exhausting and prone for mistakes.

Why not just use ‘username’ as a unique id and turn off the ability to login by ‘username’. That way if ‘username’ is plastered all over the place, it does not matter so much — as it can not be used to login and access data.

I certainly hope WP is working on a solution to fix this issue, which I see as a security issue. (As in, you need two pieces of data to log in. Username and password. publicly providing 1 of those pieces of data (the username) severely increases security risk, problems, and issues.)

In the mean time,
I used hook action wp_authenticate to do my own login (that does not use the unique id ‘username’ ).
For more information on that hook action see https://developer.wordpress.org/reference/hooks/wp_authenticate/

Depending on where you put the ‘wp_authenticate’ solution this change can survive updates with out reapplication.

To be even more complete you can turn it off in the wordpress code, which would mean your changes would have to be reapplied after updates.